Back to corpus
architecturetechnical paper candidatescore 34

Research: Stacks Appchain Architecture -- Deep Technical Analysis

Stacks appchains are independent blockchain instances that use the same protocol, transaction format, and Clarity smart contract language as the main Stacks chain, but mine on top of Stacks (or another appchain) rather than Bitcoin directly. They inherit Bitcoin's security through a hierarchical Proof of Transfer (PoX) chain: Bitcoin -> Stacks -> Appchain. The stacks-core codebase is a large Rust monorepo (~94% Rust, 31K+ commits, 135 contributors, GPL v3) with 12+ crates. Forking it is feasible but non-trivial --

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

Stacks appchains are independent blockchain instances that use the same protocol, transaction format, and Clarity smart contract language as the main Stacks chain, but mine on top of Stacks (or another appchain) rather than Bitcoin directly. They inherit Bitcoin's security through a hierarchical Proof of Transfer (PoX) chain: Bitcoin -> Stacks -> Appchain. The stacks-core codebase is a large Rust monorepo (~94% Rust, 31K+ commits, 135 contributors, GPL v3) with 12+ crates. Forking it is feasible but non-trivial -- the complexity is comparable to forking Bitcoin Core or Geth, not a simple SDK instantiation like Cosmos. Adding custom first-class features (like GPU compute proof / APOP) is technically possible at the Clarity VM level, the consensus level, and the boot code level, but requires deep Rust engineering in the stacks-core codebase. An appchain is a **separate Stacks blockchain instance** that uses Stacks (or another appchain) as its "host chain" instead of Bitcoin directly. Every appchain is a full Stacks blockchain -- same protocol, same transaction format, same Clarity VM, everything. > "Appchains are just more Stacks blockchains with the same protocol, same transaction format, and same Clarity smart contract language as the main Stacks chain." -- Jude Nelson (Stacks Foundation Lead) | Degree | Chain | Host Chain | |--------|-------|------------| | 0 | Bitcoin | (base layer) | | 1 | Stacks | Bitcoin | | 2 | Appchain | Stacks | | 3+ | Appchain-on-appchain | Another appchain | The system supports approximately **4.2 billion total appchains** organized in tiers, with logarithmic separation degrees between any appchain and Bitcoin.

Promotion decision

What has to happen next

Promote into a technical note or architecture paper with implementation anchors.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.