We record what AI won't say.
Crovia is the append-only, Ed25519-signed, Bitcoin-anchored ledger of AI training-data disclosure. When a lab stays silent about what a model was trained on, we date it, sign it, and timestamp it on Bitcoin — so the absence stops being deniable and becomes a matter of public record.
Silence is the evidence nobody keeps.
The model card that named nothing
A lab ships a frontier model. The card never names a single training source. A year later, in discovery, counsel argues they "always disclosed responsibly." Who holds the timestamp that says otherwise?
The disclosure that quietly vanished
A dataset disclosure disappears from a repo after a suit is filed. Their git history is theirs to rewrite. Crovia's isn't — every prior state is signed and Bitcoin-anchored before they can touch it.
Article 53 wanted a summary
The EU AI Act requires a training-content summary. For thousands of models we monitor, that summary was absent — and Crovia can name the exact date range it stayed absent.
FMTI rates what companies choose to disclose. Ranking sites rank what's popular. Both measure presence.
Crovia is the only observatory that certifies, with a Bitcoin timestamp, what a company did not disclose — and exactly when. We call it proof of absence.
Presence is easy: it's already published. Absence is the hard part — you have to prove a negative, contemporaneously, in a way that survives cross-examination. It's the only part that holds up in court.
The LACUNA certificate
A LACUNA certificate states one cryptographically defensible fact: during a defined observation window, Crovia found no contemporaneous cryptographic attestation of expected training-data disclosure on the public surfaces it monitors — signed, dated, and anchored to Bitcoin.
How a silence becomes evidence
Autonomous collectors read model cards, docs, repos and vendor pages on a schedule — recording presence and absence of expected disclosure.
Every observation is signed with an Ed25519 key. It cannot be forged and it cannot be attributed to anyone but Crovia.
Signed observations enter an append-only ledger. Nothing is edited, nothing is deleted — the history is immutable by construction.
The ledger is hashed and timestamped on Bitcoin via OpenTimestamps. Every record is provably older than the block that confirms it.
Don't trust us. Verify us.
- Read the ledger. Every signed observation is public JSON at
/registry/data/substrate/— with the collector, timestamp and target. - Check the signature — live. Crovia's ledger seal carries an Ed25519 signature under the
crovia.substratekey. Verify it right now, in your browser — no API, no account, no Crovia server in the loop. - Confirm the Bitcoin anchor. The anchor manifest at
/registry/data/substrate/ots_anchors.jsonlists the confirmed Bitcoin blocks. Cross-check each against any block explorer. - Verify a Seal in your browser. The in-browser verifier checks CSC-1 canonicalization, hash chain and signatures with zero network calls.
Crovia Seal is an open standard — IETF Internet-Draft draft-crovia-seal. Apache-2.0 + CC0.
One cryptographic spine
When "we observed silence" isn't enough
For active litigation and regulatory work, Crovia produces courtroom-grade forensic dossiers: memorization probes on closed models, exact-edition reproduction, and per-model EU AI Act Art. 53 compliance timelines — every claim backed by a signed, anchored envelope.
Confidential · engagement letter before any work · [email protected]