Easy Track Payment Processor with limits 09-2022 s

StatemindCode version: not recorded (see the report)

Statemind reviewed Lido (Easy Track Payment Processor with limits 09-2022 s) on 30 Sep 2022: 9 findings, 0 critical; all acknowledged, none fixed.

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

Report hosted on GitHub.

Trustblock does not review code.

Findings9

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

SeverityOpenAcknowledgedFixed
Critical000
High010
Medium000
Low080
HighPossible griefing attack to cancel motionsAcknowledged

The report gives no description here.

LowEvent parameter can be indexedAcknowledged

The report gives no description here.

LowGas optimization by replacing memory with calldataAcknowledged

The report gives no description here.

LowInconsistent naming of function parametersAcknowledged

The report gives no description here.

LowIncorrect NatSpec commentsAcknowledged

The report gives no description here.

LowNo checks for address zeroAcknowledged

The report gives no description here.

LowNode operator can spamAcknowledged

The report gives no description here.

LowPossible to create a motion with transfer amount bigger than single transfer limitAcknowledged

The report gives no description here.

LowVariables can be immutableAcknowledged

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

Lido
Audits53 audits by 13 firmsLast audit Sep 2026, by Composable Security.
Critical findings2 criticals acknowledged, not fixedReported in 2 reports, the latest by Statemind, Apr 2023. The team acknowledged both.
Open Lido’s security record

Security firm

Statemind

1 project reviewed · 11 reports · latest Jun 2026

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