Boost | Firedancer v0.1-logo

Boost | Firedancer v0.1

Firedancer is a new validator client for Solana.

Solana
Infrastructure
Validator
C/C++

Evaluating

7d: 18h remaining
Max Bounty
$1,000,000
Rewards Pool
$1,000,000
Vault TVL
To be determined
Started
10 July 2024
Ended
21 August 2024
Rewards Token
USDC
nSLOC
200,000
  • Triaged by Immunefi

  • PoC required

  • KYC required

This Boost Is Under Evaluation

Started
10 July 2024 17:00 UTC
Ended
21 August 2024 08:00 UTC

Rewards by Threat Level

Blockchain/DLT
Critical
Portion of the Reward Pool
High
Portion of the Reward Pool
Medium
Portion of the Reward Pool
All categories *
Insight
Reward pool portion

The following reward terms are a summary; read our Firedancer v0.1 Reward Distribution Terms for the full details.

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 1 Critical severity bug is found, the reward pool will be $700,000 USD
  • If 2 Critical severity bugs are found, the reward pool will be $800,000 USD
  • If 3 or more Critical severity bugs are found, the reward pool will be $1,000,000 USD

For this Boost, duplicates are valid for a reward. Private known issues are not valid.

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 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.

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

Firedancer is a new validator client for Solana.

  • Fast - Designed from the ground up to be fast. The concurrency model is borrowed from the low-latency trading space, and the code contains many novel high-performance reimplementations of core Solana primitives.
  • Secure -The validator's architecture allows it to run with a highly restrictive sandbox and almost no system calls.
  • Independent - Firedancer is written from scratch. This brings client diversity to the Solana network and helps it stay resilient to supply chain attacks in building tooling or dependencies.

For more information about Firedancer, please visit https://firedancer-io.github.io/firedancer/

Firedancer provides rewards in USDC on Solana, which are denominated in USD.

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

Default 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.