Capture: Evidentia receives proof metadata from your backend. Raw AI prompts and outputs are not required by default.
Hash: The proof payload is canonicalized and hashed so later changes become detectable.
Sign: Evidentia signs the event hash and stores the public verification material.
Merkle batch: Proofs can be batched into Merkle roots so individual events can be verified against batch metadata.
Chain anchor: Developer proofs route to Solana Devnet. Foundation and higher plans route to Solana Mainnet in limited, monitored batches. Base and Ethereum providers are implemented for future rollout but are not active yet.
Public verification: Public proof pages and export packages let reviewers inspect proof metadata without receiving raw AI data.
What Evidentia can help prove
Integrity, consistency, and public evidence
A proof record was created.
The recorded proof metadata has not changed.
The signature matches the event hash and public key.
Merkle metadata is consistent when present.
Chain anchor metadata can be inspected when a live transaction exists.
What Evidentia does not prove
No overclaiming
The submitted input was factually true.
The AI decision was correct or fair.
Customer-provided source data was accurate.
A legal, regulatory, certification, or audit outcome is assured.
A demo anchor is a live mainnet transaction.
Multi-chain path
Solana first, Base and Ethereum prepared for future activation.
Open Beta uses plan-aware chain routing: Developer uses Solana Devnet, Foundation uses Solana Mainnet, Compliance prepares Base status, and Enterprise prepares Ethereum status. Only Solana Mainnet may broadcast during Open Beta; Base and Ethereum remain gated readiness paths.