ConstatVault
Evidence of execution

A full day at 3× sustained overload, published in its entirety

Vendors publish the runs that flatter them. We published the artifacts instead — including the ones that let you catch us if the numbers don't reconcile.

124,800

Events accepted, sealed and reconciled (of 300,000 offered)

5 / 15

Tenants and agents under concurrent load

0

Net discrepancies across the entire campaign

959,624

Bitcoin block committing the daily root — confirmed on-chain ↗

Campaign
sustained-2026-07-26
Profile
5 tenants × 100 req/s × 600 s open-loop, no backpressure relief
Signature suite
Ed25519 + ML-DSA-65 (hybrid)
Transparency
RFC 6962 Merkle, hourly → daily
Anchor
OpenTimestamps → Bitcoin block 959,624, confirmed
Verifier
truthlayer-ledger-verify (MIT)
What the campaign establishes

Four claims, each tied to an artifact rather than a sentence

Integrity held under load

Every tenant's recomputed Σ(head_index + 1) equals its on-chain count and its accepted count. Overload changed throughput; it did not change correctness.

artifact: reconciliation.json

Signatures verify, classically and post-quantum

The published verifier checks both the Ed25519 seal signature and the ML-DSA-65 hybrid signature. Both pass on the real bundle, in your browser.

artifact: seal.json + hybrid_sigs

The day is committed to Bitcoin

The daily root resolves to a confirmed Bitcoin block. Anyone with a node — and no relationship to us — can confirm the timestamp independently.

artifact: root.ots

Tampering is detectable by anyone

Change one character of one hourly root and roughly half the output bits of the daily root flip. The live tamper test lets you do exactly that.

artifact: hourly_roots[]

Reconciles byte-exactEd25519 validML-DSA-65 validAnchor confirmed
A day in the life of a dispute

An agent approves a €41,250 wire. Three weeks later, the counterparty says it never authorised it.

This is the moment the whole system exists for. Here is exactly what you hand a regulator or a court — and none of it requires ConstatVault to still exist.

  1. 01 · the actionAgent agt_settlements approves wire.transfer.approve for INV-88213 — €41,250 — under policy:treasury.v7. The event is canonicalised and hybrid-signed at write time.
  2. 02 · the chainIt links to its predecessor and head_index increments. Deleting or reordering it now breaks every event after it.
  3. 03 · the sealThe day closes into a signed daily Merkle root over 24 hourly roots — one 32-byte value committing to the whole day.
  4. 04 · the anchorThat root is timestamped into Bitcoin. The dispute arrives three weeks later; the root was mined into a block before the dispute existed.
  5. 05 · the proofYou produce an inclusion proof for that single event against the anchored root — disclosing nothing about any other event — and the counterparty's own expert runs the MIT verifier offline. Exit 0.

Not one step in that chain asks the counterparty to trust you — or to trust that ConstatVault still exists. That is the difference between a log and evidence.

Reproduce it

Everything you need is a download and one command

No sales call sits between you and the artifacts. Install the published verifier, unzip the bundle, run it offline.

npm i -g truthlayer-ledger-verify

ledger-verify --tenant-id tnt_loadtest_2feacb7576e8 \
              --agent-id agt_01KYDVT3BTEVFTQEPR0FEF1598 \
              --date 2026-07-26 --dir ./bundle

What this does not claim: that the agents made good decisions, or that the campaign resembles your workload. It establishes that the record of what happened is complete, ordered, signed and time-anchored — and that you never have to take our word for any of it.

NextHow the system is secured and operated