Part of CertiK’s series
CertiK reviewed Venus Protocol (Venus - Mesh Architecture) on 19 Apr 2024: 3 findings, 0 critical; 2 marked fixed, 1 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 | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 0 | 2 |
In order for an address to be whitelisted, they must be whitelisted on both the sending and receiving chain. With the mesh-architecture it allows for an address to be implicitly whitelisted between two chains. This may cause an issue if an address should not be whitelisted when transferring directly to/from a specific chain, but it is necessary to whitelist a path between the chains. Note that this is a strictly hypothetical scenario and we are not aware of any protocols where such a scenario would cause an issues.
Both contracts set the single send and receive limit to `10000`. Similarly, they set the max daily send and receive limits to be `50000`, where this value is determined by the USD value when the function is called. As such tokens may be sent when the value of `XVS` dropped dramatically, so that when the message is to be received and the price recovers it will exceed the single receive limit or the max daily receive limit. Alternatively, the price of XVS may drop on one chains oracle, but remain constant on another chains oracle.
The report names a repository or files. Open the report to see its scope.
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