BENQI Ignite Audit Report

CyfrinCode version: not recorded (see the report)

Audit · firm’s term: audit report

Cyfrin reviewed BENQI (BENQI Ignite Audit Report) on 11 Dec 2024: 11 findings, 0 critical; 8 marked fixed, 3 acknowledged.

No open critical findings
Open BENQI’s security record

The original report was removed from its address (seen 18 Oct 2026).

Trustblock does not review code.

Findings11

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium005
Low032
HighZeeve admin could drain ValidatorRewarder by abusing off-chain BLS validation due to QI rewards being granted to failed registrationsFixed

The report gives no description here.

MediumIgnite fee is not returned for pre-validated QI stakes in the event of registration failureFixed

The report gives no description here.

MediumInconsistent transfers of native tokens could result in unexpected loss of fundsFixed

The report gives no description here.

MediumRedemption of failed registration fees and pre-validated QI is not guaranteed to be possibleFixed

The report gives no description here.

MediumRedemption of slashed registrations could result in DoS due to incorrect state updateFixed

The report gives no description here.

MediumThe default admin role controls all other roles within StakingContractFixed

The report gives no description here.

LowIncorrect operator when validating subsidisation capFixed

The report gives no description here.

LowStakingContract::slippage can be outside of minSlippage or maxSlippageFixed

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

BENQI
Audits3 audits by 1 firmLast audit Nov 2025, by Cyfrin.
Critical findingsNo open critical findingsAcross 3 reports.
Open BENQI’s security record

Security firm

Cyfrin

28 projects reviewed · 79 reports · latest Sep 2026

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