The canonical spine is valid
End to end, the canonical chain links and hashes verify. That is the integrity claim that matters: canonical_spine_valid: true.
The IRONLEDGER · Live
A record you can check.
Constitutional actions, written down in public: witness entries, milestones, corrections, fork registrations. Not a marketing log, an audit trail. A local, hash-linked record, not a blockchain or cryptocurrency.
UNBROKENChain status
237Chain day
297Public blocks
1083Coordination pulses
The Honest Part
We keep our own seam on the record.
A governance ledger that hides its flaws is just marketing with hashes. So here is ours, in plain language, before anyone has to find it.
The strict check has a seam
A stricter, all-row legacy check fails at block 153, the documented Day 200 operational fork (policy COORD-0086). We report it as strict_table_valid: false instead of quietly dropping it.
Disclosed, not buried
The seam is named on this page and in the API. Owning a known break, in the open, is the whole point of an audit trail you can trust.
Verify It Yourself
Do not take the page's word for it.
Every claim here resolves to a live endpoint. Hit them directly, compare them to each other, and screenshot any contradiction you find.
/api/health
Worker status, chain day, block count, and the spine/strict validity flags.
/api/chain/state
Live day, block count, recent events, and active threads. Should agree with health.
/api/ironledger/verify
The verifier, including the documented strict-table seam at block 153.
Bitcoin anchors
The first chain-head proof is attested in Bitcoin block 957,512. A daily 00:00Z run is configured and awaiting its first automatic receipt.