contact

Every action your agent takes,
cryptographically verifiable.

Provedex signs every event your AI agent emits with Ed25519 and hash-chains it with SHA-256. The ledger is tamper-evident and anyone with the public key can verify it offline. No API call to us. No vendor trust.

see a tamper cascade github / provedex

EU AI Act, Article 12

High-risk AI systems
must keep tamper-evident logs.

Enforcement begins August 2, 2026.

Article 12 obliges providers and deployers of high-risk AI systems to record events automatically so the system's behaviour stays traceable across its lifecycle. The penalty for non-compliance is up to 15 million EUR or 3% of global revenue, whichever is higher.

Plain log files do not pass. The chain has to survive adversarial review by a regulator, by opposing counsel, by an insurer denying a claim. It has to be checkable without trusting the vendor that wrote it.

  • Hospital AI scribes. HIPAA event integrity, malpractice discovery.
  • Bank voice loan agents. OCC and CFPB review of what the model told the borrower.
  • Insurance FNOL bots. Caller disputes the words. Replay the signed chain.
  • EU enterprise risk, government. NIST AI RMF, Article 12, internal audit.
--- days
:
-- hours
:
-- minutes
:
-- seconds

until Article 12 enforcement, 2026-08-02 UTC

One ledger.
Three verbs.

Drop the SDK in next to your agent. Every event is sealed at emission. Export the ledger to anyone. The verifier is open source, runs offline, and the public key fits on a sticky note.

  1. 01 seal()

    At emission

    Every utterance, tool call, and model output is canonicalized, Ed25519-signed, and linked to the previous event by SHA-256 hash. About 3.8 ms per event. The chain only grows.

  2. 02 verify

    Offline, by anyone

    Ship the ledger and the public key. The verifier walks the chain, re-hashes each event, checks every signature. About 1 ms per 10,000 events on a laptop.

  3. 03 replay

    Reconstruct anything

    Step the ledger forward in time and replay the exact conversation. Useful for incident review, regulator questions, training-data audits.

Fast enough to leave on.

Sealing lives in the hot path of the agent loop. Verification has to be fast enough that a regulator runs it on a laptop in the room. Measured on commodity hardware, no SIMD tricks.

seal latency
3.8 ms

per signed event, p50

throughput
261 ev/s

per Ed25519 signing key

verify cost
1 ms / 10k

offline, single thread

disk footprint
320 B/event

JSONL, uncompressed

$ provedex verify ledger.jsonl --key pub.key
ok   9,124 events  chain intact  signatures valid
ok   root 7e1c2a 88b9d4 41ff03 a02e7c

Tamper with one event.
Watch the chain collapse.

Real hash chain, signed in your browser. Click any past event to flip its body. Because every event commits to the previous hash, the break cascades to every event after it. No way to hide one edit.

Click any past event to flip its body. The verifier re-hashes the chain and the break cascades to every event after it.

$ provedex verify ledger.jsonlok 10/10 signatures valid chain intact

Self-verify.
No vendor trust.

Provedex is open source under Apache-2.0. Read the threat model, run the verifier on a sample ledger, build against the SDK in an afternoon. If you ship regulated AI, we want to talk before Article 12 lands.

github / provedex hello@provedex.io
License
Apache-2.0
SDK
Rust, Python, TypeScript
Verifier
standalone CLI, 4.1 MB