Ledger checkpoints
Once a day, the newest block of the TrustChain ledger is written down, sealed, and timestamped in the Bitcoin blockchain by independent calendars. Nobody, TrustChain included, can rewrite what came before without it showing.
| Day | Block | Block hash | Timestamp | Files |
|---|---|---|---|---|
| 2026-10-25 | #86 | 0xe8b60a82f31b973a51dc77e4d4cf138e8cd7b0b09cd983f204169ab715cf9743 | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
| 2026-10-24 | #80 | 0x1cbcc304bd962b3f6f1bc50d0e7eb797bd82dea0ede7a282b6fea6e50327086d | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
| 2026-10-23 | #75 | 0xb8aa2fe81fc3f9d6499f4f4a75c966f3f69bc5f83c1d1b780671a42a33e7318f | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
| 2026-10-22 | #73 | 0x2b1d00dac1b219057f4a3a8779d132c9a2235894364c09cb865ac76b17c57ebf | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
| 2026-10-21 | #70 | 0x9c8803de400a40df95a8d957d81024a91f6af5b084ac67f51313a595ede050a3 | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
| 2026-10-20 | #61 | 0x884d88ef936cb8f87f6f487eb82029d409c79caef24606b754bb46e6955c3207 | Timestamped by 2 calendars | Checkpoint file · Proof (a.pool) · Proof (b.pool) |
Check a checkpoint yourself
- Download a checkpoint file and one of its proofs into the same folder.
- Install the free OpenTimestamps client:
pip install opentimestamps-client. - Run
ots upgradeand thenots verifyon the proof. It names the Bitcoin block that proves the file existed by then. A new checkpoint needs a few hours for Bitcoin to confirm. - The block hash in the file must be the hash of that block on the ledger, which you can open in the Explorer, and every later block must chain back to it (the Explorer's Verify page checks this).