Venus Multichain Support

QuantstampRepository at commit 5299454

Audit

Part of Quantstamp’s series

Quantstamp reviewed Venus Protocol (Venus Multichain Support) on 19 Dec 2023: 20 findings, 0 critical; 12 marked fixed, 8 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.

Findings30

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

SeverityOpenAcknowledgedFixedMitigated
Critical0000
High0000
Medium0130
Low0792

The firm marks these findings Mitigated. They are not counted as open, acknowledged or fixed.

LowBlock Time Is Subject to ChangeMitigated

The interest rate contracts store an immutable variable `blocksPerYear` to help with calculations. However, the block time for each chain is not guaranteed to remain the same across L2's. For opBNB, the currently configured block time is 1 second, according to the [official document](https://docs.bnbchain.org/opbnb-docs/docs/core-concepts/difference-L2), which, however, includes a warning that it is susceptible to changes.

LowBlock Time on Polygon zkEVM Depends on Chain UsageMitigated

The protocol's interest rate models calculate the borrow and supply rates per block of the markets based on their current utilization rate. The `blocksPerYear` immutable variable in the models is configured based on the deployed chain to adjust the market APR. On Ethereum, BSC, and opBNB chains, the block time can be considered a reliable source of timing information. However, for Polygon zkEVM, the block time is irregular at the time of writing and depends on the chain usage. According to the [historical average block time](https://zkevm.polygonscan.com/chart/blocktime) on the Polygon zkEVM explorer, we can observe that the average block time varies over time and is relatively unreliable. This is because, currently, Polygon zkEVM blocks are produced on-demand, according to [rollup.codes](https://www.rollup.codes/polygon-zkevm), > New L2 blocks contain only one L2 transaction and is created on-demand, i.e., once there is a new transaction. An irregular block time may also affect the reward distribution rate of the XVS vault, which calculates the reward amount based on a configured `rewardTokenAmountsPerBlock` value and the number of passed blocks.

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

  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/token/XVS.sol at commit 5299454
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVaultProxy.sol at commit a158f8c
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/interfaces/IXVS.sol at commit 5299454
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/interfaces/IXVSProxyOFT.sol at commit 5299454
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVaultErrorReporter.sol at commit a158f8c
  • https://github.com/VenusProtocol/isolated-pools/contracts/JumpRateModelV2.sol at commit 5e660bf
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/token/TokenController.sol at commit 5299454
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVault.sol at commit a158f8c
  • https://github.com/VenusProtocol/governance-contracts/contracts/Governance/AccessControlManager.sol at commit 358bed4
  • https://github.com/VenusProtocol/isolated-pools/contracts/WhitePaperInterestRateModel.sol at commit 5e660bf
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/XVSBridgeAdmin.sol at commit 5299454
  • https://github.com/VenusProtocol/venus-protocol/contracts/Governance/VTreasuryV8.sol at commit 0a05857
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSVaultStorage.sol at commit a158f8c
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/BaseXVSProxyOFT.sol at commit 5299454
  • https://github.com/VenusProtocol/oracle/contracts/oracles/ChainlinkOracle.sol at commit a0a36bc
  • https://github.com/VenusProtocol/venus-protocol/contracts/XVSVault/XVSStore.sol at commit a158f8c
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/XVSProxyOFTSrc.sol at commit 5299454
  • https://github.com/VenusProtocol/isolated-pools/contracts/BaseJumpRateModelV2.sol at commit 5e660bf
  • https://github.com/VenusProtocol/oracle/contracts/ResilientOracle.sol at commit a0a36bc
  • https://github.com/VenusProtocol/isolated-pools/contracts/lib/constants.sol at commit 5e660bf
  • https://github.com/VenusProtocol/protocol-reserve/contracts/ProtocolReserve/ProtocolShareReserve.sol at commit e396119
  • https://github.com/VenusProtocol/isolated-pools/contracts/Bridge/XVSProxyOFTDest.sol at commit 5299454

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