sBTC: How Stacks Bridges Native Bitcoin Into DeFi Without Wrapping

Most approaches to using Bitcoin in DeFi require handing custody to a centralized entity. WBTC depends on BitGo and BiT Global. cbBTC depends on Coinbase. sBTC takes a different path: it locks BTC in a threshold signature wallet controlled by a rotating set of economically incentivized signers, then mints a 1:1 representation on Stacks. No single custodian holds the keys. No wrapped token intermediary sits between users and their Bitcoin.

The result is programmable Bitcoin: BTC that can participate in lending markets, trade on decentralized exchanges, and earn yield, all while settlement anchors back to Bitcoin L1 through Stacks' Proof of Transfer consensus. By Q1 2026, sBTC had attracted over $437 million in total value locked, with DeFi protocols on Stacks deploying $121 million in capital across lending, DEX liquidity, and yield strategies.

How the sBTC Peg Mechanism Works

The sBTC peg operates through a deposit and withdrawal cycle managed by a distributed signer set rather than a custodian. The core idea: BTC is locked on Bitcoin L1, and an equivalent amount of sBTC is minted on Stacks. When users want their BTC back, sBTC is burned and the locked BTC is released. Every sBTC in circulation is backed 1:1 by actual Bitcoin held in a threshold-controlled wallet.

Peg-In: Bitcoin to sBTC

To deposit, a user sends BTC to a special peg wallet on the Bitcoin blockchain. This wallet is controlled by the sBTC signer set through a threshold signature scheme. The signers monitor the Bitcoin blockchain for incoming deposits, verify the transaction, and mint the corresponding amount of sBTC to the depositor's Stacks address.

Deposits can be recognized in as little as one Bitcoin block (approximately 10 minutes). This speed is possible because if Bitcoin undergoes a chain reorganization after a deposit is recognized, the Stacks chain reorganizes in tandem, effectively unwinding the mint. The risk of premature recognition is absorbed by the protocol rather than the user.

Peg-Out: sBTC to Bitcoin

Withdrawals require more caution. A user initiates a withdrawal request on the Stacks chain, specifying the amount of sBTC to redeem and a destination Bitcoin address. The sBTC is locked on the Stacks side, and the signer set must reach 70% consensus to approve the withdrawal. Once approved, signers broadcast a Bitcoin transaction releasing BTC to the user's address, and the locked sBTC is burned.

The withdrawal process enforces a mandatory waiting period of six Bitcoin blocks (roughly one hour) to ensure finality and guard against chain reorganizations. Users pay the Bitcoin network fee for the release transaction. During the initial rollout, withdrawals were subject to a 150 BTC daily limit as a safety measure, though this cap has since been lifted.

Asymmetric timing by design: Deposits settle in roughly one Bitcoin block because the Stacks chain can reorg in sync with Bitcoin if needed. Withdrawals require six blocks because releasing actual BTC is irreversible: the protocol must be certain the withdrawal request is final before broadcasting on Bitcoin L1.

The Signer Set: Who Controls the Keys

The security of sBTC hinges on its signer set: the group of entities that collectively control the threshold wallet holding deposited BTC. Unlike wrapped assets that rely on a single custodian, sBTC distributes key control across multiple independent signers who must cooperate to move funds.

SIP-028 and the Election Process

The signer framework is defined by SIP-028, a Stacks Improvement Proposal approved by the community. The initial deployment launched with 15 community-elected signers, later adjusted to 14 active signers. These signers include institutional staking providers like Figment, Blockdaemon, Kiln, and Chorus One, selected based on experience running blockchain infrastructure, commitment to 99%+ uptime, and geographic distribution.

Operations require a 70% supermajority: at minimum 10 of 14 signers must approve any withdrawal or protocol action. Conversely, as long as just 5 of 15 signers behave honestly, deposited funds remain secure. This creates a meaningful gap between the liveness threshold (how many signers need to cooperate for the system to function) and the safety threshold (how many honest signers are needed to prevent theft).

Economic Incentives

Signers are not volunteers. They earn BTC rewards through Stacks' Proof of Transfer consensus mechanism by locking STX tokens and running signer nodes. The protocol enforces that signers collectively lock STX worth at least 200% of the BTC held in the peg wallet. A signer who underperforms or acts maliciously sacrifices their BTC rewards, creating direct economic alignment between signer behavior and peg integrity.

