Verifying ledger bundles
How anyone can check an Intramedial ledger bundle without us, offline if they want, with the offline verifier, the /verify page or a few lines of their own code, and what each result means.
Last updated November 5, 2026.
1. Verification needs no permission and no account#
A ledger bundle can be checked by anyone who has it and our public key: a counterparty, an auditor, a court. You do not need an Intramedial account, an API key or our agreement, and you do not have to tell us you are doing it. The Verifier Terms say what a valid bundle lets you rely on.
In plain language: take the bundle, take our public key, check the root and the signature. If both match, nobody has changed the bundle since we signed it.
2. The four steps#
A ledger bundle seals a range of a workspace's audit chain. It carries the hash of each record in the range, a Merkle root over those hashes, and an Ed25519 signature over a small signed core. Every verifier, ours or yours, does the same four things:
- Recompute the root. Take the
sha256of each record in , in order, and compute the Merkle root. It must equal , and the number of records must equal .
A Trustvice ProductAgents act when the plane says yes, and the record says why.
Put admission in front of your MCP servers, repositories, SaaS tools and cloud accounts. Every agent gets a lease or a reason – and you keep the lever to stop any of them.
