sBTC

Back to Explore sBTC | sBTC is a 1:1 Bitcoin-backed asset, enabling users to put their BTC to work in DeFi, dApps, and other applications. sBTC is powered by Stacks. Stacks Bitcoin Infrastructure Blockchain Bridge Rust Clarity Bitcoin Script Maximum Bounty $250,000 Live Since 02 July 2026 Last Updated 22 October 2026 Triaged by Immunefi PoC Required KYC required Arbitration enabled Submit a Bug Information Scope Resources Rewards sBTC provides rewards in STX on Bitcoin , denominated in USD. Rewards by Threat Level Blockchain/DLT Critical Max: $250,000 Min: $25,000 Primacy of Rules High Max: $25,000 Min: $5,000 Primacy of Rules Critical Reward Calculation Reward amount is 10 % of the funds directly affected, capped at the maximum critical reward of: $250,000 Minimum reward to discourage security researchers from withholding a bug report: $25,000 The reward is dependent on the ratio between the funds at risk, which includes all affected projects on top of the respective blockchain/DLT, and the market cap according to the average between CoinMarketCap.com and CoinGecko.com, calculated at the time the bug report is submitted. Smart Contract Critical Max: $250,000 Min: $25,000 Primacy of Rules High Max: $25,000 Min: $5,000 Primacy of Rules Critical Reward Calculation Mainnet assets: Reward amount is 10 % of the funds directly affected up to a maximum of: $250,000 Minimum reward to discourage security researchers from withholding a bug report: $25,000 Primacy of Impact vs Primacy of Rules sBTC adheres to the Primacy of Rules, which means that the whole bug bounty program is run strictly under the terms and conditions stated within this page. Reward Calculation for Critical Level Reports For critical Blockchain/DLT bugs, the reward amount is 10 % of the funds directly affected , capped at the maximum critical reward $250,000 . However, a minimum reward of $25,000 is to be rewarded in order to incentivize security researchers against withholding a bug report. For critical smart contract bugs, the reward amount is 10 % of the funds directly affected up to a maximum of $250,000 . The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of $25,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report. Repeatable Attack Limitations If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25 % from the amount of the first attack for every 24 hours the attack needs for subsequent attacks from the first attack, rounded down. Reward Calculation for High Level Reports High impacts concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of $5,000 to $25,000 with the reward calculated based on 100% of the funds at risk , though capped at the maximum high reward. In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24 hours that the funds are temporarily frozen, up until a max cap of the high reward. Rewards Body Payouts are handled by the Stacks Endowment team directly and are denominated in USD. However, payments will be made in the USD equivalent in the Stacks token (STX). View impacts in scope Program Overview Stacks Endowmnent has partnered with ImmuneFi to reward honest researchers who find and responsibly disclose security vulnerabilities in our critical code. Program Response SLA sBTC defines its own response and resolution SLA's as described below: Severity │ Acknowledgement + Triage SLA │ Resolution + Payment SLA (starting from date ack'd by sBTC) Critical │ 2 weeks │ 5 weeks High │ 2 weeks │ 6 weeks Medium │ 2 weeks │ 7 weeks Low │ 2 weeks │ 8 weeks Known Issues Reports covering previously identified bugs listed below are not eligible for rewards under this program. This includes: Known issues that the project is aware of, even if no fix or code changes have been implemented. Issues the project has consciously decided not to remediate. Cases where operational mitigations or procedures have been implemented to reduce potential risk. Category Description / Link Last Updated At Blockchain/DLT │ Stacks I Attackathon 13 August 2026 Blockchain/DLT │ Stacks II Attackathon 13 August 2026 Smart Contract │ Audits 13 August 2026 Blockchain/DLT │ Audits 13 August 2026 Smart Contract │ pull requests in the sBTC 13 August 2026 Blockchain/DLT │ pull requests in the sBTC 13 August 2026 Smart Contract │ GitHub issues 13 August 2026 Blockchain/DLT │ GitHub issues 13 August 2026 Category Blockchain/DLT Description / Link Stacks I Attackathon Last Updated At 13 August 2026 Category Blockchain/DLT Description / Link Stacks II Attackathon Last Updated At 13 August 2026 Category Smart Contract Description / Link Audits Last Updated At 13 August 2026 Category Blockchain/DLT Description / Link Audits Last Updated At 13 August 2026 Category Smart Contract Description / Link pull requests in the sBTC Last Updated At 13 August 2026 Category Blockchain/DLT Description / Link pull requests in the sBTC Last Updated At 13 August 2026 Category Smart Contract Description / Link GitHub issues Last Updated At 13 August 2026 Category Blockchain/DLT Description / Link GitHub issues Last Updated At 13 August 2026 KYC required The submission of KYC information is a requirement for payout processing. Participants must adhere to the Eligibility Criteria. Proof of Concept Proof of concept is always required for all severities. Responsible Publication Category 3: Approval Required 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. Chain Rollbacks Pre-Impact Bug Monitoring Attack Investment Amount Attacks With A Financial Risk To The Attacker When Is An Impactful Attack Downgraded To Griefing? Submit a Bug Total Assets in Scope 5