PipeFlare

What Is Stacks (STX) and How Does It Work

Learn how Stacks settles smart-contract transactions on Bitcoin, what STX does, how Proof of Transfer works, and the current rules for staking and sBTC.

By Jonathan West · Updated November 16, 2026

Stacks is a Bitcoin layer for smart contracts whose blocks settle on Bitcoin, and STX is its native token for mining incentives, transaction fees, and staking.

Stacks contracts can read Bitcoin state while running on a separate ledger, and its staking paths have different rules.

Category

Bitcoin layers

Difficulty

Intermediate

Where you'll see it

Stacks block production, STX staking documentation, and explanations of sBTC.

First introduced

The Stacks documentation lists a Stacks 2.0 mainnet launch event on January 14, 2021.

About stacks (stx)

Stacks is a Bitcoin layer for smart contracts whose blocks settle on Bitcoin, and STX is its native token for mining incentives and staking. The Stacks documentation, checked on 2026-11-16, describes how Stacks uses a separate ledger for smart-contract execution while settling transactions on Bitcoin. Stacks (STX) is easiest to understand by separating the layer from its token. Stacks runs contracts and records their results. STX pays transaction fees, supports block production, and can be locked for staking. Bitcoin (BTC) has a different role: miners commit BTC in the block-production process, while certain staking paths involve a Bitcoin bond. Older guides to "stacking" can describe rules that no longer apply. Proof of Transfer version 5 (PoX-5) replaced PoX-4 outright, released its locks, and did not move earlier positions into the new system automatically. The current paths and their restrictions are set out below.

How it actually works

Stacks connects smart-contract execution to Bitcoin without placing every Stacks transaction directly in a Bitcoin block. According to the Stacks overview, Stacks keeps its own global ledger and execution environment. That separation gives contracts a place to run without requiring added functionality in Bitcoin itself.

The Stacks documentation describes this as a deeper, ongoing connection to Bitcoin than a sidechain has. Stacks state follows Bitcoin forks. The docs say Stacks transactions get Bitcoin finality because reversing them would require reorganizing Bitcoin. The claim is about settlement. It does not say a Stacks transaction is written in full on Bitcoin.

Stacks contracts can also read Bitcoin state. A Bitcoin transaction can trigger a Stacks smart contract, and the contract can use built-in functions to inspect information from Bitcoin. Stacks uses Clarity for those contracts. The documentation describes Clarity as a safe, decidable language. Examine a particular contract before interacting with it.

The Stacks overview also contrasts Stacks with Lightning. In the docs' comparison, Lightning adds no functionality to Bitcoin and keeps no permanent state, while Stacks adds smart-contract functionality and settles to Bitcoin. Bitcoin produces a block about every 10 minutes, according to the same overview. For a separate Bitcoin price lookup, the live Bitcoin price converter covers Bitcoin only and does not quote STX.

What Proof of Transfer Does

Proof of Transfer (PoX) is the Stacks block-production mechanism. The Stacks Proof of Transfer documentation says miners spend previously mined BTC to compete for the right to produce Stacks blocks. Bitcoin proof-of-work miners spend electricity and receive BTC, while Stacks miners commit BTC and can receive newly minted STX and transaction fees.

A Stacks miner's BTC bid gives the miner a bid-weighted random chance in a single-leader election. The election takes place on Bitcoin, and the elected leader produces blocks on Stacks. The documentation calls PoX permissionless for miners: someone willing to spend BTC can participate. It also says PoX reuses work Bitcoin miners have already done and consumes no significant additional electricity.

Signers have a different job from miners. They validate and append Stacks blocks. A block is accepted when signers holding at least 70% of the weight approve it. The signer set stays fixed for a reward cycle of 2,100 Bitcoin blocks, comprising a 2,000-block reward phase and a 100-block prepare phase. Those phases matter when reading staking instructions because some actions are rejected during preparation.

