Legion OTC

ZokyoCode version: not recorded (see the report)

Audit · firm’s term: smart contract review

Zokyo reviewed legion (Legion OTC) on 12 Jun 2024: 13 findings, 0 critical; 12 marked fixed, 1 acknowledged.

No open critical findings
Open the reportOpen legion’s security record
Report stored on IPFS. Content hash QmdaeK2CxF91pDx33LuZViBshUVE1M2pasciRJ7K5YhVao

Trustblock does not review code.

Findings13

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

SeverityOpenAcknowledgedFixed
Critical000
High002
Medium011
Low009
HighArbitrary walletAddress leads to potentially locked assetsFixed

The report gives no description here.

HighMethod revertEscrow() doesn’t work as expectedFixed

The report gives no description here.

MediumPossible loss of funds due to destroyEscrow() methodFixed

The report gives no description here.

LowApproved tokens not validated for address(0)Fixed

The report gives no description here.

LowCEI pattern not followedFixed

The report gives no description here.

LowEscrow amount not validated for > 0Fixed

The report gives no description here.

LowMissing disable initializerFixed

The report gives no description here.

LowMissing eventsFixed

The report gives no description here.

LowRedundant checkFixed

The report gives no description here.

LowRemove unused importsFixed

The report gives no description here.

Show 2 more
LowUnnecessary Safe Math is being utilizedFixed

The report gives no description here.

LowUse ENUM for seller/buyer rolesFixed

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

legion
Audits1 audit by 1 firmLast audit Jun 2024, by Zokyo.
Critical findingsNo open critical findingsIn 1 report.
Open legion’s security record

Security firm

Zokyo

89 projects reviewed · 131 reports · latest Feb 2025

See Zokyo’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