All smart contracts of deBridge can be found at [https://github.com/debridge-finance/debridge-contracts-v1](https://github.com/debridge-finance/debridge-contracts-v1) at main branch. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. For deBridge 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.

[deBridge](https://debridge.finance/) __is a cross-chain interoperability and liquidity transfer protocol__ that allows decentralized transfer of data and assets between various blockchains. The deBridge protocol is an infrastructure platform and hooking service for:

Direct theft of any user funds

Permanent freezing of funds

Protocol Insolvency

Forgery of the content of the cross-chain messages sent through the protocol

Forgery of the sender address or chain_id  of the cross-chain messages sent through the protocol

Unauthorized claim without valid signatures from deBridge validators

Unauthorized mint of the wrapped assets (deAssets)

Theft of funds (<5% TVL impact)

Temporary freezing of funds (more than 1 day freeze)

Smart contract unable to operate due to lack of token funds

Block stuffing for profit

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Unbounded gas consumption

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/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. 

In addition to Immunefi’s Vulnerability Severity Classification System, deBridge classifies the following vulnerabilities as follows. In case of discrepancy, the one below will be followed.

Critical
  - More than 5% of the loss of TVL or an unauthorized minting of deAssets in an amount that leads to substantial loss of the peg of the wrapped asset (Total supply of deAsset exceeds amount of underlying collateral locked for more than 5%)

High
  - Up to 5% of the loss of TVL or an unauthorized minting of deAssets in an amount that leads to substantial loss of the peg of the wrapped asset (Total supply of deAsset is on up to 5% exceeds the amount of underlying collateral locked)

The following vulnerabilities/problems are not eligible for a reward:

  - Default bridging functionality doesn’t support non-standard assets (e.g. rebase assets, assets with elastic supply or tokens with fees during transfer) 
  - If a user sets an incorrect receiver or fallback address he won’t be able to claim his transfer in the destination chain and funds might be locked forever
  - If user passes ​​REVERT_IF_EXTERNAL_FAIL flag and specifies "data" and "receiver address" params that will lead to tx being constantly reverted
  - Framework used by the deBridge node exploitation of which requires knowledge of IP address unless information about IP address was obtained during the attack
  - Problem with the callProxy smart contract when gas limit specified by claimer is not enough for the proper execution of the externalCall that leads to externalCall being reverted even though transaction itself is completed

Payouts are handled by the __deBridge__ team directly and are denominated in USD. However, payouts are done in __USDT and USDC__, with the choice of the ratio at the discretion of the team. 

deBridge

Resources & Documentation