Smart Contract Assessment

HalbornCode version: not recorded (see the report)

Audit · firm’s term: smart contract assessment

Halborn reviewed ORO (Smart Contract Assessment) on 29 May 2026: 7 findings, 0 critical; all marked fixed.

No open critical findings
Open the reportOpen ORO’s security record

Report hosted on halborn.com.

Trustblock does not review code.

Findings16

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium002
Low004

Marked Informational by the firm. Not counted as findings.

InformationalDenom admin handoff can leave the wrapper in exit only modeAcknowledged

The report gives no description here.

InformationalPause authority queries are not paginatedAcknowledged

The report gives no description here.

InformationalUnbonding period increases take effect immediatelyAcknowledged

The report gives no description here.

InformationalHook destination is not validated before dispatchFixed

The report gives no description here.

InformationalMigration handlers do not enforce forward only versioningFixed

The report gives no description here.

InformationalRelease build configuration disables declared overflow checksFixed

The report gives no description here.

InformationalTokenfactory reply parsing does not validate the returned denomFixed

The report gives no description here.

InformationalUnbounded airdrop scans can make fund recovery increasingly expensiveFixed

The report gives no description here.

InformationalWithdrawal guard relies on caller supplied token typeFixed

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

ORO
Audits3 audits by 1 firmLast audit Jun 2026, by Halborn.
Critical findingsNo open critical findingsAcross 3 reports.
Open ORO’s security record

Security firm

Halborn

36 projects reviewed · 80 reports · latest Oct 2026

See Halborn’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.

Tell us