Chainlink
Chainlink is the industry-standard Web3 services platform. It has enabled trillions of dollars in transaction volume across DeFi, on-chain finance, gaming, NFTs, and other major industries. As the leading decentralized oracle network, Chainlink empowers developers to build feature-rich Web3 applications with seamless access to real-world data and off-chain computation across any blockchain.
PoC required
KYC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$3,000,000Minimum reward to discourage security researchers from withholding a bug report:
$100,000Rewards 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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All Smart Contracts bug reports require a proof of concept (PoC) and a suggestion for a fix to be eligible for a reward. All Websites and Applications bug reports must come with a PoC with an end-effect impacting an asset in scope in order to be considered for a reward. Explanations and statements are not accepted as PoCs and code is required.
Rewards for Critical Smart Contract vulnerabilities are at the sole and exclusive discretion of Chainlink Labs, with maximum reward of USD $3,000,000.
Specific reward amounts are determined based on a number of factors, such as the impact of proposed issues, ease of exploitability, and how likely the exploit conditions might occur.
Any supplementary reward beyond the minimum for the assigned criticality rating is at the discretion of Chainlink Labs.
KYC requirement
To ensure compliance, Chainlink Labs requires Know-Your-Customer (KYC) information to be provided for all bug bounty reporters submitting a report and requesting a reward.
The information required:
-
Color copy of passport
- Full Legal Name (First, middle, and last, plus any prefix, and/or suffix)
-
Proof of current address (either a redacted bank statement with your address or a recent utility bill with your name, address, and issuer of the bill)
-
If you are a U.S. citizen, permanent resident, partnership, LLC, corporation, estate or trust, please send a filled-out and signed W-9 (https://www.irs.gov/pub/irs-pdf/fw9.pdf)
-
If you are not a U.S. citizen or permanent resident, please send a filled-out and signed W-8BEN for individual and W-8 BEN-E for entities (https://www.irs.gov/pub/irs-pdf/fw8ben.pdf; https://www.irs.gov/pub/irs-pdf/fw8bene.pdf), and provide statement to certify that all services are performed outside of the U.S.
-
Ethereum Wallet Address (for transfer of payment)
All bug bounty reporters must pass the Office of Foreign Asset Control (OFAC) Specially Designated Nationals And Blocked Persons List (SDN) list screening. Rewards cannot be paid out if reporters are on the OFAC SDN list.
The collection and review of this information will be handled by the Chainlink Labs team directly.
Payouts are handled by the Chainlink Labs team directly, denominated in USD, and sent in Ethereum (ETH) or USD Coin (USDC).
Repeatable Attacks
In the event a report applies to multiple contracts or can be triggered multiple times, if a contract or product can be paused (either through on or off-chain means) only the impact of the first usage will be considered. If a product is not pausable such that there is no realistic way to prevent repeated usage of the attack, the entire amount at risk will be considered when evaluating impact.
Program Overview
Program Overview
Chainlink is the industry-standard Web3 services platform. It has enabled trillions of dollars in transaction volume across DeFi, on-chain finance, gaming, NFTs, and other major industries. As the leading decentralized oracle network, Chainlink empowers developers to build feature-rich Web3 applications with seamless access to real-world data and off-chain computation across any blockchain and provides global enterprises with a universal gateway to all blockchains.
Learn more about Chainlink by visiting chain.link or reading the developer documentation at docs.chain.link. To discuss an integration, reach out to an expert.
Primacy of Impact vs Primacy of Rules
Chainlink adheres to the Primacy of Impact, meaning that if you believe you have found a bug that causes an “In-scope Impact”, even if the affected system is not strictly within the assets listed, we still encourage you to submit it to the program for consideration. Chainlink adheres to the Primacy of Impact for the following severity levels:
- Smart Contract - Critical
- Smart Contract - High
- Websites and Applications - Critical
- Websites and Applications - High
KYC required
The submission of KYC information is a requirement for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
Prohibited Activities
- Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
- 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 that are executed against project assets
- Automated testing of services that generates significant amounts of traffic
- Public disclosure of an unpatched vulnerability in an embargoed bounty
- Any other actions prohibited by the Immunefi Rules
Feasibility Limitations
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report.