Bancor audit reports

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).

Critical findings
No open critical findings
Across the 6 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it. See the findings
Incident
Incident 17 Jun 2020
Source: De.Fi incident database. 5 audits have been published since. See the incidents
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm34

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).

Medium
6
Low
28
  • Medium Acknowledged

    Incorrect Liquidity Decrease

    Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗

  • Medium Acknowledged

    Missing Slippage Protection

    Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗

  • Medium Acknowledged

    calcExpDecayRewards is at risk of overflow reversions

    Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗

  • Medium Acknowledged

    Lack of validation

    Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗

  • Medium Acknowledged

    weightedAverage calculation might overflow

    Bancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022 · Report ↗

  • Medium Acknowledged

    Use of external calls with a fixed amount of gas

    Bancor V2 AMM Security Audit · Consensys · 1 Jun 2020 · Report ↗

  • Low Acknowledged

    Trade Function Discrepancy

    Bancor Carbon · ChainSecurity · 10 Apr 2023 · Report ↗

  • Low Open

    Gas Savings

    Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗

  • Low Open

    Inconsistent Reentrancy Protection

    Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗

  • Low Acknowledged

    BNTPool.renounceFunding Division by 0

    Bancor V3 · ChainSecurity · 27 Sep 2022 · Report ↗

All 34 open and acknowledged findings

Incidents2

Attached through a shared contract address. Our incident data ends in Nov 2026.

Incident

Incident,

5M.

Source: De.Fi incident database.

Audits before it
1.
Audits since
5, the latest dated 10 Apr 2023.
Incident

Incident,

5M.

Source: De.Fi incident database.

Audits before it
0.
Audits since
6, the latest dated 10 Apr 2023.

Audits6

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Bancor CarbonSecurity firm: ChainSecurityDate: Scope: Not recorded; see the reportNone openFindings: 2 high · 5 low
6 fixed · 1 acknowledged
chainsecurity.com ↗
Bancor V3Security firm: ChainSecurityDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 5 medium · 23 low
20 fixed · 7 acknowledged · 2 open
chainsecurity.com ↗
Bancor Compounding Rewards AuditSecurity firm: OpenZeppelinDate: Scope: Files listedNone openFindings: 1 high · 3 medium · 5 low
1 fixed · 7 acknowledged · 1 open
blog.openzeppelin.com ↗
Bancor LiquiditySecurity firm: CertiKDate: Scope: Files listedNone openFindings: 17 low
6 fixed · 11 open
skynet.certik.com ↗
Bancor GovernenceSecurity firm: CertiKDate: Scope: Files listedNone openFindings: 2 high · 7 low
5 fixed · 4 open
skynet.certik.com ↗
Bancor V2 AMM Security AuditSecurity firm: ConsensysDate: Scope: Files listed1 critical finding, fixedFindings: 1 critical · 3 high · 1 medium · 1 low
5 fixed · 1 acknowledged
diligence.security ↗

Findings82

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical001
High009
Medium063
Low181030
LowGas SavingsBancor V3 · ChainSecurity · 27 Sep 2022Open

The report gives no description here.

Open the report
LowInconsistent Reentrancy ProtectionBancor V3 · ChainSecurity · 27 Sep 2022Open

The report gives no description here.

Open the report
LowLack of event emissions after updating stateBancor Compounding Rewards Audit · OpenZeppelin · 6 Sep 2022Open

The report gives no description here.

Open the report
Lowcheck-effect-patterns not followed when sending eBancor Liquidity · CertiK · 9 Oct 2020Open

`transfer` or `safeTransferFrom` is done before storage variables are updated.

Open the report
LowExternal calls inside a loopBancor Liquidity · CertiK · 9 Oct 2020Open

External calls in the loop may lead to issues with GAS costs of a transaction.

Open the report
LowInefficient greater-than comparison w/ zeroBancor Liquidity · CertiK · 9 Oct 2020Open

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 report
LowmaxSystemNetworkTokenAmount limit is mutable.Bancor Liquidity · CertiK · 9 Oct 2020Open

According 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 report
LowOld implementation of Ownable functionalityBancor Liquidity · CertiK · 9 Oct 2020Open

Implementation of Owned.sol comes from OpenZeppelin version 1.12.0, which is from 2018 and is no longer valid.

Open the report
LowUnneccessary if statementBancor Liquidity · CertiK · 9 Oct 2020Open

If statements can be simplified as `_newConverter.addReserve(ETH_RESERVE_ADDRESS, weight);` is repeated in both cases.

Open the report
LowUsage of `syncReserveBalances` in the beginning oBancor Liquidity · CertiK · 9 Oct 2020Open

`syncReserveBalances` is called at the start of many functions.

Open the report
Show 8 more
LowUsage of uint16 in for loopsBancor Liquidity · CertiK · 9 Oct 2020Open

`uint16` is not optimal use for `for loop`.

Open the report
LowUse of an assertBancor Liquidity · CertiK · 9 Oct 2020Open

assert() 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 report
LowUse of transfer() for sending ETHBancor Liquidity · CertiK · 9 Oct 2020Open

After 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 report
LowUse of two arrays instead of a mappingBancor Liquidity · CertiK · 9 Oct 2020Open

As 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
LowCustom implementation of access control logicBancor Governence · CertiK · 9 Oct 2020Open

`Owned.sol` contract seems to implement it's own logic for access control instead of relying on openzeppelin's `Ownable.sol` contract

Open the report
LowIncorrect version of solidityBancor Governence · CertiK · 9 Oct 2020Open

The 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 report
LowInefficient greater-than comparison w/ zeroBancor Governence · CertiK · 9 Oct 2020Open

Within 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 report
LowVariable tight packingBancor Governence · CertiK · 9 Oct 2020Open

Variables in the `struct` Proposal can be tightpacked

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

The repositories and files the reports name

Bancor: questions

Is Bancor audited?

Trustblock holds 6 public audit reports for Bancor, dated 1 Jun 2020 to 10 Apr 2023. The latest is by ChainSecurity (“Bancor Carbon”).

Who audited Bancor?

4 security firms wrote the reports Trustblock holds for Bancor: ChainSecurity, CertiK, OpenZeppelin and Consensys.

Are there open findings in Bancor’s audits?

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.

Show this on your site

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.

Content

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-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