Attackathon | Stacks
Stacks is a Bitcoin L2 enabling smart contracts & apps with Bitcoin as the secure base layer. This Attackathon focuses on Stacks’ sBTC upgrade.
Live
Triaged by Immunefi
PoC required
KYC required
This Attackathon Is Live!
A flat $250,000 USD is in rewards for finding bugs on the Stacks sBTC upgrade.
On top of the $250k, a bonus reward equal to the yield generated from 1 Million STX over 3 months will be distributed equally among all SRs who submit a valid bug report. Estimated to be worth about $50,000 USD as of December 2nd, 2024.
After the first Attackathon, a second will be launched on more new code with an additional $250,000 USD + bonus STX in rewards.
Any technical questions and support requests can be asked directly to Stacks or Immunefi in the #stacks-attackathon channel in Immunefi's Discord.
When the Stacks Attackathon ends, Immunefi will publish a leaderboard and Attackathon findings report.
Rewards
Rewards by Threat Level
The following reward terms are a summary, for the full details read our Stacks Attackathon 1 Reward Terms.
-
The reward pool size is $250,000 USD, regardless of bugs found.
-
On top of the above rewards, the yield generated from 1 Million STX over 3 months will be distributed equally among all SRs who submit a valid bug report. Estimated to be worth about $50,000 USD as of December 2nd, 2024.
Duplicates and private known issues are valid for a reward.
Program Overview
Stacks is a Bitcoin L2 enabling smart contracts & apps with Bitcoin as the secure base layer. This Attackathon focuses on Stacks’ sBTC upgrade.
For more information about sBTC and, visit https://sbtc.tech/ and https://www.stacks.co/.
This Attackathon has an audit running in parallel. Bugs in the audit report that aren't disclosed are valid for rewards.
This Attackathon’s code is/will be on mainnet during the competition. Code cannot be frozen because the project may need to immediately mitigate severe bugs in live code. The following conditions apply:
- The project will share detailed changelogs when code changes are released during the Attackathon on Discord and they will be documented in our Stacks changelog.
- Duplicates and private known issues are valid for a reward until those bugs are shared publicly.
- Read our Code Update Rules for further details on how code updates will be allowed & communicated
Responsible Publication
Security Researchers may publish their bug reports, but only after Immunefi has released all of the raw bug reports as part of the contest results, with the following exceptions:
- Bug reports in evaluation may not be published until the evaluation has concluded and the bug report is resolved.
Immunefi may publish bug reports submitted to this Attackathon, as well as a leaderboard showing the participants and their earnings.
KYC required
The submission of KYC information is a requirement for payout processing.
Additional information: Not be based or test from an OFAC-sanctioned country or region or (be a sanctioned individual or organization) as defined here: https://ofac.treasury.gov/sanctions-programs-and-country-information On OFACs SDN list
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.