Part of CertiK’s series
CertiK reviewed Venus Protocol (Venus - Vaults Audit) on 4 Jul 2023: 10 findings, 0 critical; 3 marked fixed, 7 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 6 | 0 | 3 |
The following struct in `XVSVaultStorage` was changed between implementations. From ```solidity struct WithdrawalRequest { uint256 amount; uint256 lockedUntil; } ``` to the struct ```solidity struct WithdrawalRequest { uint256 amount; uint128 lockedUntil; uint128 afterUpgrade; } ``` Note that both structs will only take up 2 storage slots, so there will not be any storage collisions. However the second slot now packs two `uint128` values together. If `lockedUntil` is greater than the maximum `uint128`, then it will overflow when the implementation is upgraded so that the new `lockedUntil` will be a smaller value. It will also make `afterUpgrade` a nonzero value to start. We give this an informational severity as it is very unlikely any of these values will be this large as it would require a `pool.lockPeriod` to be set to an extremely large value.
In `VRTVault.sol`, the error message from the modifier `userHasPosition()` is missing a space.
Some events are never emitted, which can lead to confusion and code maintainability issues. ```solidity=19 event AdminTransfered(address indexed oldAdmin, address indexed newAdmin); ``` - `AdminTransfered` is declared in `VRTVault` but never emitted.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (7)
1,045 projects reviewed · 1,376 reports · latest May 2025
See CertiK’s auditsSomething 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