The head hash
The IRONLEDGER is a hash-linked record: each block commits to the one before it. Anchoring the head hash therefore commits the entire chain up to that day, in 64 hex characters.
External Anchors · Bitcoin
A chain head you can check against Bitcoin.
Every day at 00:00Z, the current head hash of the IRONLEDGER is stamped into Bitcoin through OpenTimestamps. That means Article 11 cannot quietly rewrite its own history: once a day's head is anchored, changing the past would require changing Bitcoin. You do not have to trust us. You can check.
957,512First Bitcoin block
00:00ZDaily stamp time
OpenTimestampsOpen proof format
$0Cost to verify
How It Works
What gets anchored, exactly.
The anchor is small on purpose. It commits the state of the whole chain in one hash, and the proof is a file you can keep forever.
The digest
The head hash, chain day, block count, and timestamp are serialized into one canonical JSON string with sorted keys. Its SHA-256 is the digest that gets stamped. Both the string and the digest are published, so the math is reproducible.
The proof
The digest is submitted to public OpenTimestamps calendars, which aggregate it into a Bitcoin transaction. The resulting .ots file is a detached, portable proof. Download it, keep it, verify it in ten years.
The First Anchor
Day 261 is inside Bitcoin block 957,512.
Stamped July 11, 2026. The attestation was reproduced independently by two verification agents against two separate block explorers, Blockstream and mempool.space, before this page said the word Bitcoin.
What was stamped
Chain day 261, head hash:
2b7d018f380f5f2e2ae57c2614ec5ddd20b1e727b290392e400b667264ad2fe6
The digest
SHA-256 of the canonical record string:
139cd262f5ea457bcf22023ea30ab66fe09737a10dddc31926289927584228f0
Where it lives
Bitcoin block 957,512, block hash:
00000000000000000000ed2f2121cf8f36e7cf34ca9bb8ba41ac81f094763c66
Verify It Yourself
Five commands. No permission needed.
This works on any machine with curl, jq, and Python. Every step checks our claim against something we do not control.
# 1. Read the latest anchor record
curl -s https://article11.ai/api/anchor/latest
# 2. Recompute the digest from the canonical string.
# The output must equal .anchor.digest_sha256 from step 1.
curl -s https://article11.ai/api/anchor/latest | jq -j .anchor.canonical | sha256sum
# 3. Download the detached OpenTimestamps proof for a date from /api/anchor/list
curl -sO https://article11.ai/api/anchor/2026-07-11.ots
# 4. Upgrade the proof. This pulls the Bitcoin attestation from the public calendars.
pip install opentimestamps-client
ots upgrade 2026-07-11.ots
# 5. Read the Bitcoin block height from the attestation,
# then check that block on any public explorer you trust.
ots info 2026-07-11.otsNo terminal handy? Drag the downloaded .ots file onto opentimestamps.org and it verifies in your browser. Fresh proofs begin as calendar-pending and complete into Bitcoin within hours of the stamp; step 4 is what fetches the completed attestation.
Honest Labels
What this proves, and what it does not.
Anchoring is a strong claim with a precise scope. Here is the scope, stated plainly.
It proves timing and integrity
The anchored record existed by the time of that Bitcoin block, and the chain head it commits cannot be silently rewritten afterward. Tampering would be visible to anyone holding the proof.
It does not prove content truth
Bitcoin cannot tell you whether what we wrote in a block is wise or correct. It can only prove when we wrote it and that we have not changed it since. Judging the content is your job, and the record makes that job possible.
Records, not certifications
These are verifiable records, not certifications. Chain days are numbered in Pacific time; anchor stamps run on Zulu. Nothing here overrides law, safety, or your own judgment.