See the wait for a seal.
Measurements from the seeded ledger, alongside explicit error-budget planning scenarios.
Loading local measurements…
Error budget scenarios
These synthetic 30-day scenarios show how the demonstration targets behave. They are separate from the local measurements above and do not state a production SLA.
What the measurements cover
Accept latency counts successful batches through the first durability barrier. Durable lag measures acceptance to persistence. Seal lag measures the wait from durable acknowledgement to the committed minute seal. These are means, and each is shown with the number of samples behind it. A count reads Not available when no local ledger is running, which is the state of this page unless you start one. No percentile estimate is inferred from a mean.
- Received batches
- Not available
- Durable records
- Not available
- Sealed records
- Not available
- Awaiting seal
- Not available
Ledger states
Four states, and they do not come from the same place. Received, Durable and Sealed are ledger facts. Searchable-through is reported by a retrieval index and is never inferred from ledger state.
- Received
- Loading…
- Durable
- Loading…
- Sealed
- Loading…
- Searchable-through
- Loading…
Follow the record, then check the proof.
Received means the request was acknowledged. Acknowledged is not durable. Durable means persisted in the configured store. Sealed means included in a signed root with a receipt.
Searchable-through: Searchable-through is not available. No search index is connected, and this watermark is never inferred from ledger state. It is a retrieval index position, not a durability state.
A missing record sequence is reported here, never skipped. When reconciliation finds a hole, the Received, Durable and Sealed watermarks stop at the last unbroken sequence.
Development signer means integrity under a published dev key and no independently trusted time.