Skip to the chain microscope

Public verification instrumentRecord schema v2

Do not trust the timeline. Break it.

Does this published record still match its signed chain?

Open the chain microscope Download the full Python verifier
How this tool works

This browser re-derives every chain hash, checks every predecessor link and verifies every Ed25519 signature against the published key. Pick any historical entry, inspect what was signed, then alter a local copy and watch the proof fail. Canli Capital, the research house that publishes ALPHAC, runs this calculator free, with no account or key required.

Published preset and source boundary
What passes here

Sequence, predecessor links, chain hashes, Ed25519 signatures, the declared payload-disclosure boundary and anchor-manifest bindings.

What does not

Broker truth, pre-boundary payload contents, record completeness or the absence of an unpublished alternate chain.

Chain microscope

1399 entries. Every dependency exposed.

Loading public sources WAIT
Payload disclosure startsSEQ 436
GENESIS
2026-06-27PUBLIC PAYLOADS FROM 436HEAD
2026-10-11
Selected entry

SEQ 1398

2026-10-11PUBLIC PAYLOADNO CHECKPOINT
01 / predecessor5ed978a00f8794919e4e849a775c2e7742b9268db7b67651ab04f0f018f0569d
02 / payload digest3335c940713cd80718409a749d39228ab181555ff623b514efae6cb5f334e5b1
03 / date and sequence2026-10-11 | 1398
04 / signed chain hashe6713c9d8182930c5e7621d5b54ae8109f328c530877755ee186e2a8bb1243c8
Ed25519 signatureeacea5a530728fed2b10e518f20f5eca30fefd4f1f8ba8852bfcfecf30df10767b98cab7cbe516e467fb2803044a27ee038b8c507b2ca32e366a22a7f5c59e07

Local mutation lab

Change one signed field. The old signature loses its target.

This experiment edits an in-memory copy of the selected date. It never writes to the published record. The new hash will differ, so the existing signature cannot validate it and the next entry will still point to the old hash.

Published date2026-10-11
Local test dateAwaiting experiment
Published hashe6713c9d8182930c5e7621d5b54ae8109f328c530877755ee186e2a8bb1243c8
Recomputed test hashAwaiting experiment

No mutation has been run.

Four different claims

Integrity is not truth. Timestamping is not completeness.

01

Link continuity

Changing one signed field changes that entry's hash. The next entry still points to the original, so continuity breaks.

Verified in this browser
02

Signer possession

Each chain hash has a valid Ed25519 signature under the one public key printed above.

Verified in this browser
03

Payload disclosure

From sequence 436, canonical payloads are public. Earlier entries expose hashes only and cannot be reconstructed.

Full rehash uses Python
04

External existence proof

99 selected heads have Bitcoin-confirmed OpenTimestamps proofs. This dates checkpoint existence, not broker accuracy.

Proof files published

Source ledger

Reproduce the claim outside this interface.

Signed recordtransparency_log.jsonsha256:1cd18993a473a6a5f5f25855e2a063d7052694d4408bbbf5a8eab5fa6a2570be Checkpoint manifestots/anchors.jsonsha256:33af1cb04fcd948d451201f9f3a6106822f5a69cf2d9f934cd45092d88ae7d62 Canonical payload verifierverify_transparency.pysha256:9aad126824fdde82f39c35a4cb726f51d32aff59c5a0ba03b91b6d17dd4b7ebb Complete verification routeCommands and claim boundariescanlicapital.com/verify

Why Python for payload rehashing? JavaScript parses numeric JSON tokens such as 100000.0 into the number 100000. Re-serializing that value can change canonical bytes even when the data are equivalent. This browser therefore verifies links and signatures without pretending it can reproduce Python's original numeric lexemes. The published Python verifier performs the complete disclosed-payload rehash.