Time-Based Contracts (Venus)
Summary
The Venus protocol is expanding to various EVM-compatible chains, transitioning from a block number-based to a dual timing mechanism that supports both block numbers and timestamps. This is due to the inconsistency of block times across different chains. This audit focuses on verifying these adaptations, which are distributed across several pull requests in two repositories: `venus-protocol` and `isolated-pools`. Additionally, the expansion to layer 2 chains necessitates unique oracle adaptations for their sequencers, requiring the Venus team to enhance their `oracle` repository with new features. A notable update includes the ability of the protocol to confiscate tokens from specific users and redistribute them. The audit found no other major issues but identified several low and informational points. **Update**: The Venus team addressed all issues by fixing or acknowledging them. The team also improved the test suite for all three repositories.
Issues (5)
Low | Medium | High | Critical | Total | |
|---|---|---|---|---|---|
Not fixed | 2 | - | - | - | 2 |
Fixed | 3 | - | - | - | 3 |
| Total | 5 | 0 | 0 | 0 | 5 |