sBTC
- Name: sBTC
- URL: https://docs.stacks.co/learn/sbtc
- Category: Bitcoin bridge / tokenized-BTC control plane / signer-governed BTC peg
- Tags: bitcoin-ecosystem
- Summary: sBTC is a signer-governed BTC peg for Stacks. The important facts are the single peg-wallet UTXO, the bootstrap signer set, and the onchain rotation machinery. Useful control-plane comparison, not just another wrapped-BTC ticker.
- What it does:
- Issues a SIP-010 token on Stacks that represents BTC 1:1 and can be converted back to BTC on Bitcoin
- Uses a single Bitcoin peg-wallet UTXO controlled by the sBTC signer set rather than many independent vault outputs
- Assigns signers responsibility for monitoring deposits, signing mint and withdrawal operations, managing the peg UTXO, and producing Bitcoin transactions for withdrawals
- Separates sBTC signers from Stacks Nakamoto signers, making bridge custody a distinct operator layer rather than just a byproduct of base-chain consensus
- Uses onchain contracts for signer-set administration, including key rotation and threshold validation rules for the bootstrap signer set
- Key claims:
- The main sBTC docs say the system initially uses a set of 15 community-chosen signers to maintain the peg wallet and presents community governance as part of selecting that initial signer set.
- The docs say the peg wallet is always represented as a single UTXO on Bitcoin, with deposits and withdrawals consolidated to preserve that invariant.
- The signer walkthrough shows day-to-day bridge operations are highly role-specific: signer nodes watch Bitcoin and Stacks, verify deposits and withdrawals, submit signatures to Stacks contracts, and co-produce Bitcoin payout transactions.
- The signer contract docs show the signer-control plane is explicit rather than informal: key rotation is gated to the current signer principal, all pubkeys must validate, and signature thresholds must be greater than 50% and no more than 100% of the set.
- The docs repeatedly frame signers as having full democratic access to the peg wallet, which is analytically important because it makes signer-set composition and governance more central than generic
trustless BTCbranding would suggest. - The strongest reusable insight is that sBTC turns Bitcoin bridging into a signer-governance problem around a shared single-UTXO treasury, rather than a per-deposit vault problem or a pure light-client verification problem.
- Whitepaper: The official sBTC whitepaper is linked from Stacks docs at
https://stacks-network.github.io/stacks/sbtc.pdf, but the clearest primary materials for this pass were the Stacks sBTC overview and signer docs plus the sBTC repository README. See../whitepapers/sbtc-primary-sources-2026-05-13.md. - Sources:
- https://docs.stacks.co/learn/sbtc
- https://docs.stacks.co/learn/sbtc/sbtc-signers
- https://docs.stacks.co/learn/sbtc/walkthroughs/signer-process-walkthrough
- https://docs.stacks.co/learn/sbtc/clarity-contracts/sbtc-signers
- https://raw.githubusercontent.com/stacks-network/sbtc/main/README.md
- https://stacks-network.github.io/stacks/sbtc.pdf
Internal linkages
- Strongest BTC-peg control-plane peers: threshold-network and bitvm-bridge
Control surface
-
sBTC lives or dies on signer-set composition, key rotation, and the operating discipline around one shared peg-wallet UTXO.
-
The actual questions are who gets signer power, how threshold rules change, and how deposit and withdrawal batching behaves in practice, not whether the docs say
communityoften enough. -
Read it as a signer-governed BTC peg with unusually explicit treasury concentration, not as a generic wrapped-BTC note.
-
Last reviewed: 2026-06-12 UTC