Firedancer Adds 1 SOL Fee to Bug Bounty Submissions
Researchers must now burn 1 SOL to submit a bug report for the Firedancer validator software.
Updated on Oct. 24, 2026 in Cybersecurity
Live Poll
Do you believe companies should charge researchers a fee to submit software bug reports?
Firedancer has implemented a new, non-refundable 1 SOL burn requirement for all bug bounty submissions. This policy, which took effect Oct. 18, aims to reduce the volume of duplicate and low-quality reports that previously caused review delays.
Why it matters
The change seeks to manage the review backlog by deterring spam, ensuring security teams can focus on unique vulnerabilities. During the spring contest, high submission volumes led to researchers discovering bugs that had already been reported but remained unfixed.
The new requirement mandates an irreversible transfer of 1 SOL to an incinerator wallet for any submission to be considered. Submissions are limited to 3,000 characters for technical descriptions and reproduction steps.
The players
Firedancer
Firedancer is a high-performance validator client software developed for the Solana blockchain.
Jump Crypto
Jump Crypto is the digital asset division of Jump Trading Group and the primary developer behind the Firedancer project.
Solana
Solana is an open-source, decentralized blockchain network designed for high-speed transactions.
The details
Jump Crypto stated that the burned SOL is not collected as revenue. To encourage continued research, the program is offering double payouts for eligible findings and triple payouts for Alpenglow consensus issues until Nov. 20, 2026.
Timeline
April 9-May 9, 2026: Firedancer conducted its previous Immunefi bug bounty contest.
Oct. 16, 2026: Jump Crypto released a retrospective on the bug bounty.
Oct. 18, 2026: New Firedancer bug bounty terms became effective.
Nov. 20, 2026: Increased bounty payout period ends.
The Tech Race
The introduction of a financial barrier reflects a broader shift toward professionalizing security research within high-frequency blockchain infrastructure. This moves the ecosystem away from open, high-volume submission models toward more curated, incentivized bug-hunting environments.
Researchers must now weigh the financial risk of a 1 SOL burn against the potential for bounty rewards. Those submitting reports should prioritize thorough verification to avoid losing the fee on duplicate findings.
The takeaway
Implementing a fee for bug reporting serves as a filter against spam that could otherwise slow down critical security patching. Researchers should carefully review existing report logs before submitting to ensure their findings remain eligible for payout.
What happens next
The current period of increased bounty payouts for standard findings and Alpenglow consensus issues is scheduled to conclude on Nov. 20, 2026.
Further reading
Learn more about the latest developments in Cybersecurity.
Live Poll
Do you believe companies should charge researchers a fee to submit software bug reports?
