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.
0blocks confirmed in Bitcoin
45blocks pending confirmation
—no block confirmed in Bitcoin yet
3calendars holding proofs
onanchoring worker
Calendars
| Calendar | Blocks held | Pending | Confirmed | Latest Bitcoin block |
|---|---|---|---|---|
https://a.pool.opentimestamps.org | 45 | 45 | 0 | — |
https://b.pool.opentimestamps.org | 45 | 45 | 0 | — |
https://finney.calendar.eternitywall.com | 45 | 45 | 0 | — |
Recent blocks
| Height | Sealed | Bitcoin status | Calendars | Proof |
|---|---|---|---|---|
| 48 | 2026-11-07 01:06:59 | queued for submission | 0 | — |
| 47 | 2026-11-07 01:04:14 | queued for submission | 0 | — |
| 46 | 2026-11-07 01:01:59 | queued for submission | 0 | — |
| 45 | 2026-11-07 00:59:14 | queued for submission | 0 | — |
| 44 | 2026-11-07 00:56:59 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 43 | 2026-11-07 00:54:14 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 42 | 2026-11-07 00:51:59 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 41 | 2026-11-07 00:49:14 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 40 | 2026-11-07 00:47:29 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 39 | 2026-11-07 00:46:44 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 38 | 2026-11-07 00:44:14 | pending confirmation | 3 | proof (.ots) · status (JSON) |
| 37 | 2026-11-07 00:41:44 | pending confirmation | 3 | proof (.ots) · status (JSON) |
Verify a proof yourself
- Download the block's proof:
curl -fsSLo block.ots https://www.a2ally.com/v1/ledger/blocks/<height>/anchor.ots - Get the block's hash from
/v1/ledger/blocks/<height>— it is the sha256 ofblock:followed by the canonical header. - Run
ots verify -d <block_hash> block.otswith 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.