Jito Interceptor

CertoraCode version: not recorded (see the report)

Audit · firm’s term: security assessment & formal verification · Includes formal verification

Certora reviewed Jito (Jito Interceptor) on 13 Dec 2024: 8 findings, 0 critical; 4 marked fixed, 4 open.

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

Report hosted on GitHub.

Trustblock does not review code.

Findings8

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium002
Low401
Lowcalculate_fee_amount may return fee amount greater than the total_amountOpen

The report gives no description here.

Lowprocess_claim_pool_tokens does not check that the vaults are distinct.Open

The report gives no description here.

LowUsage of saturating_sub in process_claim_pool_tokens.Open

The report gives no description here.

LowWhen a receipt is closed/claimed with a transferred owner, the rent will not be paidOpen

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

Jito
Audits1 audit by 1 firmLast audit Jan 2025, by Certora.
Critical findingsNo open critical findingsIn that report, 6 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Jito’s security record

Security firm

Certora

20 projects reviewed · 46 reports · latest Aug 2026

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