PoX has had earlier versions; PoX-5 is the current version described in the Stacks documentation. PoX should also be distinguished from proof of stake: the Stacks leader election uses BTC bids on Bitcoin, while Stacks signers approve blocks using signer weight. The four roles below involve different assets and responsibilities.

Roles in Stacks Proof of Transfer, per the Stacks documentation (checked 2026-11-16)
RoleWhat they doWhat they put upWhere the docs explain it
MinersSpend BTC to compete to produce a tenure of Stacks blocks, and earn the STX coinbase plus transaction fees.BTC bidsMining
Stacks signersValidate and append blocks. Approval by signers holding at least 70% of the weight accepts a block.Signer weight from staked STXSigning
Bitcoin stakersPair a Bitcoin bond with STX under the current staking rules.BTC locked on Bitcoin layer 1, or sBTC, paired with STXBitcoin Staking
STX-only stakersStake STX to a signer-manager without a Bitcoin bond.Locked STXStaking

What STX Is Used For

STX is the native token of Stacks. The Stacks network basics documentation says newly minted STX provides an incentive for layer 2 (L2) miners. STX also provides incentives for signers involved in Bitcoin peg-outs and pays gas fees for Stacks transactions. The docs also expect most of the Stacks economy to use BTC as its economic unit once the sBTC peg is live.

The documentation treats the separate token as a deliberate design choice. It says a mining incentive needs an asset the protocol can mint, so BTC cannot serve that role. The Stacks overview also connects the token choice to maintaining decentralization without relying on a federation. These are explanations of the design in the Stacks documentation. They make no promise about STX's value.

The smallest STX unit is a micro-STX. One STX contains 1,000,000 micro-STX. This denomination describes how token amounts can be represented on Stacks; it does not change the separate roles of BTC in miner bids and STX in fees or staking.

Under the current staking rules, STX can be locked alongside a Bitcoin bond or staked without a Bitcoin leg. The two arrangements have different terms. Reading "STX staking" as a single route can therefore hide whether a position includes a BTC or sBTC bond.

How Staking Works Under the Current Rules

PoX-5 replaced PoX-4 outright, so the current STX staking paths differ from older stacking instructions. The Bitcoin Staking documentation says PoX-4 locks were released at Epoch 4.0, which activated at Bitcoin block 960,230. The docs also point to a guide on what changed in PoX-5. Positions did not migrate automatically. A former stacker who took no new action has unlocked STX and is not receiving staking rewards. Future rewards are not guaranteed either.

The Bitcoin Staking documentation describes three paths. A native BTC bond keeps timelocked BTC under the participant's own keys on Bitcoin layer 1 (L1) and pairs that bond with locked STX on Stacks. An sBTC bond pairs sBTC with STX and can be made directly or through a pool. STX-only staking locks STX without a Bitcoin bond. The native-BTC leg has no pool path, and the three paths cannot be combined into overlapping positions for the same Stacks principal.

A Stacks principal can hold one position at a time. In particular, a principal cannot hold two overlapping bonds or combine a bond with an overlapping STX-only stake. Check the principal and the intended term before choosing a path. The restriction covers overlapping positions only and does not limit how many tokens a wallet can hold.

A protocol bond is a commitment lasting 12 reward cycles, or about six months. The bond pairs a Bitcoin-side timelock with an STX lock on Stacks L2. Neither bond exit path releases the locked STX before the term ends. Someone who needs access to that STX during the term should account for the lock before entering a bond; selecting an exit path does not shorten it.

The native-BTC bond path is allowlisted through the Stacks Endowment, according to the Bitcoin Staking documentation. Joining the allowlist is an off-chain conversation with the Endowment and not an application programming interface call. The Endowment publishes bond parameters and the allowlist on-chain before a bond opens, and the docs link a page on getting allowlisted for a bond. Parameters are published roughly seven days before Day 0, and the allowlist is fixed at setup. A principal absent from that list at setup cannot join that bond. Registration is also rejected during the prepare phase, the final 100 Bitcoin blocks of a cycle.

