21 December 2021
Live since
No
KYC required
$100,000
Maximum bounty

Program Overview

Connext is the interoperability protocol of L2 Ethereum. You can use Connext to send transactions of value or call data across chains and/or rollups. Unlike most other interoperability systems, Connext enables this without introducing any new trust assumptions or external validators.

For more information about Connext, please visit https://connext.network/.

This bug bounty program is focused on their smart contracts and is focused on preventing:

  • Thefts and freezing of user funds
  • Thefts and freezing of liquidity on the contract
  • Network shutdown
  • Abuse of auction process
  • Abuse of virtual AMM pricing
  • Abuse of system to create fraudulent slashing conditions

Rewards by Threat Level

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System. This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts/blockchains, encompassing everything from consequence of exploitation to privilege required to likelihood of a successful exploit.

All Critical smart contract bug reports must come with a detailed written explanation in order to be considered for a reward.

Vulnerabilities marked in the Consensys Diligence Audit are not eligible for a reward.

Payouts are handled by the Connext team directly and are denominated in USD. However, payouts are done in USDC, USDT, DAI, with the choice of the ratio at the discretion of the team.

Smart Contracts and Blockchain

Critical
Level
USD $100,000
Payout
high
Level
USD $50,000
Payout
medium
Level
USD $20,000
Payout
low
Level
USD $10,000
Payout

Assets in Scope

All smart contracts of Connext can be found at https://github.com/connext/nxtp/tree/main/packages/contracts/contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. For similar contracts (multiple instances on different chains), there will not be duplicated counting of bugs. One bug that exists in all contracts will be counted as a single bug.

Impacts in Scope

Only the following impacts are accepted within this bug bounty program. All other impacts are not considered as in-scope, even if they affect something in the assets in scope table.

Smart Contracts/Blockchain

  • Thefts and freezing of user funds
  • Thefts and freezing of liquidity on the contract
  • Network shutdown
  • Abuse of auction process
  • Abuse of virtual AMM pricing
  • Abuse of system to create fraudulent slashing conditions
Smart Contract - Transaction Manager
Type
Smart Contract - Fulfill Interpreter
Type
Smart Contract - Multicall
Type
Smart Contract - Connext Price Oracle
Type
TransactionManager.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type
ConnextPriceOracle.sol
Type
TransactionManager.sol
Type
FulfillInterpreter.sol
Type
Multicall.sol
Type

Prioritized Vulnerabilities

We are especially interested in receiving and rewarding vulnerabilities of the following types:

Smart Contracts and Blockchain

  • Re-entrancy
  • Logic errors
    • including user authentication errors
  • Solidity/EVM details not considered
    • including integer over-/under-flow
    • including rounding errors
    • including unhandled exceptions
  • Trusting trust/dependency vulnerabilities
    • including composability vulnerabilities
  • Oracle failure/manipulation
  • Novel governance attacks
  • Economic/financial attacks
    • including flash loan attacks
  • Congestion and scalability
    • including running out of gas
    • including block stuffing
    • including susceptibility to frontrunning
  • Consensus failures
  • Cryptography problems
    • Signature malleability
    • Susceptibility to replay attacks
    • Weak randomness
    • Weak encryption
  • Susceptibility to block timestamp manipulation
  • Missing access controls / unprotected internal or debugging interfaces
  • All smart contract vulnerabilities
  • Double-spends from faulty off-chain logic
  • Creating fraudulent slashing conditions

Out of Scope & Rules

The following vulnerabilities are excluded from the rewards for this bug bounty program:

  • Attacks that the reporter has already exploited themselves, leading to damage
  • Attacks requiring access to leaked keys/credentials
  • Attacks requiring access to privileged addresses (governance, strategist)

Smart Contracts and Blockchain

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Basic economic governance attacks (e.g. 51% attack)
  • Lack of liquidity
  • Best practice critiques
  • Sybil attacks
  • Centralization risks

The following activities are prohibited by this bug bounty program:

  • Any testing with mainnet or public testnet contracts; all testing should be done on private testnets
  • Any testing with pricing oracles or third party smart contracts
  • Attempting phishing or other social engineering attacks against our employees and/or customers
  • Any testing with third party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
  • Any denial of service attacks
  • Automated testing of services that generates significant amounts of traffic
  • Public disclosure of an unpatched vulnerability in an embargoed bounty