Incident,
5M.
Source: De.Fi incident database.
- Audits before it
- 1.
- Audits since
- 5, the latest dated 10 Apr 2023.
Bancor has 6 public audit reports from ChainSecurity, CertiK, OpenZeppelin and 1 other firm; the latest is ChainSecurity, 10 Apr 2023; 1 critical finding, marked fixed by the firm. It also holds 2 incidents (latest 17 Jun 2020).
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
34 findings are still open or acknowledged in the firms’ reports: 6 medium, 28 low (18 open, 16 acknowledged).
Incorrect Liquidity Decrease
Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗
Missing Slippage Protection
Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗
calcExpDecayRewards is at risk of overflow reversions
Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗
Lack of validation
Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗
weightedAverage calculation might overflow
Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗
Use of external calls with a fixed amount of gas
Bancor V2 AMM Security Audit · Consensys · 1 Jun 2020 · Report ↗
Trade Function Discrepancy
Bancor Carbon · ChainSecurity · 10 Apr 2023 · Report ↗
Gas Savings
Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗
Inconsistent Reentrancy Protection
Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗
BNTPool.renounceFunding Division by 0
Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗
Attached through a shared contract address. Our incident data ends in Nov 2026.
5M.
Source: De.Fi incident database.
5M.
Source: De.Fi incident database.
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Bancor Carbon | Security firm: ChainSecurity | Date: | Scope: —Not recorded; see the report | None open | Findings: 2 high · 5 low 6 fixed · 1 acknowledged | chainsecurity.com ↗ |
| Bancor V3 | Security firm: ChainSecurity | Date: | Scope: —Not recorded; see the report | None open | Findings: 1 high · 5 medium · 23 low 20 fixed · 7 acknowledged · 2 open | chainsecurity.com ↗ |
| Bancor Compounding Rewards Audit | Security firm: OpenZeppelin | Date: | Scope: Files listed | None open | Findings: 1 high · 3 medium · 5 low 1 fixed · 7 acknowledged · 1 open | blog.openzeppelin.com ↗ |
| Bancor Liquidity | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 17 low 6 fixed · 11 open | skynet.certik.com ↗ |
| Bancor Governence | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 2 high · 7 low 5 fixed · 4 open | skynet.certik.com ↗ |
| Bancor V2 AMM Security Audit | Security firm: Consensys | Date: | Scope: Files listed | 1 critical finding, fixed | Findings: 1 critical · 3 high · 1 medium · 1 low 5 fixed · 1 acknowledged | diligence.security ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 1 |
| High | 0 | 0 | 9 |
| Medium | 0 | 6 | 3 |
| Low | 18 | 10 | 30 |
The report gives no description here.
Open the reportThe report gives no description here.
Open the reportThe report gives no description here.
Open the report`transfer` or `safeTransferFrom` is done before storage variables are updated.
Open the reportExternal calls in the loop may lead to issues with GAS costs of a transaction.
Open the reportWithin Solidity, unsigned integers are restricted to the non-negative range. As such, greater-than comparisons with the literal 0 are inefficient gas-wise.
Open the reportAccording to the documentation, `The system holdings cannot exceed 500K BNT worth of pool tokens in a pool`. In contrast, `maxSystemNetworkTokenAmount` is not a constant value and can be changed using `setSystemNetworkTokenLimits()` function.
Open the reportImplementation of Owned.sol comes from OpenZeppelin version 1.12.0, which is from 2018 and is no longer valid.
Open the reportIf statements can be simplified as `_newConverter.addReserve(ETH_RESERVE_ADDRESS, weight);` is repeated in both cases.
Open the report`syncReserveBalances` is called at the start of many functions.
Open the report`uint16` is not optimal use for `for loop`.
Open the reportassert() uses all gas available in the transaction. The assert() function should only be used to test for internal errors and check invariants. Within Solidity, unsigned integers are restricted to the non-negative range. As such, greater-than comparisons with the literal 0 are inefficient gas-wise.
Open the reportAfter EIP 1884 was included in the Istanbul hard fork, it's not recommended to use .transfer() and .send() as this function's a hard dependency on gas costs make them obsolete as they are forwarding a fixed amount of gas 2300 . This can cause some issues when sending ether to a contract. send and transfer do not longer protect from reentrancies in case of gas price changes.
Open the reportAs the `addLiquidity` , `removeLiquidity` and `verifyLiquidityInput` functions all accept an array of token addresses and an array of amounts that are associated with each other, it makes code harder to review and read.
Open the report`Owned.sol` contract seems to implement it's own logic for access control instead of relying on openzeppelin's `Ownable.sol` contract
Open the reportThe linked contracts necessitate a version too recent to be trusted. Consider deploying with 0.6.11. We do not recommend using any latest version for deployment, specially if changes were made in the optimizer or the language semantic. Version 0.6.12 made changes to optimiser that's why we do not recommend using this version.
Open the reportWithin Solidity, unsigined integers are restricted to the non-negative range. As such, greater-than comparisons with the literal 0 are inefficient gas-wise
Open the reportVariables in the `struct` Proposal can be tightpacked
Open the reportThe reports name a repository or files. Open a report to see its scope.
Trustblock holds 6 public audit reports for Bancor, dated 1 Jun 2020 to 10 Apr 2023. The latest is by ChainSecurity (“Bancor Carbon”).
4 security firms wrote the reports Trustblock holds for Bancor: ChainSecurity, CertiK, OpenZeppelin and Consensys.
34 findings are still open or acknowledged in the firms’ reports: 6 medium, 28 low (18 open, 16 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="bancor"></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