Evidence infrastructure · not observability

When your AI agent is accused, what do you show?

Logs are testimony. Anyone with database access can change them, and everyone knows it. TrustVault turns every agent action into a signed, hash-chained, Bitcoin-anchored record — evidence a regulator, a court, or a hostile counterparty can verify without trusting you, and without contacting us.

Ed25519 + ML-DSA-65 hybridAnchored in Bitcoin block 959,624RFC 6962 Merkle transparencyMIT-licensed offline verifier
26,745,712

Events sealed under 3× sustained overload

0

Accepted events dropped. Byte-exact reconciliation.

< 1 s

To verify a full day offline, on a laptop

Verifiability horizon — the proof outlives the vendor

The gap

Everyone is monitoring agents. Nobody can prove what they did.

Observability tells you what your systems believe happened. Evidence tells a skeptical third party what did happen. Under dispute, only one of those survives cross-examination.

Mutable logs prove nothing

An append-only table is append-only until someone with credentials decides otherwise. Your adversary will say exactly that — and they'll be right.

Attestation is now a legal requirement

The EU AI Act, DORA, SEC cyber rules and sectoral regulators are converging on the same demand: demonstrate, with records, what the automated system did and under what authority.

Agents act faster than review

An autonomous agent can execute thousands of consequential actions before a human reads the first alert. Evidence must be created at write time, not reconstructed afterwards.

The design constraint: if verification requires anything from us — an API key, a running server, a company that still exists — it isn't evidence. It's a promise.

The mechanism

Four steps between an agent's action and evidence that outlives us

No new cryptography. Well-understood primitives, composed so that tampering is arithmetically impossible rather than merely against policy.

01

Every action is signed at the moment it happens

Each agent event is canonicalised and signed with a hybrid Ed25519 + ML-DSA-65 signature, then linked into a per-agent hash chain. A missing or reordered event breaks the chain immediately.

02

Hours and days compress into Merkle roots

Events fold into hourly roots, hourly roots into one daily root, using the exact RFC 6962 construction certificate transparency uses. One 32-byte value commits to the entire day.

03

The daily root is anchored to Bitcoin

The root is timestamped into the Bitcoin blockchain via OpenTimestamps. To forge a day of history you'd have to rewrite a chain we have no control over.

04

Anyone verifies it offline, forever

Auditors run our MIT-licensed verifier against a downloaded bundle. No account, no network call to us, no trust in our infrastructure — and we can't revoke the licence.

NextRead the full architecture, primitive by primitive
Evidence of execution

We ran it at 3× overload for a full day, then published everything.

Not a benchmark slide. A downloadable bundle, a public verifier, and a Bitcoin block number you can look up in a client we don't operate.

ReconcilesSignatures validAnchor confirmed

26,745,712 events. Five tenants. Zero net discrepancies.

Per tenant we recompute the sum of every agent's head_index + 1 and require it to equal both the on-chain count and the accepted count. It does — byte-exact — and you can run that arithmetic yourself in your browser in about a second.

Open the live verifier
What's in the public bundle
  • Daily seals with Ed25519 and ML-DSA-65 signatures
  • 24 hourly Merkle roots per agent-day
  • OpenTimestamps .ots proof for the anchored root
  • Reconciliation artifact for all five tenants
  • The MIT verifier, published on npm and PyPI
Download the evidence bundle
Who this is for

Built for the moment someone stops believing you

Everything works fine until it doesn't. TrustVault is priced and designed for organisations where that moment is expensive.

Regulated enterprises

Banks, insurers and healthcare operators who must show a supervisor exactly what an automated system did, and under whose authority.

artifact: signed daily seal + anchor proof

Agent platforms

Vendors selling autonomy into the enterprise, who need their customers' auditors to trust the record without trusting the vendor.

artifact: per-tenant reconciliation

Post-incident forensics

Teams reconstructing a bad hour with records that cannot be quietly improved between the incident and the review.

artifact: per-agent hash chain

Don't take our word for it. That's the entire point.

Every claim on this site is backed by an artifact you can download and a verifier you can run without us. Start there — then talk to us.