Defly
Defly is a self-custody wallet which means you are the only one who has access to your private keys. Everything about Defly is designed to keep it this way, unlike most crypto exchanges.
PoC required
KYC required
Rewards by Threat Level
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, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.
All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope 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. Explanations and statements are not accepted as PoC and code is required.
Reports of Critical application bugs will be rewarded with a bounty of up to USD 100,000. We require the report demonstrates an exploit that could directly lead to a loss of funds greater than or equal to USD 50,000. The bounty amount is 10% of the total value of the affected wallets at the time the report is submitted. However, there is a minimum reward of USD 10,000 and the maximum is USD 100,000.
The Algorand Foundation has agreed to match 100% of any financial reward offered by Defly for any validated Critical or High impact vulnerability payout. The matching payout is already included in the reward amounts displayed on the program. For example, if a white hat finds a critical vulnerability and it is validated, they will be eligible to receive USD 50,000 from Defly as well as USD 50,000 from the Algorand Foundation for a total of USD 100,000.
The following vulnerabilities are not eligible for a reward:
- All vulnerabilities marked in the (‘Kudelski Security Audit’) are not eligible for a reward
KYC shall be completed for bug bounty hunters submitting a vulnerability report and requesting a reward for Critical and High Smart Contracts vulnerabilities and Critical Websites and Applications vulnerabilities. The basic information needed is full name, residential address, and passport details (DOB, issuing country and passport number). Based on the basic information submitted, Defly Wallet team may request further information at its sole discretion for compliance with applicable laws.
Additionally, all levels of bug bounty hunters submitting a vulnerability report and requesting a reward need to submit certification that (i) they are not acting, directly or indirectly, for or on behalf of any person, group entity, or nation named by any Executive Order or the United States Treasury Department as a terrorist, “Specially Designated National and Blocked Person,” or other banned or blocked person, entity, nation, or transaction pursuant to any law, order, rule or regulation that is enforced or administered by the Office of Foreign Assets Control; and (ii) they are not engaging in, instigating or facilitating this transaction, directly or indirectly, on behalf of any such person, group, entity, or nation. They also need to submit an attestation that all information provided is true, correct, up-to-date and not misleading. The collection of this information will be done by the Defly Wallet team.
Bug bounty reward payouts (including all Matching Payments and top-ups, if any) are handled by the Defly Wallet team directly and are denominated in USDCa.
Program Overview
Defly is a self-custody wallet which means you are the only one who has access to your private keys. Everything about Defly is designed to keep it this way, unlike most crypto exchanges.
For more information about Defly, please visit https://defly.app/.
The Algorand Foundation’s sponsorship of this bug bounty program will expire on 30.06.2024.
KYC required
The submission of KYC information is a requirement for payout processing.
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.