Three-Phase Decentralization Roadmap

sBTC is rolling out in phases, each expanding the signer set's decentralization:

• Phase 1 (December 2024): Deposit-only mainnet launch with 15 community-elected signers
• Phase 2 (2025): Full two-way peg with withdrawals enabled, deposit cap removed (previously capped at 5,000 BTC), minimum deposit reduced to 0.001 BTC
• Phase 3 (timeline TBD): Open, permissionless, rotating signer set integrated directly with Proof of Transfer consensus, eliminating the whitelist model entirely

The liveness ratio: The total sBTC in circulation is capped at 50% of the value of STX locked in stacking. This ensures signers always have more economic value at stake than the BTC they control. If the ratio is breached (for example, if STX price drops significantly), new peg-ins are paused until the ratio is restored.

Trust Assumptions: sBTC vs WBTC vs tBTC vs cbBTC

Every method of representing Bitcoin on another chain involves trust tradeoffs. The differences come down to who holds the keys, how many parties must collude to steal funds, and what economic incentives keep the system honest. Here is how sBTC compares to the major alternatives:

WBTC and cbBTC offer simplicity and deep liquidity on Ethereum, but both require trusting a single corporate custodian with all deposited BTC. tBTC distributes trust across a large random node set, though its security depends on the Threshold Network's T token economics rather than Bitcoin itself. sBTC occupies a middle ground: fewer signers than tBTC but with economic incentives tied directly to Stacks consensus, and a clear roadmap to open the signer set entirely.

DeFi Use Cases Enabled by sBTC

sBTC's value proposition is not just "Bitcoin on another chain." It is programmable Bitcoin within a smart contract environment that settles to Bitcoin L1. The Stacks DeFi ecosystem reached approximately $121 million in deployed capital by Q1 2026, with sBTC as the primary collateral asset.

Lending and Borrowing: Zest Protocol

Zest Protocol is the largest lending market on Stacks, with $75.9 million in TVL as of Q1 2026. Users can supply sBTC as collateral to borrow stablecoins or other assets, or lend their sBTC to earn interest denominated in BTC. Zest's V2 upgrade introduced improved capital efficiency, higher caps, and smoother liquidation mechanics.

The key differentiator from Ethereum-based lending protocols: Zest borrowers and lenders interact with actual Bitcoin-backed collateral on a chain that inherits Bitcoin finality, rather than a custodial token on an independent consensus mechanism.

Decentralized Exchanges: ALEX and Bitflow

ALEX is the primary DEX on Stacks, offering token swaps, liquidity pools, and a yield farming program (the Surge campaign) that rewards sBTC liquidity providers with additional ALEX tokens on top of swap fees. Bitflow provides a complementary DEX experience focused on stable swaps and optimized routing.

