Stacks enables Bitcoin finality for all transactions

There is a phrase that gets thrown around a lot in crypto: “secured by Bitcoin.” Stacks is now making a more specific, more verifiable claim: every transaction on its network settles with the same finality as a Bitcoin block, because it is literally anchored to one.

That is the functional output of the Nakamoto upgrade, a hard fork that activated on the Stacks network in late October 2024, around Bitcoin block 867,867. Since then, reversing a confirmed Stacks transaction requires reorging Bitcoin itself.

What the Nakamoto upgrade actually changed

Before Nakamoto, Stacks processed transactions in its own block cadence, loosely coupled to Bitcoin but not bound to it at the state level. The upgrade restructured how Stacks organizes block production, tying each block tenure directly to a Bitcoin block.

The mechanics work like this: Stacks miners commit to a block at Bitcoin block N, and the state from that block gets written to Bitcoin at N+1. Once that next Bitcoin block arrives, all Stacks miners are required to build on that same chain tip. There is no fork path that bypasses Bitcoin’s ledger.

The result is what the Stacks ecosystem describes as 100% Bitcoin finality. Not probabilistic finality, not optimistic finality with a challenge window, but the same irreversibility guarantee that makes Bitcoin the benchmark for settlement in the first place.

Stacks runs on a Proof-of-Transfer consensus model, where miners bid Bitcoin to earn the right to produce Stacks blocks. The Nakamoto upgrade extended that connection to the ledger level, so security and state settlement are now both rooted in Bitcoin’s chain.

Smart contracts on Stacks are written in Clarity, a decidable language that does not compile to bytecode, meaning the contract behavior can be fully analyzed before execution.

sBTC and what finality enables in practice

The Nakamoto upgrade was the foundation. sBTC, which launched on mainnet in December 2024, is one of the first major products built on top of it.

sBTC is a Bitcoin-backed asset that lives on Stacks and inherits the same finality guarantee. It allows Bitcoin holders to move value into Stacks-based applications, including DeFi protocols and yield products, without wrapping through a centralized custodian or a bridging mechanism that introduces its own trust assumptions.

The finality guarantee matters here because it closes a specific attack surface. With weaker finality models, a sufficiently motivated adversary could in theory reverse a transaction after a user has already received funds on the other side of a bridge. On post-Nakamoto Stacks, that scenario requires the attacker to also reorg Bitcoin, which raises the cost of an attack to the level where it becomes economically irrational.

Bitcoin staking products are also part of the post-Nakamoto landscape, with users able to lock STX and earn Bitcoin yield through the Proof-of-Transfer mechanism. Those positions also sit under the same finality umbrella, meaning the staking records themselves carry the same settlement weight as any other confirmed Stacks transaction.

Where this lands in the competitive landscape

There are several approaches to adding programmability near Bitcoin. Some use sidechains with federated or threshold multisig bridges. Some use rollup architectures that post state roots to Bitcoin but require sequencer trust in the interim. Some use payment channel networks optimized for specific use cases rather than general computation.

Stacks’ post-Nakamoto position is distinctive because the finality claim is not conditional. There is no “assuming the bridge operators are honest” caveat, no “after the challenge period” asterisk. The settlement guarantee derives from Bitcoin’s own block production.

Block times on Stacks are tied to Bitcoin’s roughly ten-minute cadence for tenure boundaries, though block production within a tenure is faster post-Nakamoto than it was before the upgrade.

STX, the native token used for transaction fees and staking, sits at the center of the economic model. Demand for block space on Stacks, which grows as more applications and assets settle through the network, feeds directly into demand for STX.