▸ ARCHITECTURE · ONE TEMPLATE THROUGH THE GATEWAY

Six steps. One template. Every named code on the way through.

The Failure Atlas tells you what has gone wrong. The Q&A tells you what to expect. This page tells you the path a single block template walks through ReserveGrid OS — from ingress at the SV2 gateway, through independent re-derivation with rust-bitcoin, into Class D declared-versus-derived checks, into Class M mempool ground truth, and out to the miner pool — with the reason-code surface named at every stage. Drag the scrubber, or let it play.

▸ ARCHITECTURE · WALKTHROUGH

One template. Six stops.

Scrub the timeline to walk a template through the gateway. Pause to read the panel; resume to keep moving. Every claim on this page maps to a published reason code or a [policy.*] key.

1
T+0 · Ingress
2
Class S
3
Class D
4
Class M
5
Verdict
6
Egress
Phase 1 · L1

A template arrives.

Stratum V2 NewTemplate frame from the operator’s template-manager. Header + coinbase + transaction digests.

rg-consensus parses the frame and hands the structural pieces to its re-derivation facade.

STEP 01 / 06
▸ WHAT TO READ NEXT
Failure Atlas →
Real incidents — what each layer of this pipeline would have caught, with the named reason code.
Q&A · Operator evaluation →
Six blunt questions in order: what it does, what it tells you, how to configure, cost & license, why-not-existing-tools, and what’s WIRED today.
Product surface →
Reason-code map · TOML keys · telemetry · adoption modes · roadmap. The full operating surface.