STX-only staking has a different clock. The Stacks staking documentation permits a lock of 1 to 96 cycles, with no indefinite lock option and no per-staker minimum. An STX-only participant can request unstaking outside the prepare phase, and the STX unlocks at the start of the next cycle. Locked STX stays in the account but is unspendable at the protocol level until it unlocks. That next-cycle exit rule belongs to STX-only staking; it does not shorten a bond's 12-cycle commitment.

Every bonded or STX-only participant must be associated with a signer-manager. The participant can run one or stake to one, but the docs describe no separate solo path without a signer-manager. A signer-manager needs at least 50,000 STX staked to it in aggregate to qualify for a reward distribution. Individual STX-only stakers have no matching minimum. For background on locking tokens in other systems, see crypto staking, then use the Stacks rules for this specific decision.

The documentation says staking rewards come from BTC miners commit. STX-only rewards come from the miner BTC left after protocol bond obligations are met, so they vary and are not guaranteed. The default reward form is sBTC. A native BTC payout can instead be elected through a signer-manager. A signer-manager may also charge a fee through contract-level rules. The Stacks staking documentation says choosing a manager means reading its fee, fee ceiling, admin set, and grant status on-chain, and it points to a guide on staking to an existing signer-manager.

What sBTC Is

sBTC is a Bitcoin-pegged token used for a two-way peg between Bitcoin and Stacks. The Stacks network basics documentation describes sBTC as a decentralized, trust-minimized design with an open network of signers rather than a federation. It identifies sBTC as a fungible token compliant with Stacks Improvement Proposal 10 (SIP-010). The docs also have an sBTC section for further reading.

The peg gives Bitcoin an asset representation that Stacks contracts can use. In the current staking paths, sBTC can also serve as the Bitcoin leg of a bond, either directly or through a pool. That pool option does not extend to a native-BTC bond. A reader comparing the two bond paths should identify which asset is locked and which exit rules apply before treating them as interchangeable.

For a broader explanation of token representations, see wrapped Bitcoin. The Stacks documentation's description of sBTC supplies the rules for this particular peg. Its stated aim of reducing counterparty risk does not remove general bridge and smart-contract risks.

Is Stacks Safe? What the Risks Are

Stacks has smart-contract, peg, lockup, and permission risks that call for separate checks. The Stacks overview says Stacks transactions are secured by Bitcoin's hash power and gain Bitcoin finality. That security claim concerns the connection to Bitcoin. It does not assess every contract a reader might use or every action involved in moving an asset through a peg.

Smart contracts and two-way pegs carry general smart-contract and bridge risks. Before using a particular Stacks contract or sBTC, read the Stacks overview and the network basics documentation, which describes sBTC. The docs also have an sBTC section. The docs' description of sBTC as trust-minimized is a design claim, not a guarantee against a loss.

A lock also limits access to STX. STX-only staking leaves tokens in the account but makes them unspendable during the lock. A protocol bond fixes a 12-cycle term, and neither bond exit path releases STX early. Match the intended lock to the STX-only exit rule or the bond terms before committing a position.

Permission rules can block an otherwise planned native-BTC bond. The Stacks Endowment's allowlist process takes place off-chain, and the Bitcoin Staking documentation says a principal missing from the fixed allowlist cannot join that bond. The prepare phase blocks registration as well. Check the published bond parameters and cycle timing in the Bitcoin Staking documentation before assuming a registration will be accepted.

Signer-manager choice belongs to the staker. A manager may charge fees, and its contract has a fee ceiling, an admin set, and a grant status to examine. The Stacks staking documentation lists those on-chain terms. The docs say PoX has no slashing of locked STX, while a signer that fails to perform forfeits rewards rather than principal. Rewards remain not guaranteed. Start with the Stacks Bitcoin Staking glossary if a bond or signer term is unfamiliar.

What Would Change This Picture

