Anoma security review

Nethermind Security13 Nov 2025Code version: not recorded (see the report)

Nethermind Security reviewed Anoma (Anoma security review) on 13 Nov 2025: 3 findings, 0 critical; all marked fixed.

No open critical findings

Open the report Open Anoma’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings3

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	0	3

Marked Info or Best Practices by the firm. Not counted as findings.

InfoDifferences between the specification and implementationAcknowledged

The report gives no description here.

InfoPrivacy Leakage through imageID usageAcknowledged

The report gives no description here.

Best PracticesRemove debug trait for secret keyFixed

The report gives no description here.

Best PracticesShould constrain logic instances’ length to match the number of keys in the batch circuitFixed

The report gives no description here.

InfoThe function verifyMerkleProof() does not distinguish between the leaves and nodesFixed

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 Anoma’s security record

Anoma

Audits2 audits by 2 firmsLast audit Nov 2025, by Nethermind Security.

Critical findings1 critical acknowledged, not fixedReported in “Namada Ethereum Bridge audit” by Oak Security, Mar 2023. The team acknowledged it.

Open Anoma’s security record

Security firm

Nethermind Security

57 projects reviewed · 81 reports · latest Sep 2026

See Nethermind Security’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.