Attackathon | Fuel Network
Fuel is an operating system purpose built for Ethereum Rollups. Fuel allows rollups to solve for PSI (parallelization, state minimized execution, interoperability) without making any sacrifices.
Status
Immunefi vault program
Rewards
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Fuel Attackathon Reward Terms.
The reward pool size varies based on the severity of bugs found:
-
If one or more Low severity bugs are found the reward pool will be $100,000 USD
-
If one or more Medium severity bugs are found the reward pool will be $250,000 USD
-
If one or more High severity bugs are found the reward pool will be $500,000 USD
-
If 1 Critical severity bug is found the reward pool will be $800,000 USD
-
If 2 Critical severity bugs are found the reward pool will be $900,000 USD
-
If 3 or more Critical severity bugs are found the reward pool will be $1,000,000 USD
For this Attackathon, duplicates and private known issues are valid for a reward.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Reward Payment Terms
Payouts are handled by the Fuel Network team directly and are denominated in USD. However, payments are done in USDC.
Rewards will be distributed all at once based on Immunefi’s distribution formula after the event has concluded and the final bug reports have been resolved.
Insight Rewards Payment Terms
Insight Rewards: Portion of the Rewards Pool
- The "Insight" severity was introduced on Boost & Attackathon programs to recognize contributions that extend beyond identifying immediate vulnerabilities. Currently, it's not an option to select the Insight severity when submitting a report. However, our team or program will designate it accordingly if applicable. "Insights" underscores our commitment to valuing all types of contributions that contribute to a more secure environment and will always be rewarded. View more information about Insights
Program Overview
Fuel is an operating system purpose built for Ethereum Rollups. Fuel allows rollups to solve for PSI (parallelization, state minimized execution, interoperability) without making any sacrifices.
For more information about Fuel Network, please visit https://fuel.network/
Code Update Period
From July 1st 8am UTC -to- July 6th 8am UTC the Fuel Attackathon will be in the “Code Update Period”.
- During this time the assets in-scope will be changing.
- Before this time (Epoch 1) and after this time (Epoch 2) the assets in-scope will NOT be changing.
- Any bug reports submitted during the Code Update Period will be judged based on the assets in-scope as of July 6th 8am UTC.
Fuel Network will provide a changelog and give a live technical walkthrough of the changes, their effects, and answer whitehat questions on Immunefi’s Discord at the end of the code update period.
The changelog can be found on this page, as well as in this article.
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.
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.