Verify SuperChain independently.
The registry doesn’t ask you to trust it. The operator signs the chain’s current head with a published key, and anchors that signed head to Bitcoin via OpenTimestamps — so its state at a point in time is provable against a chain no one controls.
the exact signed message
superc-sth/v1 327 327 0x92834d11e482d099985ac715170ed5d5a746dcdb1c37416f23083154f6c54a89 2026-08-16T23:40:37.629Z
Each block’s hash reproduces from sha256(parent_hash + merkle_root + number + timestamp). Recompute it — it must match.
A record’s transaction hash reproduces from its sealed contents, and appears in its block’s merkle root. So the record is provably in that block.
Every block’s parent_hash equals the previous block’s hash — an unbroken chain proves the log only ever appended, never rewrote.
The head above is signed by the operator’s Ed25519 key and anchored to Bitcoin. To rewrite history, someone would have to contradict a permanent public-chain record.
A separate observer runs hourly on GitHub’s infrastructure — outside this operator’s control. It re-verifies every checkpoint’s Ed25519 signature and proves the log only ever appended, then publishes what it saw to a public, git-timestamped record. Because that record lives where the operator can’t reach it, rewriting history here would visibly contradict it. It doesn’t make the registry decentralized — it makes tampering hard to hide.