01 / THE PURPOSE
What is Stacks for?
Stacks supports programmable applications that relate to Bitcoin without changing Bitcoin’s base-layer scripting rules. Applications execute on Stacks, while Bitcoin participates in the mechanism used to select block producers and anchor history.
02 / THE ARCHITECTURE
Three questions about the machinery.
Where do instructions run?
Execution modelSmart contracts use Clarity. They can examine Bitcoin-chain information, define assets, and apply explicit transaction post-conditions. Contract execution happens on Stacks; Bitcoin miners do not simply execute all Clarity programs.
03 / THE DESIGN CHOICES
What comes with the design?
Each architecture makes choices about security, performance, coordination, and who can participate.
Liveness depends on sufficient signers agreeing; Bitcoin continuing to produce blocks does not by itself keep Stacks applications operating.
Moving BTC into an application representation introduces peg and signer assumptions that must be assessed separately.
Clarity and transaction post-conditions can improve inspectability, but they do not eliminate mistakes in application logic.
04 / IN PRACTICE
Follow one use.
A user calls a Clarity exchange contract with a post-condition limiting the STX it may spend. The transaction is checked on Stacks, and its acceptance depends on Stacks consensus and the surrounding Bitcoin-anchored history.
05 / CHECK THE EXPLANATION
Sources & snapshot.
Network descriptions use the references below. The CoinMarketCap snapshot determines which assets are in scope and their captured rank; it does not assess the quality of a network.
- Proof of Transfer Stacks Docs
- Signing and signer responsibilities Stacks Docs
- Clarity and transaction post-conditions Stacks Docs
- CoinMarketCap top 100 snapshot Captured 14 Nov 2026 · See the complete scope audit
- Stacks (STX) on CoinMarketCap Captured asset rank #77
Profile checked 14 Nov 2026. Network designs and ranked positions can change.