Migration Core (Venus)

Quantstamp13 Sep 2025Code version: not recorded (see the report)

Quantstamp reviewed Venus Protocol (Migration Core (Venus)) on 13 Sep 2025: 3 findings, 0 critical; 1 marked fixed, 2 open.

No open critical findings

Open the report Open Venus Protocol’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings3

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

Severity	Open	Fixed
Critical	0	0
High	0	0
Medium	0	0
Low	2	1

Low`VTokenstorage` Does Not Keep Extra SlotsFixed

The new `VTokenInterfaceR1` implementation now inherits from `VTokenStorageR1` instead of `VTokenStorage`. The previous `VTokenStorage` contract reserved an additional 50 storage slots through a `uint256[50] __gap` placeholder, ensuring room for future variable additions without altering the storage layout. After the migration, this explicit reservation is no longer visible to developers. In subsequent upgrades, they may overlook the previously intended expansion buffer or inadvertently add storage variables beyond the implicit 50-slot allowance, risking storage collisions or corrupting the upgrade path.

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

Venus Protocol

Audits67 audits by 7 firmsLast audit Sep 2025, by Quantstamp.

Critical findingsNo open critical findingsAcross the 67 reports, 4 critical findings were reported. Each is marked fixed by the firm that reported it.

IncidentIncident 12 May 2022Source: De.Fi incident database.

Open Venus Protocol’s security record

Security firm

Quantstamp

236 projects reviewed · 332 reports · latest Oct 2026

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