Firedancer

Firedancer is a new validator client for Solana.

Fast - Designed from the ground up to be fast. The concurrency model draws from experience in 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, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.

KYC Requirement

Firedancer will be requesting KYC information in order to pay for successful bug submissions. The following information will be required:

• Full name
• Date of birth
• Proof of address (either a redacted bank statement with address or a recent utility bill)
• Copy of Passport or other Government issued ID
• Eligibility Criteria

Security researchers who wish to participate must adhere to the rules of engagement set forth in this program and cannot be:

• On OFACs SDN list
• Official contributor, both past or present
• Employees and/or individuals closely associated with the project
• Security auditors that directly or indirectly participated in the audit review

Responsible Publication

Firedancer adheres to category 3 - Approval Required. This Policy determines what information researchers are allowed to make public from their submitted bug reports. For more information about the category selected, please refer to our Responsible Publication page.

Firedancer adheres to the Primacy of Rules, meaning the whole bug bounty program is run strictly under the terms and conditions stated on this page.

Proof of Concept (PoC) Requirements

A PoC, demonstrating the bug's impact is required for this program and has to comply with the Immunefi PoC Guidelines and Rules.

Known Issue Guidelines

To ensure fairness and transparency in the bug reporting process, Firedancer is prohibited from claiming that a bug report is a known or duplicate issue without providing clear and verifiable evidence. This measure is crucial to maintaining the integrity of the bug bounty program.

Firedancer must present specific proof that an issue has been previously reported and acknowledged even if not disclosed publicly or privately as a known issue. Without such evidence, the bug report will be considered valid and eligible for the appropriate reward as per the bug bounty program terms.

For detailed information as what qualifies as acceptable proof of known issues, refer to the article on Immunefi Support: Report Closed for Known Issues.

Public Disclosure of Known Issues

Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.

• https://immunefi.com/boost/firedancer-boost/information/
• https://github.com/firedancer-io/firedancer/issues
• https://github.com/firedancer-io/firedancer/pulls
• https://github.com/firedancer-io/audits

Previous Audits

[Firedancer]’s completed audit reports can be found at https://github.com/firedancer-io/audits. Any unfixed vulnerabilities mentioned in these reports are not eligible for a reward.

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 state what security researchers, as well as projects, can or cannot cite when reviewing a bug report.

Immunefi Standard Badge

By adhering to Immunefi’s best practice recommendations, Firedancer has satisfied the requirements for the Immunefi Standard Badge

Root Cause Duplicity Exemption

If multiple distinct bugs are reported with the same root cause, they will be treated and grouped as one bug.