Skip to content

LibraryConsensus2024Design paperCorpus record

Stacks Nakamoto: Bitcoin-finalised block production

Stacks protocol. Stacks.

The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
4

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    Settled to Bitcoin is not 'is Bitcoin'. The execution rules are Stacks' rules. Bitcoin timestamps and anchors them.

  2. Claim 02 · Paper model

    The proposal

    The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.

  3. Claim 03 · Paper model

    The mechanism

    Miners or signers, as the docs name them, produce Stacks blocks. Bitcoin transactions anchor the result.

  4. Claim 04 · Paper model

    The bound

    This note does not quote a Bitcoin block delay as a measured latency.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    Settled to Bitcoin is not 'is Bitcoin'. The execution rules are Stacks' rules. Bitcoin timestamps and anchors them.

    Model

    What has to hold

    You are reading the Stacks docs for the Nakamoto rules. An older white paper may describe a retired mechanism.

    Falsifier

    What would retire it

    What Bitcoin reorg depth would revert a Stacks transaction?

  2. 02 The proposal

    Observation

    What the study says

    The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.

    Model

    What has to hold

    You are reading the Stacks docs for the Nakamoto rules. An older white paper may describe a retired mechanism.

    Falsifier

    What would retire it

    What Bitcoin reorg depth would revert a Stacks transaction?

  3. 03 The mechanism

    Observation

    What the study says

    Miners or signers, as the docs name them, produce Stacks blocks. Bitcoin transactions anchor the result.

    Model

    What has to hold

    You are reading the Stacks docs for the Nakamoto rules. An older white paper may describe a retired mechanism.

    Falsifier

    What would retire it

    Who can produce the next Stacks block under the page you opened?

  4. 04 The bound

    Observation

    What the study says

    This note does not quote a Bitcoin block delay as a measured latency.

    Model

    What has to hold

    You are reading the Stacks docs for the Nakamoto rules. An older white paper may describe a retired mechanism.

    Falsifier

    What would retire it

    What, exactly, is written into Bitcoin?

03 Sequence

One action, as an operating tape

  1. 01Miners or signers, as the docs name them, produce Stacks blocks. Bitcoin transactions anchor the result.
  2. 02Clarity contracts execute in Stacks' virtual machine. Bitcoin script does not run them.
  3. 03A signer set that can halt production is a liveness assumption the docs discuss. Read it as liveness, not as a footnote.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    This note does not quote a Bitcoin block delay as a measured latency.

  2. What actually moves

    The cut

    Clarity contracts execute in Stacks' virtual machine. Bitcoin script does not run them.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    This note does not quote a Bitcoin block delay as a measured latency.

  3. What a later deployment may change

    The cut

    A signer set that can halt production is a liveness assumption the docs discuss. Read it as liveness, not as a footnote.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading the Stacks docs for the Nakamoto rules. An older white paper may describe a retired mechanism.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

Anchoring is not a two-way bridge for arbitrary assets.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  1. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

Settled to Bitcoin is not 'is Bitcoin'. The execution rules are Stacks' rules. Bitcoin timestamps and anchors them.

What the design proposes

  • Miners or signers, as the docs name them, produce Stacks blocks. Bitcoin transactions anchor the result.
  • Clarity contracts execute in Stacks' virtual machine. Bitcoin script does not run them.
  • A signer set that can halt production is a liveness assumption the docs discuss. Read it as liveness, not as a footnote.

How the mechanism is specified

  • Miners or signers, as the docs name them, produce Stacks blocks. Bitcoin transactions anchor the result.
  • Clarity contracts execute in Stacks' virtual machine. Bitcoin script does not run them.
  • A signer set that can halt production is a liveness assumption the docs discuss. Read it as liveness, not as a footnote.

What this page does not treat as proven

  • This note does not quote a Bitcoin block delay as a measured latency.
  • The earlier Stacks proof-of-transfer paper is a different mechanism if the page you opened has replaced it.
  • Anchoring is not a two-way bridge for arbitrary assets.

Why the desk still reads it

The Nakamoto release of Stacks publishes block production that settles its history to Bitcoin, so a reorg of Stacks is tied to a reorg of Bitcoin rather than to a separate short fork rule.

09 Lexicon

Terms, opened into the record

Bitcoin finality
The claim that reverting this chain requires reverting Bitcoin. The claim's depth is a parameter.
Clarity
Stacks' contract language. It is not the EVM and not Bitcoin script.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.