The public pin ledger · digests only
The Mirror. Checked by your browser, not by us.
Every tenant's chain head folds into one canonical checkpoint, hash-chained back to genesis, and a new checkpoint is written when the record changes. This page refolds every link in your tab with crypto.subtle, so the verdict is your browser's arithmetic.
How it works
Four steps, all public.
Chain heads fold. Each tenant's record chain has a head. Planisphere folds the heads into one canonical root.
Checkpoints chain. Each epoch digest is a SHA-256 of the epoch's content chained to the previous digest, back to genesis.
Your tab refolds. The page fetches the checkpoints and recomputes every digest with your browser's own crypto.
You read the verdict. A match on every link plus unbroken sequence numbers means chain continuity holds.
01 · Live
The checkpoints.
Loaded from the public endpoint and refolded in this tab when the page opens.
| Refold | Epoch | Created | Members | Canonical root | Epoch digest |
|---|---|---|---|---|---|
| Rows load live from the public endpoint when the page opens. | |||||
The ledger could not be fetched from this tab. The chain still exists; try again, or read it raw at api.planisphere.ooo/trust/epochs.
Rows are live, not static. If the fetch fails, the chain still exists: read it raw at api.planisphere.ooo/trust/epochs.
The arithmetic
What your browser recomputes.
epoch_digest = SHA-256(JSON({
"content": { canonical_root, epoch_seq, members_digest,
n_members, rollup_version: "1" },
"prev": prev_epoch_digest
}))
genesis prev = 0000…0000 (64 zeros)Your record
Find your record's epoch.
A record's pin names the epoch that anchors it: the same epoch_seq and canonical_root shown here. Check it on Verify, with no account.
Honest limits
What the Mirror proves, and what it doesn't.
No checkpoint was altered or removed after it was written.
It cannot show that every action was recorded.
Digests and member counts. No member identities, no record contents. Operators choose their own disclosure.
You need only this page's source and the published endpoint. To dispute it, you must dispute the math.
Questions.
How often is a checkpoint written?+
When the record changes. Quiet periods produce no new checkpoint, so gaps between epochs are normal.
Do I need an account?+
No. The ledger and Verify are public.
Is this a legal finding or certification?+
No. It shows the records have not changed since they were checkpointed.
Related: Verify a receipt · Genesis Seal #0 · Pricing