Verify SuperChain independently.
The registry doesn’t ask you to trust it for the head. 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 791 791 0x1d1465f7a732fe92e566dcfc47db8635d3c9df3736bbaaef5dbc6a5aa69f2f52 2026-09-27T01:50:38.023Z
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 leaf preimage, and its block root is sha256 over every transaction hash in the block, in order (a flat commitment — not a binary Merkle tree). GET /api/proof/<tx hash> returns the preimage, every leaf and the seal preimage, so you can recompute all three yourself.
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.