# a2ally Bitcoin anchoring dashboard

Every sealed ledger block's hash is submitted to public OpenTimestamps calendars, which commit it into a Bitcoin transaction. Anchoring worker: **on** · blocks submitted **179** · confirmed **132** · pending **47** · latest confirmed block #128 in Bitcoin block 974896

## Calendars
- `https://a.pool.opentimestamps.org`: 179 block(s) held, 132 confirmed, 47 pending, latest Bitcoin block 974896
- `https://b.pool.opentimestamps.org`: 179 block(s) held, 132 confirmed, 47 pending, latest Bitcoin block 974896
- `https://finney.calendar.eternitywall.com`: 179 block(s) held, 66 confirmed, 113 pending, latest Bitcoin block 974877

## Recent blocks
- Block 179 (2026-11-07): queued for submission
- Block 178 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/178/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/178/anchor
- Block 177 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/177/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/177/anchor
- Block 176 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/176/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/176/anchor
- Block 175 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/175/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/175/anchor
- Block 174 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/174/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/174/anchor
- Block 173 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/173/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/173/anchor
- Block 172 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/172/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/172/anchor
- Block 171 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/171/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/171/anchor
- Block 170 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/170/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/170/anchor
- Block 169 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/169/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/169/anchor
- Block 168 (2026-11-07): pending confirmation, 3 calendar(s), proof https://www.a2ally.com/v1/ledger/blocks/168/anchor.ots, JSON https://www.a2ally.com/v1/ledger/blocks/168/anchor

## Verify a proof
Download `https://www.a2ally.com/v1/ledger/blocks/<height>/anchor.ots` and run `ots verify -d <block_hash> a2ally-ledger-block-<height>.ots` with the OpenTimestamps client; the digest is the block's hash (sha256 of `block:` plus the canonical header). A pending proof is a calendar's signed promise, not yet buried in Bitcoin — the same `ots verify` call tells you which.

Human page: https://www.a2ally.com/anchors