BurrBear
  • Introduction
  • FAQs
  • Product Overview
    • Multi Stable Pools
    • Generalized Pool
    • Burr Pools
      • Why Use a Burr Pool?
      • Invariant FAQs
      • Oracle Registry
    • Contract Addresses
  • Tokenomics
    • BURR
    • Tokenomics
      • Airdrop Claims
    • Emissions Schedule
    • Governance
      • Reward Vault Request for NECT:HONEY:USDC Multi Stable Pool
  • Printing BurrBeras NFTs
    • What are the Printing BurrBeras?
    • Benefits Afforded to NFT Holders
    • Berome Powells
    • Bearet Yellens
    • Beary Benslers
    • Future NFT Collections
  • Developer Docs
  • Contract Audits
    • Boyco Audit
    • Audits
  • Socials
    • X (formerly Twitter)
    • Medium
    • Discord
    • Github
  • Branding Assets
    • Brand Assets
Powered by GitBook
On this page
  • Audited Components and Reports from Balancer
  • Burr Pool
  1. Contract Audits

Audits

PreviousBoyco AuditNextBrand Assets

Last updated 4 months ago

BurrBear is a Balancer v2 fork. 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

Burr Pool

PeckShield Audit

The review focused on the contracts that were 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

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.

2021-03-15
2021-04-02
2021-04-22
2021-10-09
2021-10-08
2022-05-27
2022-05-27
2022-09-23
2022-09-02
2022-10-25
here
374KB
PeckShield-Audit-Report-v1.0.pdf
pdf
2MB
Akira-Tech-Audit-Report.pdf
pdf