Orderly Network audit
Audit competition · firm’s term: private contest
Sherlock reviewed Orderly Network (Orderly Network audit) on 30 Jun 2024: 5 findings, 0 critical; 4 marked fixed, 1 acknowledged.
No open critical findings
Open the reportOpen Orderly Network’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings5
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 1 |
| Medium | 0 | 1 | 3 |
| Low | 0 | 0 | 0 |
HighValor._doValorEmission() should not be a public functionFixed
The report gives no description here.
MediumBackward fees are not sent to the ledger and there is no function to extract them from vault chainFixed
The report gives no description here.
MediumMismatch between lastValorUpdateTimestamp and valorEmissionStartTimestamp during the OmnichainLedgerV1.initialize() functionFixed
The report gives no description here.
MediumProxyLedger operations will always revert due to mismatch of fee in the parameter and ProxyLedger provided to _lzSend()Fixed
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 Orderly Network’s security record
Orderly NetworkAudits19 audits by 5 firmsLast audit Nov 2025, by Guardian Audits.
Critical findings2 criticals acknowledged, not fixedReported in 2 reports, the latest by Guardian Audits, Oct 2023. The team acknowledged both.
Open Orderly Network’s security recordSecurity firm
Sherlock46 projects reviewed · 67 reports · latest Sep 2026
See Sherlock’s auditsSomething 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