Burr Pool Audit
BurrBear's Multi Stable Pool was forked from Balancer v2 and Burr Pools were forked from Xave Finance's FXPools. Attached here are the latest respective audits
Below is a summary of the security audits performed on the Balancer code that we have integrated into our project. Please refer to these reports for detailed findings and recommendations.
Audited Components and Reports from Balancer
| Scope | Company | Report |
|---|---|---|
Vault, Weighted Pool, Stable Pool | OpenZeppelin | |
Vault, Weighted Pool, Stable Pool | Trail of Bits | |
Vault | Certora | |
MultiRewards, Stable Pool | OpenZeppelin | |
Linear Pool, Stable Phantom Pool | Trail of Bits | |
Timelock Authorizer | ABDK | |
Batch Relayer | Trail of Bits | |
Composable Stable Pool | Certora | |
Composable Stable Pool | Trail of Bits | |
Managed Pool | Trail Of Bits |
Audited Components and Reports from Xave Finance
Our platform also integrates Burr Pools originally developed by Xave Finance. The following details the audits conducted on these components, which are essential for maintaining our platform’s security integrity.
PeckShield Audit
The review focused on the FXPool contract that was built on top of Balancer's v2 Vault. There were 5 issues (1 critical, 1 low, 1 information and 2 mediums) pointed out during the audit review. These issues have been resolved. Please refer to our Audit Report on PeckShield github here
Akira Tech Audit
Akira Tech's audit focused on manually reviewing the codebase, searching for security issues such as, but not limited to, re-entrancy problems, transaction ordering, block timestamp dependency, exception handling, call stack depth limitation, integer overflow/underflow, self-destructible contracts, unsecured balance, use of origin, costly gas patterns, architectural problems, code readability. Issues were closed on the updated version of the FXPool contract.
Last updated