Connext

Connext is a modular protocol for securely passing funds and data between chains. Developers can use Connext to build crosschain apps (xApps) - applications that interact with multiple domains (blockchains and/or rollups) simultaneously.

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 AMM pricing
• Abuse of system to create fraudulent slashing conditions

Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2. 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.

Rewards for valid bug reports are paid at the dollar amount displayed in the rewards table or 10% of the USD value at risk, whichever of the two is less.

Vulnerabilities marked in the following audits are not eligible for a reward.

• Consensys Diligence Audit
• https://github.com/connext/audits

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.

All smart contracts of Connext can be found at https://github.com/connext/monorepo/tree/main/packages/deployments/contracts/contracts. with recent deployments in the deployments directory. 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.

If a High or Critical impact can be caused to any other asset managed by Connext that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

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