A later PoX version could change the native-BTC bond entry process. The Bitcoin Staking documentation says PoX-6 is expected to remove the manual allowlist step. It describes an expected change, not a rule already in force. A revision to the allowlist, the one-position rule, or the bond terms would also change which staking actions are available. Use the current Stacks documentation to check those rules before acting.

Stacks is best understood as a Bitcoin layer that settles on Bitcoin, with STX as its mining and staking token. That takeaway serves readers deciding whether to learn more about Stacks or trying to understand how its blocks and staking paths work. It is based on the Stacks documentation. Rewards are not guaranteed, and the documentation provides no return figure to rely on here.

This page is not for anyone seeking a price, a return figure, or a recommendation to buy or stake. Such readers should read the Stacks documentation for the protocol rules and consult a qualified professional about any money decision.

This page is general information and not financial advice.

To go beyond this explainer on what Stacks (STX) is, read the current Stacks documentation and compare its staking rules with the path you want to understand.

Start here

  1. 1Read the Stacks overview and identify which functions take place on Bitcoin and which take place on Stacks.
  2. 2Use the Proof of Transfer documentation to distinguish BTC-bidding miners from block-approving signers.
  3. 3Compare the native-BTC bond, sBTC bond, and STX-only routes in the Bitcoin Staking documentation before considering a position.
  4. 4For a potential STX-only position, read what the Stacks staking documentation says about choosing a signer-manager and its fee.
  5. 5Return to the Stacks documentation for the current rules, especially if an older guide describes PoX-4.

Strengths

  • The Stacks documentation says its separate ledger runs smart contracts while transactions settle on Bitcoin, without adding functionality to Bitcoin itself.
  • The Stacks documentation says contracts can read Bitcoin state and respond to Bitcoin transactions.
  • The Stacks documentation describes an STX-only staking path with no per-staker minimum and an exit at the start of the next cycle after a valid unstaking request.

Common misunderstandings

  • PoX-4 stacking instructions describe a superseded path; PoX-5 replaced PoX-4 without automatically moving earlier positions.
  • A native-BTC bond requires an off-chain allowlist process through the Stacks Endowment, and its 12-cycle term does not release locked STX early.
  • A Stacks principal cannot hold overlapping staking positions, and STX-only rewards depend on miner BTC left after bond obligations. Rewards are not guaranteed.

Common questions

What is STX?

STX is Stacks' native token. The Stacks network basics documentation says it provides mining and peg-out signer incentives and pays Stacks transaction fees. STX can also be locked under the current staking rules.

How does Stacks work?

Stacks runs smart contracts on its own ledger while settling transactions on Bitcoin. The Stacks overview says contracts can read Bitcoin state, and the Proof of Transfer documentation says BTC bids elect Stacks block leaders on Bitcoin.

How do you stack STX today?

You use a current PoX-5 path that locks STX either alongside a Bitcoin bond or as an STX-only position. The Stacks Bitcoin Staking documentation says each principal can hold one position at a time and must be associated with a signer-manager. Bond and STX-only exit terms differ, and rewards are not guaranteed.

Is Stacks legit?

The Stacks documentation describes a Bitcoin layer, its block-production roles, and its staking rules. That documentation does not remove smart-contract, peg, lockup, or signer-manager risks. Read the current staking rules for a specific action rather than treating the existence of documentation as a safety verdict.

Is STX the same as Bitcoin?

No. The Stacks network basics documentation identifies STX as Stacks' native token for incentives and transaction fees. The Proof of Transfer documentation says miners commit Bitcoin (BTC) to compete to produce Stacks blocks.

What changed from PoX-4 to PoX-5?

PoX-5 replaced PoX-4 outright and released all PoX-4 locks. The Bitcoin Staking documentation says earlier positions did not migrate automatically, so older stacking instructions do not describe the current registration paths. The docs also link a guide on what changed in PoX-5.

Sources

Related guides

Ready to put this into practice?

Exchange sign-up bonuses pay both you and a referrer after a qualifying trade.

See bonuses →