Velvet Capital - V3 Smart Contracts

Resonance SecurityCode version: not recorded (see the report)

Resonance Security reviewed Velvet Capital (Velvet Capital - V3 Smart Contracts) on 19 Sep 2024: 11 findings, 1 critical; 7 marked fixed, 4 acknowledged.

1 critical finding, fixed
Open the reportOpen Velvet Capital’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings21

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

SeverityOpenAcknowledgedFixed
Critical001
High002
Medium012
Low032

Marked Info by the firm. Not counted as findings.

InfoLack of ERC165 ChecksAcknowledged

The report gives no description here.

InfoTransfer Of Super Admin Ownership Does Not Revoke Other RolesAcknowledged

The report gives no description here.

InfoMissing Length ChecksFixed

The report gives no description here.

InfoPossible Accidental Event FloodingFixed

The report gives no description here.

InfoPrice Check Not Taking Into Account The Return TypeFixed

The report gives no description here.

InfoRedundant Checks On latestRoundData()Fixed

The report gives no description here.

InfoRedundant Checks On multiTokenWithdrawal()Fixed

The report gives no description here.

InfoRedundant Checks On updateTokens()Fixed

The report gives no description here.

InfoUnused FunctionsFixed

The report gives no description here.

InfoUnused Input Parameter _protocolConfigFixed

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

Velvet Capital
Audits3 audits by 2 firmsLast audit Sep 2024, by Resonance Security.
Critical findingsNo open critical findingsAcross the 3 reports, 3 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Velvet Capital’s security record

Security firm

Resonance Security

27 projects reviewed · 57 reports · latest Dec 2025

See Resonance Security’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