When sBTC mainnet opened deposits on December 17, 2024, its 1,000 BTC initial cap filled in four days. That single fact tells you most of what you need to know about 2026 BTCFi: there is real, unmet demand for putting native BTC to work on a Bitcoin-anchored smart-contract chain, and users will tolerate a federation if it ships and works.
In Part 2 we examined the validity-proof camp — Citrea, Alpen, and the BitVM2 bridges that promise near-trustless Bitcoin programmability. That future is real, but it is mostly testnet. Stacks is what is live, audited, and holding nine-figure TVL today. It is also the most honest BTCFi system about its own trust assumptions, which is why it deserves a careful look.
From Blockstack to Stacks: A Long Road to Mainnet
Stacks did not appear in the 2024 BTCFi gold rush. Muneeb Ali and Ryan Shea founded Blockstack in 2013 as a decentralized identity and storage project on top of Bitcoin. The team spent six years building infrastructure before the token sale that put them on the map: on July 10, 2019, the SEC qualified Blockstack PBC's $28M Stacks offering under Regulation A+, the first SEC-qualified retail token sale in U.S. history. The project rebranded to Stacks in 2020, and Stacks 2.0 mainnet went live on January 14, 2021 with a new consensus mechanism called Proof of Transfer (PoX) and a smart-contract language called Clarity.
Clarity matters because it is decidable: you can statically analyze any Clarity contract for cost, reachability, and certain classes of bugs before deploying it. That is a deliberate trade against the EVM's expressiveness, and it is part of why Stacks has avoided the kind of catastrophic logic exploits that plague EVM-based BTC wrappers. (ALEX, the one major Stacks DEX exploited in 2024, lost funds to a compromised admin key, not a Clarity bug.)
Proof of Transfer: BTC In, BTC Out
PoX is the consensus mechanism that anchors Stacks to Bitcoin. STX miners do not burn electricity; they transfer BTC to a set of STX holders called stackers in exchange for the right to produce Stacks blocks. Stackers lock their STX for two-week reward cycles and earn that BTC as yield. Historically, stacking APY ran 2-9% paid in BTC; post-Nakamoto it has averaged above 10%.
This design has a useful side effect: every Stacks block is, by construction, attested to in a Bitcoin transaction. A 51% attack on Stacks therefore requires 51% of Stacks miners' BTC commitments — economic weight that is denominated in the same asset Stacks is trying to anchor to. The Dual Stacking pilot launched in late 2025 extends this further by letting users stake actual BTC (not just STX) into the security model, and it had attracted over $100M and 320 BTC by Q1 2026.
Nakamoto: Five-Second Blocks, Bitcoin Finality
For its first three years, Stacks had a serious UX problem: blocks tracked Bitcoin's ~10-minute cadence, so DEX trades and lending interactions felt like 2017 Ethereum. The Nakamoto upgrade activated at Bitcoin block #867,867 on October 29, 2024 and fixed this with tenure-based block production. A miner is elected per Bitcoin block as before, but during their tenure they produce Stacks blocks roughly every 5 seconds, with each block signed by the stacker set.
The other half of Nakamoto is 100% Bitcoin finality. Once a Stacks block is buried under approximately 6 Bitcoin confirmations (~60 minutes), reorganizing it would require reorganizing Bitcoin itself. This is a stronger finality guarantee than any optimistic L2 and equivalent in spirit to what validity rollups offer once their proofs land on L1. Nakamoto also introduced ATC-C, a MEV-resistance mechanism that prevents miners from rewriting history within their own tenure. If you want to understand why this matters, our piece on how a blockchain transaction works walks through finality from first principles.
sBTC: A Threshold Federation, Honestly Labeled
sBTC is the asset that makes Stacks a BTCFi platform rather than just an interesting smart-contract chain. It is a 1:1 BTC-backed token on Stacks, minted when users deposit BTC into a federation-controlled address and burned on withdrawal.
The federation has 15 elected signers, drawn from doxxed institutions (Bitfinex, Trust Machines, Wintermute, and others). Per SIP-028, any peg-in mint or peg-out burn requires approval from at least 11 of the 15 — a 70% threshold. sBTC mainnet launched on December 17, 2024 with permissionless peg-in (anyone can deposit) and a 1,000 BTC cap that filled in four days. Phase 2, completed on April 30, 2025, made peg-out permissionless as well: any sBTC holder can redeem for native BTC without asking permission, subject to signer liveness. Phase 3, which would rotate the signer set algorithmically and reduce social trust further, is not yet live as of May 2026.
Is this trustless? No, and the Stacks team does not claim it is. It is trust-minimized: 11 of 15 doxxed institutions must collude to steal funds, and the threshold and identities are on-chain and auditable. Compared to WBTC's single custodian, this is a meaningful improvement. Compared to a future BitVM2 bridge with 1-of-N honesty assumptions, it is strictly worse cryptographically. The honest framing in Part 1's trust spectrum places sBTC firmly in the federated-bridge tier, just at the better end of it.
Q1 2026: The Numbers Behind the Narrative
Deposit caps were removed in early 2025, and sBTC TVL climbed steadily through the year. It peaked at $545M and closed Q1 2026 at $437M — a meaningful retracement, but still by far the largest live deployment of any BTCFi system. STX itself trades around $0.22 with a market cap of roughly $401M as of Q2 2026, which is worth flagging: the asset securing the bridge is worth materially less than the BTC the bridge holds. That is a real risk and we will return to it.
DeFi activity on Stacks is concentrated in a handful of protocols. Zest Protocol leads with $75.9M in deployed capital, followed by Granite at $26M, StackingDAO at $20M, and Bitflow at $5M — about $121M total. Most of this is BTC-collateralized lending and stacking liquid-staking derivatives, exactly the kinds of products that make sense for an audience that wants BTC yield without selling BTC. Our explainer on how on-chain lending and liquidations work covers the mechanics; the Stacks versions are conceptually identical to Aave with sBTC as collateral. ALEX, the dominant Stacks DEX before its 2024 admin-key exploit, has TVL under $1M and has effectively been replaced by newer venues. On the institutional side, Fireblocks and BitGo support sBTC custody, Nansen tracks it as a first-class asset, and Circle's USDC is bridged natively to Stacks.
Where Stacks Sits Versus the Alternatives
Four quick comparisons. Versus WBTC and other custodial wrappers: dramatically better — more signers, on-chain threshold, doxxed parties, permissionless peg-out. Versus validity rollups like Citrea and Alpen: worse trust model on paper, but live, audited, and processing real volume in 2026 while most validity-rollup BTC bridges are still testnet or behind training wheels. Versus emerging BitVM2 bridges: strictly worse cryptographically — a 1-of-N optimistic bridge beats an 11-of-15 federation — but BitVM2 deployments are not yet at production scale. Versus Lightning: orthogonal. Lightning is for payments; Stacks is for programmable BTC. They do not compete.
Failure Modes Worth Naming
Four risks deserve explicit attention. First, signer collusion: 11 of 15 doxxed institutions could in principle agree to steal funds. Doxxing mitigates but does not eliminate this. Second, signer liveness: if more than 5 signers go offline simultaneously, peg-outs halt until the set recovers. This has not happened in production but is a real operational risk. Third, smart-contract risk on the Clarity contracts that hold concentrated sBTC TVL — Clarity's decidability helps, but it is not magic. Fourth, the STX-BTC value asymmetry: stackers' economic security is denominated in STX, and a sharp STX price collapse weakens the cost of attacking the chain even though the underlying BTC remains in the federation's custody. There is also a smaller reorg risk during the ~6-confirmation peg-in window, which is why most integrations wait the full hour before crediting deposits.
None of these are dealbreakers. They are the kind of risks any experienced BTCFi user should understand before bridging more than they can afford to lose. If you are evaluating sBTC as a personal allocation, keeping the bulk of your BTC self-custodied in Zelcore and bridging only a working portion is the conservative play.
Looking Ahead
In Part 4 we will look at two more pieces of the BTCFi puzzle: Babylon, which lets BTC holders stake their coins to secure other proof-of-stake chains without bridging, and Rootstock, the merge-mined EVM sidechain that has quietly been the longest-running BTC smart-contract platform. Both have a different answer to the question Stacks answers with sBTC, and the trade-offs are instructive.
