Venus Income Allocation

QuantstampRepository at commit 2e0f5f6

Audit

Part of Quantstamp’s series

Quantstamp reviewed Venus Protocol (Venus Income Allocation) on 12 Oct 2023: 12 findings, 0 critical; 2 marked fixed, 10 acknowledged; 2 more marked mitigated.

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

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings19

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

SeverityOpenAcknowledgedFixedMitigated
Critical0000
High0000
Medium0200
Low0822
LowInconsistency of Error Handling for vToken's Privileged FunctionsFixed

In the `VToken.setAccessControlManager()` function of the core pool, the caller is checked against the `admin`. If the caller is not authorized, the function returns an error code without reverting the transaction. However, the function comments state: > @return uint 0=success, otherwise will revert This inconsistency between the function's behavior and comments can confuse developers. Relying solely on the function's comments may lead developers to assume that a transaction will revert upon failure, while it may silently fail if `setAccessControlManager()` is called by an unauthorized caller. Additionally, other privileged setters within the codebase also have inconsistent behavior. For example, `setProtocolShareReserve()` silently fails with an error code returned if the caller is unauthorized, while `setReduceReservesBlockDelta()` reverts the transaction during an unauthorized call.

LowIt Is Not Possible to Remove Items From the `distributionTargets` ArrayFixed

Currently, the distribution configs are updated via the `addOrUpdateDistributionConfigs()` function, and hence, the `distributionTargets` array is updated. It is currently possible to add an entry or update a percentage of existing entries but not remove entries from the array, hence leading to an issue where if an entry was added incorrectly, it could not be removed and only be set to 0 percentage, hence leading to be not accounted for, but would waste gas.

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 (3)

  • https://github.com/VenusProtocol/venus-protocol/contracts/Tokens/VTokens/VTokenInterfaces.sol at commit 2e0f5f64f49aba3150e49c7a7e34a28826726f20
  • https://github.com/VenusProtocol/venus-protocol/contracts/Tokens/VTokens/VToken.sol at commit 2e0f5f64f49aba3150e49c7a7e34a28826726f20
  • https://github.com/VenusProtocol/venus-protocol/contracts/Utils/ErrorReporter.sol at commit 2e0f5f64f49aba3150e49c7a7e34a28826726f20

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

240 projects reviewed · 338 reports · latest Nov 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