Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

01 · BATHRON in five minutes

Normative source: N-SPEC v0.7, preamble, §1.4, §7.1, §8.4; WHY-N §3, §7; APP-SPEC v1 draft §0.4. This page explains; it does not restate rules or parameter values.

BATHRON is a settlement network with its own chain, separate from Bitcoin and rooted in it. N-SPEC v0.7, preamble; WHY-N §3

A settlement needs a way to distinguish valid operations from the history in which they appear. BATHRON separates those questions. Bitcoin establishes the origins of resources. Objects carry provenance and conservation obligations. N, the consensus engine, selects a history when valid evolutions become incompatible. Selecting a history does not itself establish conservation; that also depends on the application rules. WHY-N §3

What Bitcoin contributes

Bitcoin supplies roots, verified facts, time and randomness. Each node checks Bitcoin data in the context of the Bitcoin reference block designated by an N block. A producer cannot substitute a personal account of what happened on Bitcoin. N reads Bitcoin without changing its rules. N-SPEC v0.7, preamble, point 3, §8.4, §11.1

How N chooses a history

One producer is selected for each slot from the active ticket registry, using a seed derived from Bitcoin. There is no committee, no quorum and no vote. N ranks valid chains by their production blocks and uses a public tie-break independent of block content. It selects a chain; it does not merge incompatible blocks. N-SPEC v0.7 §5.3, §5.4, §7.1, §9.3, §1.4, invariant 17; WHY-N §2

M0 and burned bitcoin

M0 is the settlement asset. Its origin is burned bitcoin. An M0 burn creates M0; a ticket burn gives production weight to a registered identity. Reactivation restores suspended participation rights. Ticket and reactivation burns create no M0. Fees transfer existing M0, and there is no block reward. A burn leaves no Bitcoin reserve that can be reclaimed. APP-SPEC v1 draft §0.4; N-SPEC v0.7 §1.4, invariants 1–4 and 12, §4.9, §6.7; WHY-N §3

Depth is a decision

There is no native finality. Inclusion starts a depth assessment. The participant delivering value outside BATHRON chooses a depth from the published table, within the published domain: the network, clock and adversary assumptions under which N's quantitative claims hold. Settlement may take hours, and conflicts may stop progress. Outside that domain, N makes no quantitative claim. WHY-N §7, §8; N-SPEC v0.7 §1.4, invariant 18, §17.1, §17.2, §17.6, §18

Who takes responsibility

Producers are registered identities selected to produce blocks. Settlement Providers handle BTC/M0; Liquidity Providers handle X/M0, where X is another asset. Providers choose their delivery depth. Builders create interfaces, users choose terms, and observers examine evidence: these are responsibilities around a service, distinct from the production role. N-SPEC v0.7 §4.1, §7.1; APP-SPEC v1 draft §0.4, §13, principle; WHY-N §7

See also

See Known limitations and How this project is built.

The N engine, Producers and tickets, Depth and statuses, Burns, Who does what, and Where trust lives.