Checklists

Two lists. The first is for somebody bringing pipeline A up. The second is for somebody building a client against it. Both persist in this browser and nowhere else.

Deployment

Deployment checklist

0 of 20Reset

Binding

Node 24.19.0 and npm 11.17.0 are pinnedThe engines field pins Node exactly. Other versions are untested here.The three binding values are real, not the placeholdersThe reference file ships an all zero INIT txid and spec hash. Those are not launch parameters.The namespace was derived rather than typedIt is a checksum across the whole binding. A mismatch stops the boot.The close height equals the open height plus 4,320The open height leads the INIT height by at least 1,008 blocks

Dependencies

Migrations have run against an empty, dedicated schemaNothing runs them automatically outside compose. MySQL commits DDL implicitly, so a partial migration cannot roll back.A dedicated Bitcoin Core node is reachable and reports the expected chainThe identity check is an exact string comparison, and mainnet maps to main.The node is past initial block downloadThe RPC URL is not a loopback address if the service runs in a containerSomething populates the checkpoint tableNo code path in this repository inserts a checkpoint, and readiness cannot pass without one.

Signing and trust

The Ed25519 key is loaded from a secret manager, never from source controlThe service reads raw hex from the environment and provides no file, HSM, or KMS loader.All four release identity values describe the artifacts actually runningPipeline B is a genuinely separate codebase, node, store, owner, and release processBoth trust maps are populated and verified disjointNothing in the code checks this. A signer present in both maps could satisfy both sides of the comparison alone.

Operations

Traffic is gated on readiness, not on container healthThe image health check probes liveness only and will report healthy while readiness is refusing.Access control sits in front of every routeThere is no authentication, authorization, API key, rate limiting, or CORS anywhere, including on metrics and readiness.The scrape configuration hits readiness as well as metricsThe two custom gauges only refresh as a side effect of a readiness request.Alerts exist for sustained 503 on the verified surface and for readiness going falseThe MySQL container has resource limits and hardeningThe indexer service is hardened in the reference compose file and the database service is not.Mainnet stays gated until every item above is genuinely true

Progress is kept in this browser's local storage under a single key. Clearing site data removes it, and nothing is sent anywhere.

Integration

Integration checklist

0 of 13Reset

Correctness

503 is handled as a state, not as an outage to retry throughOn the verified surface it means the two pipelines did not agree. Retrying harder does not create agreement.404 and 503 are treated as genuinely differentA missing row stays a 404 even on the verified surface, because the query error escapes ahead of verification.Cached data is stored with its verification blockData without the agreement it came with is just numbers you were once told.The interface can say that state is unconfirmedSilently showing a stale value is the failure mode the whole design exists to prevent.String counters are not parsed as JavaScript numbers without careBigint values are serialized as decimal strings on purpose.

Protocol understanding

Only a chapter increments the chapter countRecovery and a non-canonical exit do not advance the sequenceA terminal object never becomes active again except through a reorganizationFounding status can change if a reorganization moves the CREATEChapter content availability is never a validity condition

Safety

Pipeline A alone is never treated as authority for spendingThe repository states this explicitly. A missing, stale, or disagreeing tuple must block mint and protected-output spending flows.The expected protocol id is pinned and checkedA different INIT txid is a different protocol, even when every payload field looks identical.Sustained 503 raises an alert rather than being swallowed

Progress is kept in this browser's local storage under a single key. Clearing site data removes it, and nothing is sent anywhere.

Both lists are drawn from the repository’s own operational guidance and from the behaviour of the code. If an item surprises you, the page it links to explains why it is there.