An OpenAIIS checkpoint in Bitcoin block 973103
On 25 October 2026 an owner-signed checkpoint of the OpenAIIS universal registry was timestamped through OpenTimestamps and confirmed in Bitcoin. This page lists the evidence and lets you check the block headers yourself.
What was anchored
| Registry checkpoint | Tree size 1, signed by the registry operator |
|---|---|
| Checkpoint Merkle root | 56e0df9339995ff92b4de930b8745e68e2efe589e2baf1aa32475cc69f0abd39 |
| SHA-256 of the signed checkpoint note | 8b7f1c915e3afa7e1c3c0861fe8012ac03978f53d1994de25280b3f9e408cd45 |
| SHA-256 of the OpenTimestamps proof | 3c51ab7cb31d1f2bcda63dfcf8124c8054091a8670832a4ac909085ab5f696f9 |
| Bitcoin block | 973103, mined 2026-10-25 18:00:31 UTC |
| Block hash | 00000000000000000001fd3a7d7509d540d5e764e413d16acf9d07e090b8f47b |
| Confirmations when checked | 9 (the reference minimum is 6) |
| Assurance class reported | Public-source header verification: PUBLIC_SOURCE_ACTIVE_CHAIN_REPORTED_LOCAL_HEADER_POW_AND_LINKS |
The checkpoint was produced during release preparation, before the stable v1 wire profile was adopted on 26 October 2026. Historic records keep their original profile and stay verifiable under it (Protocol V5.0 §3.5).
Check the block headers
These are the raw 80-byte headers of block 973103 and the five blocks after it. Your browser hashes each one twice with SHA-256, compares it with the published block hash, checks the proof of work against its difficulty target, and checks that each header points to the one before. Nothing is downloaded or sent.
| Height | Mined (UTC) | Block hash | Hash | Work | Link |
|---|---|---|---|---|---|
| 973103 | 18:00:31 | 00000000000000000001fd3a7d7509d540d5e764e413d16acf9d07e090b8f47b | not checked | not checked | not checked |
| 973104 | 18:02:41 | 00000000000000000001628a6ee144e0a149a23e4898d790eeec2719eff565d8 | not checked | not checked | not checked |
| 973105 | 18:12:34 | 0000000000000000000088514496a84d7975689ca65df8099ac8d68177425c43 | not checked | not checked | not checked |
| 973106 | 18:22:05 | 00000000000000000000b86feab88635531cec9f8127fddfb746e4e04f7ba8f4 | not checked | not checked | not checked |
| 973107 | 18:36:31 | 000000000000000000013c3ad45c91437384a28d9b68f37299c87326aeacd794 | not checked | not checked | not checked |
| 973108 | 18:41:34 | 000000000000000000017b2368a4f98b2dc78eecf0cbf4a836d5f552773d6701 | not checked | not checked | not checked |
Show the raw headers
973103 00a0fc221b8905aaebb9ca3042191a463419e9bef9d6a001e42b01000000000000000000495505bd54687f50b4260d97c3b827dd9a5ee23b5d50730c7df6922051046eeebf43de6a930002174c1cae08 973104 00c079317bf4b890e0079dcf6ad113e464e7d540d509757d3afd01000000000000000000a782ee6c402b1eed1683a0fa423564bd6f63e1eed0910c03a3a65fc5ee53f86a4144de6a930002178321ef37 973105 00005c21d865f5ef1927ecee90d798483ea249a1e044e16e8a6201000000000000000000a3b1df6da11e6befbed5f9fa8b70b6316282ce428066fb765afc38d9c863b0499246de6a93000217203c8014 973106 00e09821435c427781d6c89a09f85da69c6875794da8964451880000000000000000000037348821ceaf3a254a133d049c6652b5c3018d6a09aa7f12d84e8ac12e3edc51cd48de6a930002175933c8b4 973107 0000f227f4a87b4fe0e446b7dffd27819fec1c533586b8ea6fb80000000000000000000041693dc09c7ed0bbac6f3656f06bc0291e8c00b602a55d1ae96cff1d88f748302f4cde6a930002176e64a43c 973108 00a0822394d7acae2673c89972f3689b8da2847343915cd43a3c010000000000000000009a3cd34ee3cfe2cd1ea7f3bb7b96745db99ed4beaf7a44a0b47e4948e1b2cb075e4dde6a9300021775e1a8df
To confirm these blocks are on Bitcoin's main chain, look up block
973103 on mempool.space
or query your own Bitcoin node with getblockheader 00000000000000000001fd3a7d7509d540d5e764e413d16acf9d07e090b8f47b.
What this does and does not show
Shown here
- The six headers are real mainnet blocks: each hash meets a difficulty of about 1.4 × 1014, so producing them took real Bitcoin mining work.
- They form one linked chain starting at block 973103.
- The reference verifier reported the checkpoint's OpenTimestamps proof committed to that block, with 9 confirmations at the time.
Not shown on this page
- The portable proof bundle (signed record, inclusion receipt, checkpoint note and
.otsfile) is not posted here yet, so you cannot re-run the commitment check from this page alone. - The assurance class relies on a public source for active-chain selection. It is not full-node consensus validation.
- Bitcoin bounds when the checkpoint existed. It does not prove authorship, legal priority, authority, consent or that any claim is true.