Both platforms enable sBTC holders to provide liquidity and earn fees without leaving the Stacks ecosystem. Because Stacks produces blocks every few seconds post-Nakamoto (compared to Bitcoin's 10-minute blocks), DEX trading operates at speeds comparable to other L2 environments.

Yield Strategies

Beyond lending and trading, the sBTC ecosystem offers several yield paths:

• sBTC Rewards Program: Holders earn up to 5% APY in BTC rewards simply by holding sBTC, funded by Stacks ecosystem incentives
• Stacking yield: Supplying sBTC to protocols like Zest can earn 1-2% additional APY on top of the base rewards
• Granite Protocol: A borrowing/lending protocol with $26 million in TVL, offering BTC-denominated yield
• StackingDAO: Liquid stacking derivatives with $20 million in TVL, enabling users to earn stacking rewards while keeping sBTC liquid for DeFi

The Nakamoto Upgrade: Why sBTC Needed New Consensus

sBTC could not have launched under Stacks' original consensus rules. The Nakamoto upgrade, which activated in October 2024, introduced two critical changes that made the sBTC peg viable.

Bitcoin Finality

Pre-Nakamoto, Stacks blocks could be reorganized independently of Bitcoin. This made it impossible to build a reliable peg: an attacker could deposit BTC, receive sBTC, then trigger a Stacks reorg to erase the mint while keeping the BTC. The Nakamoto upgrade ties Stacks finality directly to Bitcoin blocks. Once a Stacks transaction is confirmed and the corresponding Bitcoin block is mined, it cannot be reversed without also reversing Bitcoin itself.

Faster Block Production

The upgrade also moved Stacks from one block per Bitcoin block (approximately 10 minutes) to producing blocks every few seconds. This makes DeFi interactions practical: swapping, lending, and providing liquidity require fast confirmation times that the old cadence could not support.

Risks and Open Questions

sBTC represents a meaningful improvement over centralized custody for Bitcoin bridging, but it introduces its own set of risks that users should understand.

Signer Collusion

The 70% threshold means that if 10 of 14 signers collude, they could theoretically steal all deposited BTC. The economic deterrent is the 200% STX collateral requirement: signers have more value at stake than the BTC they control. However, this deterrent depends on the market value of STX. If STX price drops sharply relative to BTC, the economic security ratio weakens, though the liveness ratio mechanism pauses new deposits before the ratio fully inverts.

Stacks Consensus Dependency

sBTC's security is ultimately tied to Stacks consensus. A critical bug in the Stacks node software, a sustained network outage, or a failure in the Proof of Transfer mechanism would affect sBTC operations. While the Nakamoto upgrade improved reliability and introduced Bitcoin finality, Stacks remains a younger and less battle-tested network than Bitcoin or Ethereum. The March 2026 network upgrade (3.3.0.0.6) and upcoming SIP034 enhancements aim to improve throughput by up to 30x, but each upgrade introduces its own integration risk.

Peg Stability Under Stress

sBTC's 1:1 peg is maintained by the guarantee that any sBTC can be redeemed for actual BTC through the withdrawal process. But during periods of high demand, withdrawal queues, network congestion, or signer downtime could create temporary deviations from the peg on secondary markets. The initial 150 BTC daily withdrawal cap demonstrated this tension: safety measures that protect the system can also constrain liquidity when users need it most.

Centralization During Transition

Until Phase 3 delivers a fully open signer set, sBTC operates with a permissioned group of 14 signers. This is more decentralized than WBTC or cbBTC, but less decentralized than other Bitcoin L2 approaches that inherit Bitcoin's full validator set. The transition to permissionless signing has no firm timeline, and its success depends on sufficient STX staking participation and signer diversity.

sBTC and Spark: Different Paths for Bitcoin Utility

Both sBTC and Spark share the same fundamental goal: making Bitcoin more useful beyond Layer 1. But they solve different problems with distinct architectures.

sBTC bridges BTC into a smart contract environment. It creates a programmable representation of Bitcoin that can interact with lending protocols, DEXs, and yield strategies on Stacks. The tradeoff is that users move their BTC into a threshold-controlled wallet and receive a derivative token, even if that token is trustlessly redeemable.

Spark takes a different approach entirely. Rather than creating a wrapped or pegged representation, Spark uses statechains and FROST threshold signatures to transfer ownership of actual BTC without broadcasting on-chain transactions. There is no bridge, no derivative token, and no smart contract environment. Instead, Spark focuses on instant, self-custodial payments: sending and receiving native Bitcoin at Lightning speed without channel management.

The two protocols are complementary rather than competing. A user who wants to earn yield on their BTC through DeFi might use sBTC. A user who wants to send Bitcoin instantly to a friend might use Spark. Both expand what Bitcoin holders can do without trusting a centralized custodian.

What to Watch

sBTC's trajectory depends on several open questions:

• Phase 3 timing: When the signer set becomes fully open and permissionless, the trust model changes fundamentally. This is the most important milestone for sBTC's long-term credibility
• STX price correlation: The liveness ratio ties sBTC capacity to STX market value. A sustained STX decline could cap sBTC growth regardless of demand
• DeFi ecosystem depth: With $121 million in deployed capital, Stacks DeFi is growing but remains small compared to Ethereum. sBTC's utility depends on this ecosystem expanding
• Competition from other Bitcoin L2s: Projects like Citrea, Botanix, and Babylon offer alternative approaches to Bitcoin DeFi, each with different trust and performance tradeoffs

For developers building on Bitcoin, the Spark SDK offers a complementary toolkit: instant self-custodial payments that work alongside DeFi-focused protocols like sBTC. For a broader look at how Bitcoin L2s compare, see our Bitcoin Layer 2 comparison.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.