Orchid Network Protocol

Consensys1 Nov 2019Code version: not recorded (see the report)

Consensys reviewed Orchid (Orchid Network Protocol) on 1 Nov 2019: 10 findings, 1 critical; 7 marked fixed, 3 open.

1 critical finding, fixed

Open the report Open Orchid’s security record

Report hosted on diligence.security.

Trustblock does not review code.

Findings10

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	1
High	0	0	0
Medium	0	0	2
Low	3	0	4

CriticalStaking node can be inappropriately removed from the treeFixed

The report gives no description here.

MediumSimplify the logic in OrchidDirectory.pull()Fixed

The report gives no description here.

MediumVerifiers need to be pure, but it’s very difficult to validate purenessFixed

The report gives no description here.

LowDocument that math in OrchidDirectory assumes a maximum number of tokensFixed

The report gives no description here.

LowImprove function visibilityFixed

The report gives no description here.

LowUnneeded named return parameterFixed

The report gives no description here.

LowUse consistent staker, stakee ordering in OrchidDirectoryFixed

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

Orchid

Audits3 audits by 1 firmLast audit Dec 2020, by Consensys.

Critical findingsNo open critical findingsAcross the 3 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.

Open Orchid’s security record

Security firm

Consensys

41 projects reviewed · 59 reports · latest Oct 2024

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