Avail
Bounty Range
$1,000 - $250,000
external program
Avail
Avail is designed to be a platform that connects different ecosystems by providing a modular, scalable, and interoperable platform. Avail Nexus powers the new onchain world, beyond the boundaries of siloed blockchain networks.
Avail's vision is to provide a cohesive, unified user experience within a flexible and modular blockchain ecosystem, drawing on lessons from Web2 to innovate in Web3. Avail is not just building a product; we are pioneering a new category in the blockchain space, paving the way for an era of enhanced scalability and seamless integration.
Avail aims to provide a cohesive platform that bridges the gaps between various blockchain ecosystems. By implementing the right primitives and standards, Avail seeks to ensure interoperability and cooperation among diverse blockchain networks. This approach not only enhances the user experience but also fosters a more integrated and efficient blockchain ecosystem.
With Avail's foundational DA layer, different ecosystems can innovate on top freely, while leveraging Nexus for cross-ecosystem messaging.
Avail provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
Websites and Applications
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
For critical Blockchain/DLT bugs: The reward amount is 10% of the funds directly affected, capped at the maximum critical reward of USD 250,000. However, a minimum reward of USD 25,000 is to be rewarded in order to incentivize security researchers against withholding on a bug report. Note that critical Blockchain/DLT bugs need to be able to exploit the runtime layer of the blockchain, as the critical chain logic is strictly part of the runtime.
For critical Blockchain/DLT bugs with a non-funds-at-risk impact, the reward will be paid out as follows:
For high Blockchain/DLT non-funds-at-risk impacts, the reward will be paid out as follows:
For critical smart contract bugs: The reward amount is 10% of the funds directly affected up to a maximum of USD 250,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 25,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 5,000 to USD 20,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
For critical web/apps bug reports will be rewarded with USD 20,000, only if the impact leads to:
All other impacts that would be classified as Critical would be rewarded a flat amount of USD 6,000. The rest of the severity levels are paid out according to the Impact in Scope table.
Payouts are handled by the Avail team directly and are denominated in USD. However, payments are done in USDC on Ethereum.
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.
Avail will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria.
A PoC, demonstrating the bug's impact, is required for this program and has to comply with the Immunefi PoC Guidelines and Rules. Proof of concept is always required for all severities.
Avail's completed audit reports can be found at https://github.com/availproject/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.
Responsible Publication: Category 3: Approval Required
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:
Avail has satisfied the requirements for the Immunefi Standard Badge by adhering to Immunefi's best practice recommendations.