Evidence integrity and proof providers
Use integrity evidence to check whether exported session records match their recorded proof. VeriProof supports Solana and Azure SQL Ledger; the deployment selects the provider.
A recorded provider status is not an independent verification result. Export the evidence pack and run the public verifier when the review requires that check.
Provider boundary
| Provider | Recorded proof | Verification boundary |
|---|---|---|
| Solana | Session commitment, transaction reference, network, and supporting proof material | The verifier reads the recorded Solana transaction through an approved RPC endpoint |
| Azure SQL Ledger | Exact ledger row reference and ledger verification metadata | The verifier connects to the customer’s Azure SQL Database and checks protected database digests |
Solana proof transactions are public and global. Do not include session content, personal data, or secrets in a public proof transaction.
Azure SQL Ledger is not a public blockchain. Verification requires authorized database access and separately protected digests.
Submission lifecycle
VeriProof seals the session record
After the application completes the supported recording flow, VeriProof records the integrity metadata used for later checks.
The selected provider receives the commitment
Provider submission runs through the deployment’s anchoring workflow. The record can remain pending while a background worker processes or retries it.
VeriProof records the provider result
A successful provider operation records the provider-specific reference. A failed or incomplete operation remains visible for monitoring and reconciliation.
An authorized reviewer exports the evidence pack
The evidence pack contains the session files, integrity manifest, provider metadata, and the instructions needed by the public verifier.
The reviewer runs independent verification
veriproof-verify hashes the exported records and checks the selected provider without calling a VeriProof API.
Interpret status carefully
| Recorded state | Meaning | Required action |
|---|---|---|
| Pending | VeriProof has not recorded a completed provider submission | Monitor the backlog and provider health |
| Anchored | VeriProof recorded a provider reference | Run independent verification when the review requires it |
| Failed | The latest provider operation did not complete | Investigate the error and reconciliation state |
| Not anchored | The evidence pack has no completed provider proof | Do not describe the record as externally verified |
An anchored state says what VeriProof recorded. Only a successful verifier result shows that the exported files match the external provider proof at verification time.
What verification can establish
A successful verifier result establishes that the checked session files match the evidence-pack manifest and recorded provider proof. Retain the result with the package you reviewed.
If provider access fails, verification is incomplete; that is not evidence of a mismatch. Investigate the reported result before drawing a conclusion about integrity.
It does not establish that:
- the application submitted every relevant event;
- the recorded business facts were true;
- the AI system complied with a law or policy;
- the customer retained a complete chain of custody outside VeriProof; or
- the application followed a returned policy decision.
Monitor the operating path
Operators should monitor:
- pending proof submissions and their age;
- provider errors and retry activity;
- reconciliation results;
- changes to provider configuration;
- verifier access and protected digest retention; and
- evidence-pack export and retention.
Verify an export
Follow Verify exported evidence for provider-specific commands and result meanings.