Exported files
The signed inventory identifies each file, its fingerprint, and its byte length. The verifier rejects a package whose files do not match that inventory.
Technical brief
How VeriProof checks evidence integrity
A decision record is only worth what a stranger can verify. This paper walks through how an exported record is signed, fingerprinted, and checked, so a reviewer who does not trust us can still trust the evidence.
Keep the record and the integrity check together
A review starts with the decision. The next question is whether the evidence has changed since it was recorded.
VeriProof connects selected session records to a signed export and a separate proof reference. Reviewers can examine the decision and check its evidence together.
Start with the content being checked
SHA-256 fingerprints represent the content covered by the integrity contract. The verifier recalculates them instead of relying on a stored fingerprint alone.
Source record fingerprints
Session content and inclusion proofs connect the export to its source commitments. The external provider gives the verifier a separate reference to check.
A fingerprint doesn't show whether the original business facts were correct. Inspect the data source, policy context, and review history for that question.
The package identifies its proof provider
Each package carries its verification references. The integrity envelope identifies the proof provider and source commitments used to check the export.
Integrity proof for each record
Choose the proof provider for your environment
Keep verification in Azure with the default Azure SQL Database Ledger option. Need a public reference? Choose Solana when your environment is created.
Private verification in Azure
Store each session’s fingerprint in an append-only Azure SQL Database Ledger table. Verification checks the ledger against separately protected database digests to detect changes.
Your auditor gets read-only verification access, separate from the access that records evidence, and checks each fingerprint in Azure. Nothing is published to a public network.
Public verification with Solana
Publish a fingerprint for a group of records to Solana. Anyone with the reference can inspect the public transaction.
VeriProof sends fingerprints only. Decision content, personal data, and protected health information stay in your deployment; verification uses the public Solana network.
One verification option per environment
The proof provider is fixed after the environment is created. Choosing the other provider requires a new environment with its own proof history. Private Enterprise runs entirely in your own Azure subscription, integrity ledger included.
Azure SQL Database Ledger: check the row and protected digests
Azure SQL Database Ledger stores record fingerprints in an append-only table. Verification checks the recorded row and uses separately protected database digests to assess the ledger.
Verification uses separate access from evidence recording, and the proof and its verification stay within Azure. Azure SQL Database Ledger is the default integrity option in the managed service. Private Enterprise, coming soon to Azure Marketplace, will run entirely in your own Azure subscription, completely separate from veriproof.app, and this ledger runs there with it.
Solana environments: check the exact public transaction
Solana records a batch commitment in a public transaction. VeriProof sends fingerprints rather than decision content to this network, and no personal or patient data is ever published to it.
The verifier checks the recorded transaction, its memo, and the root linked to the session's inclusion proof. An explorer can show the transaction, but cannot verify the exported files or package signature.
Public proof references remain on the network when off-chain content is deleted. Include that distinction in your retention and data-handling review.
Recover interrupted proof submissions
Provider outages can delay recording a fingerprint. VeriProof uses retry and reconciliation processes to recover eligible incomplete work.
Retry
Temporary submission failures follow the configured retry path. Operators monitor attempts and failures that need intervention.
Reconcile
Reconciliation finds eligible sessions without proof references and queues recovery work.
Confirm
The recorded status distinguishes pending proof from completed verification. Reviewers can see which checks still need to finish.
Test recovery with the provider and load you plan to use. The relevant measures are completion time, backlog growth, and whether interrupted work is recovered.
The evidence pack makes its scope inspectable
A package contains selected session records, a manifest, a redaction report, and an integrity envelope. Additional review material depends on the selected records and export options.
The signature protects the package inventory. The redaction report explains how the export differs from the available source data.
Verify the export independently
Give reviewers a check they can run independently. The Verify CLI checks the exported files, signature, and proof reference without calling a VeriProof API.
The result shows whether the evidence passed verification, changed, or could not be checked.
What reviewers can establish
What was included
The signed inventory lists the exported files. A redaction report explains changes made for the export.
Whether it matches
Verification checks the files against the signed inventory and source proof. A mismatch or incomplete check is reported in the result.
What the decision means
Integrity is one part of the review. Your reviewers assess the original facts and decide whether the business decision was appropriate.
Technical questions
Azure SQL Database Ledger is the default and keeps verification within Azure. Choose Solana when your reviewers need a public proof reference.
Yes. Reviewers can check an evidence pack independently, without a VeriProof account.
The check reports that verification could not finish. Restore provider access and run it again; a connection failure is distinct from changed content.
No. It checks the integrity of the supplied evidence. Review the original facts and the decision against your assessment criteria.
Use a representative workload with your chosen provider. Measure submission and confirmation times, backlog, retries, and recovery rather than relying on a universal throughput figure.
Examine the proof path for your deployment
Download the sample evidence pack and run the checks yourself, or bring the questions your reviewers need answered and we will walk through it with you.