Triaged by Immunefi
Runnable PoC Required
KYC required
This Audit Competition Is Live!
$1,000,000 USD is available in rewards for finding eligible bugs in Firedancer v1 codebase of about 636,000 nSLOC.
KYC is required.
Firedancer v1 team will respond within 48 hours on weekdays to all bug reports. Any technical questions and support requests can be asked directly to Firedancer v0.1 or Immunefi in the Firedancer v0.1 Audit Competition Discord channel.
In this contest bug fixes may be applied mid-contest. Further details are in the 'Assets In Scope' section.
When the Audit Competition has ended Immunefi will publish an event-specific leaderboard and bug reports from the event.
Rewards
Rewards by Threat Level
Frankendancer codebase (code that is ONLY reachable from fdctl/fddev) is not the focus of this contest, please report issues via the standing bug bounty.
The following reward terms are a summary; read our Standardized Audit Competition Reward Terms for full context.
The reward pool will be entirely distributed among participants. The size depends on the bugs found:
- If no valid bugs are found, the reward pool will be $50,000 USD
- If no High or Critical 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 one or more Critical severity bug is found, the reward pool will be $1,000,000 USD
For this Audit Competition, duplicates are valid for a reward under the following conditions:
- Duplicate reports for the same unfixed bug are valid
- Once a fix is merged to main, new reports for that bug are invalid
- Reports submitted before the fix are still eligible
Fixes may be applied mid-contest.
Private known issues are not valid.
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms and includes All Star Pool and Podium Pool reserved for All Star Program participants.
Reward Payment Terms
Payouts are handled by the Firedancer team directly and are denominated in USD. However, payments are done in USDC on Solana.
After the event has concluded and the final bug reports have been resolved, rewards will be distributed all at once based on Immunefi’s distribution formula.
Program Overview
Firedancer is a new, independent validator client for Solana, written from scratch in C.
- Fast - Built using a low-latency, high-throughput concurrency model optimized for modern hardware.
- Secure - Tile-based sandboxing with process, thread, and memory isolation. Each tile is an independent security domain.
- Independent - A fully independent Solana protocol implementation, providing client diversity to the network.
Firedancer v1.0 is the first full, independent Solana validator client - all Agave dependencies from the v0.x hybrid client (Frankendancer) have been replaced with native C implementations.
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.