Exactly Protocol Update audit (October 2025)

ABDK ConsultingCode version: not recorded (see the report)

ABDK Consulting reviewed Exactly Protocol (Exactly Protocol Update audit (October 2025)) on 31 Oct 2025: 37 findings, 0 critical; 8 marked fixed, 29 acknowledged.

No open critical findings
Open the reportOpen Exactly Protocol’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings37

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium062
Low0236
MediumIn case “allowed” is false, the “allower” field should be cleared.Fixed

The report gives no description here.

MediumThis makes it impossible to distinguish the “ExtensionFailed” error throws here and the same error thrown from within the extension.Fixed

The report gives no description here.

LowConsider specifying as “^0.8.0” unless there is something special regarding this particular version.Fixed

The report gives no description here.

LowProcedural in VerifiedAuditor.solFixed

The report gives no description here.

LowProcedural in VerifiedMarket.solFixed

The report gives no description here.

LowSuboptimal in DebtRoller.solFixed

The report gives no description here.

LowSuboptimal in FlashLoanAdapter.solFixed

The report gives no description here.

LowWe didn’t review this file.Fixed

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

Exactly Protocol
Audits8 audits by 3 firmsLast audit Oct 2025, by ABDK Consulting.
Critical findingsNo open critical findingsAcross the 8 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Exactly Protocol’s security record

Security firm

ABDK Consulting

31 projects reviewed · 64 reports · latest Jan 2026

See ABDK Consulting’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