Venus - VAI Controller Upgrade

CertiKFiles named in the report

Audit

Part of CertiK’s series

CertiK reviewed Venus Protocol (Venus - VAI Controller Upgrade) on 26 Apr 2024: 6 findings, 0 critical; 5 marked fixed, 1 open.

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

Report hosted on skynet.certik.com.

Trustblock does not review code.

Findings6

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low105
LowInconsistent Use Of `addUint`, `subUint`, `mulUinOpen

In the functions `mintVAI()` and `repayVAIFresh()`, the use of functions `addUint`, `subUint`, `mulUint`, and `divUint` was replaced by functions `add_`, `sub_`, `mul_` and `div_` respectively. The main difference is that the previous set of functions returned an error which was either used to revert the transaction and return a specific string message describing where the calculation failed or emit a `Failure` event. The updated version will revert with a generic overflow, underflow, or divide by zero string error. This is done only in the functions `mintVAI()` and `repayVAIFresh()`, with the remaining instances of `addUint`, `subUint`, `mulUint`, and `divUint` in the contract unchanged.

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.

Repository and files the report names (1)

  • contracts/Tokens/VAI/VAIController.sol

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

CertiK

1,045 projects reviewed · 1,376 reports · latest May 2025

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