● Every action signs the next
The chain is public. You can verify it.
Per-tenant chain heads. RFC 8785 JCS canonicalization in the application layer. Hourly Merkle anchors to immutable external storage. Append-only is enforced at the database role-permission level, not in application code. GDPR crypto-shred is supported by key deletion. No log line, no audit-trail-shaped object, no "just trust us."
Verify a chain entry · client-side
No server round-trip. The verification runs in your browser with SubtleCrypto. Paste a chain entry from /builds or load the bundled demo.
SHA-256 · RFC 8785 JCS · SubtleCrypto · zero round-trips
Trust chain
Three verifications. None of them ask you to trust IsoKron.
Step 1
Verify your in-database chain. The widget above does this client-side: pull a chain entry, canonicalize it, hash it, walk back. No platform trust required.
Step 2
Compare your hourly Merkle root against the published external checkpoint. Anchors are written to immutable storage on the hour. Match what your chain computes against what we published. No platform trust required.
Step 3
Verify the checkpoint signature against the published public key. The signing key's public half is published separately from our platform; the signature on each anchor is recoverable independently. No platform trust required.
There is no point in the chain where you have to trust IsoKron's claim that the data is unchanged. The verification is structural.
chain_height: pendingverified pending