Attackathon | Stacks II
Stacks is a Bitcoin L2 enabling smart contracts & apps with Bitcoin as the secure base layer. This Attackathon focuses on Stacks’ sBTC upgrade.
Evaluating
Triaged by Immunefi
PoC required
KYC required
This Attackathon Is Under Evaluation
Rewards
Rewards by Threat Level
Rewards Terms
Rewards are distributed among SRs according to Immunefi’s Standardized Competition Reward Terms.
Rewards are denominated in USD and distributed in STX.
The reward pool 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 either among exceptional bug reports or equally among all SRs who submit a valid report, at Stacks’ discretion. Estimated to be worth about $50,000 USD as of December 1st, 2024.
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, please visit https://sbtc.tech/
For more information about Stacks, please visit https://www.stacks.co/
Live Fixes & Duplicate Rules
Stacks’ Attackathon includes deployed code with live TVL in scope and so the code cannot be frozen because they may need to make bug fixes to protect users.
Read our full rules on live fixes & duplicate validity for this Attackathon.
Dispute Resolution
If there is any dispute over bug reports between projects and security researchers, Immunefi has final say on validity and severity based on the terms of this program.
Responsible Publication Policy
Immunefi will publish bug reports, earnings, and a leaderboard for this Attackathon. Security Researchers may publish their bug reports as well, but only after Immunefi has published the valid bug reports as part of the competition results.
KYC Requirement
Stacks requires KYC information to pay for 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
Security researchers are required to submit KYC within 14 days of KYC being requested, else their rewards may be forfeited. Immunefi may make exceptions due to extenuating
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.