Brickken has 2 public audit reports from Hacken and CertiK; the latest is Hacken, 15 Feb 2024; 1 critical finding, marked fixed by the firm. It also holds 4 deployed contracts on 4 chains.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
6 findings are still open or acknowledged in the firms’ reports: 3 high, 3 low (3 open, 3 acknowledged).
Centralization Related Risks
Brickken - Audit · CertiK · 23 Dec 2022 · Report ↗
Centralized Control of Contract Upgrade
Brickken - Audit · CertiK · 23 Dec 2022 · Report ↗
Potential Flashloan Attack
Brickken - Audit · CertiK · 23 Dec 2022 · Report ↗
Potential Price Manipulation in getBKNPrice() Function in STOFactoryUpgradeable.sol
Brickken / Protocol · Hacken · 15 Feb 2024 · Report ↗
Costly Operations Inside A Loop
Brickken - Audit · CertiK · 23 Dec 2022 · Report ↗
Third Party Dependency
Brickken - Audit · CertiK · 23 Dec 2022 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Brickken / Protocol | Security firm: Hacken | Date: | Scope: 4 addresses on 4 chains | None open | Findings: 6 medium · 8 low 13 fixed · 1 open | hacken.io ↗ |
| Brickken - Audit | Security firm: CertiK | Date: | Scope: Files listed | 1 critical finding, fixed | Findings: 1 critical · 3 high · 2 medium · 10 low 11 fixed · 3 acknowledged · 2 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 3 | 0 |
| Medium | 0 | 0 | 8 |
| Low | 3 | 0 | 15 |
The report gives no description here.
Open the reportThe computation for each iteration is complex, it could lead to gas insufficiency when the length of the array `tokensToChange` is large. ```solidity= function changeWhitelist( address[] calldata tokensToChange, uint256[] calldata multipliers, bool[] calldata statuses ) external onlyOwner { for (uint256 i = 0; i < tokensToChange.length; i++) { ```
Open the reportThe contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assume their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc.
Open the report| Address | Chain | Source code |
|---|---|---|
| 0xddb2…e3760xddb293bb5c5258f7484a94a0fbd5c8b2f6e4e376 | Chain: Base | Source code: Verified source |
| 0xd44e…c6bc0xd44e4dc8bdf7c1c62cfdbb182022097ba42ac6bc | Chain: Avalanche | Source code: Verified source |
| 0x0e28…b4980x0e28bc9b03971e95acf9ae1326e51ecf9c55b498 | Chain: BNB Chain | Source code: Verified source |
| 0x0a63…a36d0x0a638f07acc6969abf392bb009f216d22adea36d | Chain: Ethereum | Source code: Verified source |
Trustblock holds 2 public audit reports for Brickken, dated 23 Dec 2022 to 15 Feb 2024. The latest is by Hacken (“Brickken / Protocol”).
2 security firms wrote the reports Trustblock holds for Brickken: Hacken and CertiK.
6 findings are still open or acknowledged in the firms’ reports: 3 high, 3 low (3 open, 3 acknowledged). Of 1 critical finding: marked fixed by the firm. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="brickken"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
Something 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