Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$65,000Minimum reward to discourage security researchers from withholding a bug report:
$10,000Reward Calculation for Critical Level Reports
For Critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward USD 65 000. However, a minimum reward of USD 10 000 is to be rewarded in order to incentivize security researchers against withholding on a bug report.
For critical Blockchain/DLT bugs with a non-funds-at risk impact, the reward will be paid out as follows:
- Network not being able to confirm new transactions (total network shutdown): USD 25 000
- Unintended permanent chain split requiring hard fork (network partition requiring hard fork): USD 25 000
- Permanent freezing of funds (fix requires hardfork): USD 10 000 - USD 25 000
Reward Calculation for High Level Reports
For High Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows:
- Unintended chain split (network partition): USD 10 000
- Temporary freezing of network transactions by delaying one block by 500% or more of the average block time of the preceding 24 hours beyond standard difficulty adjustments: USD 10 000
- Causing network processing nodes to process transactions from the mempool beyond set parameters: USD 10 000
Reward Payment Terms
Payouts are handled by the Aleo team directly and are denominated in USD. However, payments are done in ALEO on Aleo Network.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability
Program Overview
Welcome to the Aleo Bug Bounty Program! We care deeply about the security of the Aleo network and want to incentivize white hat hackers and security researchers to find vulnerabilities in our core protocol.
Aleo is a developer platform that uses zero-knowledge technology to enable decentralized apps that are private, programmable, secure, and scalable. We are launching a fully permissionless, next-generation blockchain & new consensus protocol that is faster, more efficient, and more decentralized than traditional models. Aleo is more than a blockchain. It’s a new computing paradigm defined by client-side execution & cutting-edge cryptography designed for the web.
For more information about Aleo, please visit https://aleo.org/.
Aleo provides rewards in ALEO on Aleo Network, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section.
KYC Requirement
Aleo will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
- Full name
- Date of birth
- Proof of address (either a redacted bank statement with address or a recent utility bill)
- Copy of Passport or other Government issued ID
Eligibility Criteria
Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:
- On OFACs SDN list
- Official contributor, both past or present
- Employees and/or individuals closely associated with the project
- Security auditors that directly or indirectly participated in the audit review
Responsible Publication
Aleo adheres to Category 3: Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.
Primacy of Impact vs Primacy of Rules
Aleo adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page.
Proof of Concept (PoC) Requirements
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.
Previous Audits
Aleo’s completed audit reports can be found at https://aleo.org/post/aleo-completes-security-audits-of-snarkos-and-snarkvm/. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
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.
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.