ZK attestation for AI training provenance
Prove without revealing.
PROVA anchors your AI training decision log on-chain the day it is made — and lets you prove any single entry in zero knowledge when a dispute arrives, years later. The dataset stays sealed. The date is no longer yours to assert; it is consensus.
Selective disclosure, live
One root. The whole log. Disclose exactly one entry.
Below is a training-time decision log. Every entry is sealed. Its Merkle root — computed right now, in your browser, with SHA-256 — is what gets anchored on-chain. Disclose any entry: the others stay sealed, and the root does not move.
computing…
The problem
Compliance is decided in disputes — years after training.
Article 53 AI Act requires providers of general-purpose AI models to put in place a copyright policy and to identify and comply with rights reservations expressed under Article 4(3), Directive (EU) 2019/790 — the text-and-data-mining opt-out.
The question in a dispute is never whether you had a policy. It is whether you can prove what your records said, and when they said it — without opening your training corpus to the opposing party.
A database export dated today proves nothing about last year. Internal logs can be written after the fact, and everyone in the room knows it. Full disclosure proves the point but surrenders the dataset — composition, sources, scale — to a counterparty.
PROVA closes both gaps at once: the record is dated by consensus, and disclosure is measured in single entries, proven in zero knowledge.
The protocol
Commit. Anchor. Disclose.
Commit
Your decision log — every opt-out honored, every license recorded, every exclusion applied — is committed as a single Merkle root. One hash. Nothing readable, nothing leaked, nothing to subpoena.
Anchor
The root is anchored on Starknet, secured by STARK validity proofs settled to Ethereum. From that block on, the timestamp is not your assertion — it is public consensus. One honest caveat: the timestamp hardens fully once the batch settles to L1, a window of hours. Disputes under the AI Act are measured in years.
Disclose
Prove a predicate over one entry — "work W was excluded before run R" —
with a zero-knowledge proof verified against the anchored root. The rest of the log
stays sealed.
The trust boundary
What PROVA proves — and what it does not.
- Proven
- That a specific entry existed in your decision log at time T, unaltered since — and that T precedes the training run, the dispute, or any date the other side cares to name.
- Not proven
- That your training pipeline actually obeyed the entry. No attestation system can close that gap alone, and we will not pretend this one does.
But when both sides hold dated commitments, a dispute reduces to comparing dates — and the party without a verifiable record loses the argument by default.
Who anchors what
Your opt-out, dated before their training run.
Commit your reservation registry — catalogs, opt-out declarations, license terms — as it stands today. When a model ships trained on reserved work, you hold consensus-dated proof that your reservation predates the run. Per-work, without publishing the catalog.
Answer a regulator with a proof, not a data room.
Commit your compliance decisions at each training run. When Article 53 questions arrive, respond with a verifiable proof of the relevant entry — not months of discovery over your corpus, your sources, and your suppliers.
Licensing
Annual licenses. You operate your own compliance domain.
PROVA is infrastructure, not a custodian. Each licensee runs its own registry; we never hold your data, your keys, or your records.
Pilot
- Single registry, single jurisdiction profile
- Monthly on-chain anchoring
- Standard disclosure circuits
- Direct engineering support
Standard
- Multiple registries
- Scheduled anchoring per training run
- Dispute-time proof generation support
- Counterparty verification tooling
Enterprise
- Multi-jurisdiction profiles, cross-list proofs
- Custom disclosure predicates
- Legal-team integration & SLA
- Dedicated circuit review
Before 2 August
The record you anchor today is the argument you win later.
Pilots run in weeks, not quarters. Write to us with your registry shape and jurisdiction profile — we will answer with an anchoring plan.
[email protected]