All smart contracts of Celer Network can be found at [https://github.com/celer-network/sgn-v2-contracts](https://github.com/celer-network/sgn-v2-contracts). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program. For cBridge 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 permanent freezing of any funds in liquidity pool smart contract or staking contracts
  - Thefts and permanent freezing of unclaimed yield rewards

__Web/App__

The only web vulnerabilities in scope are those which lead directly and unequivocally to loss of user funds, a direct breach of data, and the deletion of site data

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

There are some modifications from the above Severity Classification for this bug bounty program:

Critical Level Security - Modified: 
  - Empty or permanent freeze the contract's holdings (e.g. economic attacks, flash loans, reentrancy, MEV, logic errors, integer over-/under-flow)

Medium Level Security - Excluded: 
  - Griefing denial of service (i.e. attacker spends as much in gas as damage to the contract)
  - Gas griefing

All web/app bug reports must come with a PoC in order to be considered for a reward. All High and Critical Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. 
Critical Smart Contract and Blockchain bug reports are further capped at 10% of economic damage up to USD 2,000,000, which primarily takes into consideration the funds at risk but may include branding and PR aspects at the discretion of the team. However, they have a minimum reward of USD 150,000. 

The following vulnerabilities are not eligible for a reward:

  - Previously known vulnerabilities (resolved or not) on the Ethereum network (and any other fork of these).
  - Previously known vulnerabilities in Tendermint and or/any other fork of these.
  - Previously known vulnerabilities in cosmos-sdk and or/any other fork of these.
  - Previously known vulnerable libraries without a working Proof of Concept.
  - Attacks requiring MITM or physical access to a user's device.
  - Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis
  - Any griefing attacks on the system or smart contract trying to spend gas costs or liquidity lockup to incur gas costs and computational overhead  for the validators and operators of the network.
  - Liquidity value reduction or arbitraging incurred due to the pricing mechanisms of the system and LP’s own operations. 
  - Attacks involving getting access to privileged admin keys 
  - Delay of cross-chain transfer (fund security not compromised) due to network/rpc error from the blockchain endpoint being used by SGN validators
  - Security issues related to connected blockchains of cBridge is not in the scope
  - As to the current implementation, it is possible (with low probability) that a user triggered transaction (e.g., add liquidity, send fund, delegate stake) is not automatically synced to the sgn, or the sgn failed to automatically submit the fund relay transaction to the destination chain (e.g., due to chain rpc endpoint failure). Such cases do not introduce fund security, and can be recovered through manual CLI tools. Related improvements will be included in later releases.

Celer Network requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed is acquired through mutually agreed third-party KYC solutions. The collection of this information will be done by the Celer Network team.

Payouts are handled by the __Celer Network__ team directly and are denominated in USD. However, payouts are done in __ETH__, __CELR__, __or a stablecoin__, with the choice of the ratio at the discretion of the team.


All smart contracts of Polkastarter can be found at [https://github.com/polkastarter](https://github.com/polkastarter). However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

__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__

Loss of user funds staked (principal) by freezing or theft.

__Web/App__

Anything that can lead to loss of user funds.

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System](https://immunefi.com/severity-updated/). 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 bug reports must come with a PoC in order to be considered for a reward.

Critical vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum of __USD 50 000__ for Critical bug reports. 

Payouts are handled by the __Polkastarter__ team directly and are denominated in USD. Payouts are done in __USDC__ or __USDT__, up to the discretion of the team.

Only the web/app assets explicitly listed here are in-scope. All else is out-of-scope.

Relevant smart contracts of Polygon can be found at:

[https://github.com/maticnetwork/contracts](https://github.com/maticnetwork/contracts)

[https://github.com/maticnetwork/pos-portal](https://github.com/maticnetwork/contracts)

[https://github.com/fx-portal/contracts](https://github.com/maticnetwork/contracts)

[https://github.com/maticnetwork/genesis-contracts](https://github.com/maticnetwork/genesis-contracts) 

However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

__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__

  - Loss of user funds by permanent freezing or direct theft
  - Loss of governance funds
  - Theft of unclaimed yield
  - Freezing of unclaimed yield
  - Temporary freezing of funds for any amount of time
  - Unable to call smart contract
  - Network shutdown
  - Smart contract gas drainage
  - Smart contract fails to deliver promised returns
  - Checkpoint manipulation
  - Protection of Delegated and Staked Amount on Smart Contract
  - Securing Bridge Transfers (Minting, Withdrawal)
  - Double spend by getting the clients to accept a different chain
  - Double spend by validating malicious blocks
  - Tamper/manipulate blockchain history to invalidate transactions
  - Cause a user to mint tokens to own account
  - Undermine consensus mechanism to split the chain
  - Censorship (e.g. on checkpoints)
  - Steal tokens from node
  - Prevent node from accessing the network
  - Abuse bugs in the economic system to defraud other participants (e.g. avoid transaction fees to full nodes)
  - Denial of service attacks
  - Chain halt and shutting down the network 

__Web/App__

  - Domain takeover
  - Denial of service
  - Access on server
  - Users spoofing other users
  - Redirected funds by address modification

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

A PoC and a suggestion for a fix is required for all Critical and High bug reports. Additionally, a PoC is required for Medium Web/App bug reports. A high-quality suggestion for a fix may come with a bonus from the Polygon team.

All bug reports must include the following information in order to be considered for a reward:

Summary:
  - add summary of the vulnerability

Steps To Reproduce:
  - add details for how we can reproduce the issue

  1.  add step
  1.  add step
  1.  add step

Supporting Material/References:
 - list any additional material (e.g. screenshots, logs, etc.)
    - attachment / reference

Bug reports containing the following will not be eligible for a reward with this bug bounty program:

  - Previously known vulnerabilities (resolved or not) on the Ethereum network (and any other fork of these).
  - Previously known vulnerabilities in Tendermint and or/any other fork of these.
  - Previously known vulnerabilities in cosmos-sdk and or/any other fork of these.
  - Previously known vulnerable libraries without a working Proof of Concept.
  - Attacks requiring MITM or physical access to a user's device.
  - Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.

Critical Smart Contract bug reports are further capped at 10% of economic damage, which primarily takes into consideration the funds at risk but may include branding and PR aspects at the discretion of the team. However, they have a minimum reward of __USD 100 000__. 

Payouts are handled by the __Polygon__ team directly and are denominated in USD. However, payouts are done in __MATIC__. The Polygon team may, at its discretion, allow for other options to be done.

Further information about the smart contracts in Sifchain can be found at [https://github.com/Sifchain/sifnode/tree/master/smart-contracts](https://github.com/Sifchain/sifnode/tree/master/smart-contracts). However, only those in the assets in scope table are considered as in-scope of the bug bounty program. 

Further information about the Web/App can be found at [https://github.com/sifchain/sifchain-ui](https://github.com/sifchain/sifchain-ui). Additionally, all other web/app components of the project are out-of-scope for this bug bounty program. 

Web/App vulnerabilities not directly involving the assets listed in this table are out of scope. 

__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 and Blockchain__

  - Loss of any funds by freezing or theft
  - Gaining unauthorized permissions or access to privileged roles
  - Any crashing or loss of availability of our blockchain

__Web/App__

  - Direct loss of any funds by freezing or theft
  - Gaining unauthorized permissions or access to privileged roles
  - Any crashing or loss of availability of our blockchain

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System](https://immunefi.com/severity-updated/). 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 web/app bug reports must come with a PoC in order to be considered for a reward. A PoC is not required for smart contract and blockchain vulnerabilities. However, one may be requested if validity is questioned. 

For both Smart Contract and web/app bugs, only those that are explicitly within the Impacts in Scope section are considered as in-scope of the bug bounty program. Additionally, for added clarification, the following vulnerabilities are explicitly out-of-scope in the bug bounty program:

  - Anything involving DDoS
  - Anything involving third party distributed system dependencies, especially various open source IBC relayer nodes, and overloading/crashing them
  -  Previously known vulnerabilities (resolved or not) on the Ethereum network (and any other fork of these).
  - Previously known vulnerabilities in Tendermint and or/any other fork of these.
  - Previously known vulnerabilities in Cosmos SDK and or/any other fork of these.
  - Previously known vulnerable libraries without a working Proof of Concept.
  - Public Zero-day vulnerabilities that have had an official patch for less than 1 month will be awarded on a case by case basis.
  - Findings related to the encryption or access control of the third party wallets.

The maximum payout for a “Critical” bounty is capped at 10% of direct economic damage, primarily focusing on the funds at risk as well as branding and PR considerations at the discretion of the team with a maximum payout of __USD 2 000 000__ but with a minimum payout of __USD 50 000__. 

Payouts are handled by the __Sifchain__ team directly and are denominated in USD. However, payouts are done in __USDT__, __USDC__, __ETH__, or __BTC__, at the discretion of the team.

DeFi's leading bug bounty platform, protecting $100 billion in user funds

For Hackers

For Projects