Omniscia Brickken Protocol Audit
Token Implementation Security Audit
Audit Overview
We were tasked with performing an audit of the Brickken codebase and in particular their ERC20 token implementation supporting two additional functionalities; a Compound-like token balance tracking mechanism suitable for governance as well as the EIP-2612 permit implementation.
Over the course of the audit, we identified a documentation mismatch as well as certain optimizations that can be applied to the codebase that we advise the Brickken team to evaluate and assimilate in their codebase.
Post-Audit Conclusion
The Brickken team has acknowledged all issues identified in the report and has opted to not apply any changes to the codebase to alleviate them as they have already deployed their contracts.
As a result, a centralization concern remains with regards to the roles that the Brickken token contract has assigned to its owners and we urge them to delegate those roles to a proper DAO implementation as soon as possible.
Contracts Assessed
| Files in Scope | Repository | Commit(s) |
|---|---|---|
| Brickken.sol (BRI) | protocol | 8286d7f90d |
Audit Synopsis
| Severity | Identified | Alleviated | Partially Alleviated | Acknowledged |
|---|---|---|---|---|
 | 0 | 0 | 0 | 0 |
 | 0 | 0 | 0 | 0 |
 | 1 | 0 | 0 | 1 |
 | 5 | 1 | 0 | 4 |
During the audit, we filtered and validated a total of 1 findings utilizing static analysis tools as well as identified a total of 5 findings during the manual review of the codebase. We strongly recommend that any minor severity or higher findings are dealt with promptly prior to the project's launch as they introduce potential misbehaviours of the system as well as exploits.
The list below covers each segment of the audit in depth and links to the respective chapter of the report: