Avail’s codebase can be found at [https://github.com/availproject](https://github.com/availproject). 

Documentation and further resources can be found on [https://docs.availproject.org/docs/introduction-to-avail](https://docs.availproject.org/docs/introduction-to-avail).

Avail is designed to be a platform that connects different ecosystems by providing a modular, scalable, and interoperable platform.
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.



Injection of malicious HTML or XSS through metadata

Malicious interactions with an already-connected wallet, such as:  Modifying transaction arguments or parameters Substituting contract addresses Submitting malicious transactions

Direct theft of user funds

Subdomain takeover with already-connected wallet interaction

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as:   Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Taking down the application/website

Retrieve sensitive data/files from a running server, such as:   /etc/shadow, database passwords, blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Execute arbitrary system commands

Protocol insolvency

Permanent freezing of funds

Direct theft of any user funds, whether at-rest or in-motion

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Permanent freezing of funds (fix requires hardfork)

Direct loss of funds

Unintended permanent chain split requiring hard fork (network partition requiring hard fork)

Network not being able to confirm new transactions (total network shutdown)

Primacy of Impact

Primacy of Impacy

Subdomain takeover without already-connected wallet interaction

Improperly disclosing confidential user information, such as:  Email address, Phone number, Physical address, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:  Email, Password of the victim etc.

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:  HTML injection without JavaScript, Replacing existing text with arbitrary text, Arbitrary file uploads, etc

Temporary freezing of funds

RPC API crash affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer

Causing network processing nodes to process transactions from the mempool beyond set parameters

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

Unintended chain split (network partition)

Redirecting users to malicious websites (open redirect)

Injecting/modifying the static content on the target application without JavaScript (reflected), such as:  Reflected HTML injection, Loading external site data

Changing non-sensitive details of other users(including modifying browser local storage)without already-connected wallet interaction & with up to one click of user interaction, such as: Changing the first/last name of user, Enabling/disabling notifications

Unbounded gas consumption

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk

Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network

Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours

Temporarily disabling user to access target site, such as:  Locking up the victim from login Cookie bombing, etc.

Taking over broken or expired outgoing links, such as:  Social media handles, etc.

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction & with significant user interaction, such as: Iframing leading to modifying the backend/browser state(must demonstrate impact with POC)

Modification of transaction fees outside of design parameters

Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.3](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-3/). 

__Reward 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 250,000. However, a minimum reward of USD 50,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 50,000
- Unintended permanent chain split requiring hard fork (network partition requiring hard fork) - USD 50,000
- Permanent freezing of funds (fix requires hardfork) - USD 50,000

For high Blockchain/DLT non-funds-at risk impacts, the reward will be paid out as follows: 

- Unintended chain split (network partition) - USD 20,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 20,000
- Causing network processing nodes to process transactions from the mempool beyond set parameters - USD 20,000
- RPC API crash affecting projects with greater than or equal to 25% of the market capitalization on top of the respective layer - USD 20,000

For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 500,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 50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.

__Repeatable Attack Limitations__

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. 

__Reward Calculation for High Level Reports__

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 [24h] 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:
A loss of funds involving an attack that does not require any user action
Private key or private key generation leakage leading to unauthorized access to user funds 

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.  

__Reward Payment Terms__

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

Resources & Documentation