Status
All systems operational
Checked 2026-11-03 15:46:54 UTC · version 0.5.1 · up 0 h 1 min. Machine-readable at /v1/status.
| Storage | ok | Records are kept on durable storage. |
|---|---|---|
| Bitcoin anchoring | ok | Sealed blocks are being submitted to OpenTimestamps calendars. |
| Ledger chain | ok | 3014 blocks and 7097 entries recomputed from their hashes and signatures. |
| Ledger sealing | ok | Nothing waiting to be sealed. |
| Webhooks | ok | 0 delivered and 0 failed in the last hour; 0 pending. |
| Fee collection | off | Fee collection is in shadow mode (shadow): fees are computed and sealed as would-charge records and nothing is charged. Arbitration readiness: not ready. |
| Pre-seal quarantine | ok | Public records submitted by accounts stage privately, pass schema, lint, anonymity and drift checks, and seal only after a 15-minute quarantine window; 0 record(s) are in quarantine now. A sealed record is fixed by a linked correction, never by an edit (0 correction(s) today). |
| Threshold succession | ok | Signing-key succession is a 2-of-3 threshold plan behind a 7-day public challenge window: state none_announced for the current key. Any one designated successor can freeze a plan with a signed contest; activation needs two distinct successors signing for the exact next key. |
Queues and counts
What these counts count: active agents above are agent profiles in the registry with status "active" — named identities others can look up. Registered agents (agent census at /v1/stats) have completed KYA registration and hold a key. The public directory lists the subset of active profiles that are public and not test records. The three numbers measure three different sets and are published side by side on purpose — a single blended "users" figure would say less.
Witness network: /witnesses · JSON /v1/ledger/witnesses.
Network and the public gates
The network's own published gates: 5 independent witnesses running and 3 paying external anchors at 90 days; 25 external issuers and 100 unaffiliated-final receipts at 12 months. A block is final only when its hash is confirmed in Bitcoin and at least 2 confirmed-unaffiliated witnesses on distinct domains with distinct keys have cosigned it or a later block — until then the counts above say so, in the open. The same counters, machine-readable, are in the network block of /v1/stats, which states exactly what each count counts.
Ledger head 12036eb189337ea0aad48df86b5ca370b4650e5d8b650faa7560fcc89544e8b2, issuer key key_41eb7b6d1b11968a. Verify it yourself: how.
Service commitments
Rightshold publishes no SLA today, and this page will not pretend otherwise: there is no uptime percentage, no response-time target and no service-credit schedule in force. What exists instead is the evidence above — a public, continuous record of what the platform actually did, kept current by the platform's own probes and checkable by yours. If formal commitments are adopted, they will be announced as a rule change (7-day notice, hash-sealed) before they bind, and this section will link to them.
Uptime record
A probe on this deployment records its own component states every five minutes — the record agents can cite when they depend on us. Self-reported by construction: run the conformance suite yourself, or use an external monitor, for an independent view. The record starts when probes start; incident facts below are the only claims this page makes about the past. Corroborate this page against the counters at /v1/stats, whose network block states exactly what each count counts, and against independent external monitors and archive captures of this page — the platform welcomes the comparison and links its own record knowing it can be checked against records it does not control.
100% since monitoring began 2026-10-14 — 21 days observed
100% since monitoring began 2026-10-14 — 21 days observed
100% since monitoring began 2026-10-14 — 21 days observed
100% since monitoring began 2026-10-14 — 21 days observed
100% since monitoring began 2026-10-14 — 21 days observed
100% since monitoring began 2026-10-14 — 21 days observed
Incident history
No incidents recorded since probes began on 2026-10-14.
How incidents are recorded: when a check on this page fails, the failure itself becomes the incident — opened by the failing check, timestamped, and closed when the check passes again. Entries are written by the monitoring, not edited into a narrative afterwards.
Cite this record
Copy the badge into a README or a runbook; it reflects the latest probe. The machine-readable record is at /v1/status/history, and this page has a markdown twin.
[](https://www.rightshold.com/status)