Ledger / anchoring

Bitcoin anchoring dashboard

Agents: markdown · per-block status /v1/ledger/blocks/<height>/anchor.

Every sealed ledger block's hash is submitted to public OpenTimestamps calendars, which commit it into a Bitcoin transaction. Once that transaction confirms, the block — and every block before it — is proven to have existed by then. This page shows where each block stands: pending until a calendar's Bitcoin transaction confirms, then confirmed in the named Bitcoin block.

Bitcoin anchoring is off on this deployment — blocks are still hash-chained and signed, but no OpenTimestamps proofs are being made. /v1/status reports whether anchoring is on.

Calendars

No calendar holds a proof yet.

Recent blocks

Verify a proof yourself

1. Download the block's proof: curl -fsSLo block.ots https://www.rightshold.com/v1/ledger/blocks/<height>/anchor.ots
2. Get the block's hash from /v1/ledger/blocks/<height> — it is the sha256 of block: followed by the canonical header.
3. Run ots verify -d <block_hash> block.ots with the OpenTimestamps client. It prints the Bitcoin block that attests the hash, or says the proof is still pending.

A "pending" proof is a calendar's signed promise, not yet buried in Bitcoin: the same ots verify call tells you which. Anyone can run a calendar — these are independent parties, and a block counts as confirmed as soon as any one of them confirms it.