Huma protocol

Certora4 Jul 2024Code version: not recorded (see the report)

Audit · firm’s term: security assessment & formal verification · Includes formal verification

Certora reviewed Huma Finance (Huma protocol) on 4 Jul 2024: 11 findings, 0 critical; 9 marked fixed, 2 acknowledged.

No open critical findings

Open the report Open Huma Finance’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings25

Statuses are the security firm’s own, from its report.

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	0	0
Medium	0	0	0
Low	0	2	9

LowDuplicate error codesFixed

The report gives no description here.

LowEvent uses amount instead of amount_to_collectFixed

The report gives no description here.

LowInitialize can be front-runFixed

The report gives no description here.

LowMisleading eventsFixed

The report gives no description here.

LowMissing check on indexFixed

The report gives no description here.

LowPool state can be changed after it is closedFixed

The report gives no description here.

LowRemoving and adding lender deletes dataFixed

The report gives no description here.

LowUnderlying token decimals could be too large or too smallFixed

The report gives no description here.

LowUnprocessed_amount not always scaled correctlyFixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Huma Finance’s security record

Huma Finance

Audits8 audits by 4 firmsLast audit Dec 2025, by Halborn.

Critical findingsNo open critical findingsAcross 8 reports.

Open Huma Finance’s security record

Security firm

Certora

29 projects reviewed · 56 reports · latest Aug 2026

See Certora’s audits

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.