ClaimAnchor™ · Evidence Provenance Infrastructure for Insurance
An insurer can no longer claim they never received the file.
Bitcoin-anchored at transmission. Verifiable by anyone. Alterable by no one.
What anchoring proves
A Bitcoin anchor might prove that a particular fingerprint existed no later than a certain time. It does not, by itself, prove authorship, accuracy, lawful possession, contractual assent, or the truth of the underlying document.
The Problem
Claims systems were built to manage documents — not verify them. Existing platforms can prove where a document is stored. They cannot independently prove when it entered the process, whether it changed after submission, or whether the record in a dispute is identical to the original.
Fraud analytics tell you whether something looks suspicious. ClaimAnchor tells you what was submitted and when. These are different problems. Only one has an independent infrastructure answer.
Five years ago, altering a document required expertise. Today, PDFs can be rewritten, invoices generated, photos modified. Insurers can no longer rely on visual inspection alone.
A single claim dispute runs $10,000–$30,000 in defense costs. Carrier audits take days of reconstruction. SIU investigations require metadata forensics. The evidence gap is an operational cost center.
Why Now
Guidewire
January 2026
"Called for insurers to invest in ‘provenance-protected workflows’ and ‘real-time verification tools’ — describing the need to verify where digital content came from, whether it’s been altered, and how confident insurers can be in its authenticity."
Verisk
March 2026
"98% of insurers say AI editing fuels fraud. 45% anticipate stricter proof-of-loss requirements within 3–5 years. Only 43% feel very confident detecting document authenticity at scale."
NAIC
Ongoing
"Blockchain records are permanent, cannot be deleted, provide a reliable audit trail, and may reduce fraud risk. Lists claims management and fraud prevention as identified use cases."
Guidewire described a requirement. Verisk quantified the gap.
ClaimAnchor is the product that closes it.
Why Existing Systems Aren't Enough
Existing systems timestamp into databases they control. Those timestamps can be challenged because they belong to an interested party. ClaimAnchor's timestamp is Bitcoin — a public record owned by no one.
| Capability | Claims System | Doc Management | Fraud Analytics | ClaimAnchor™ |
|---|---|---|---|---|
| Store documents | ||||
| Track workflow | ||||
| Detect suspicious submissions | ||||
| Independent provenance | ||||
| Third-party verifiable (no login) | ||||
| Immutable evidence record | ||||
| Neutral-party timestamp |
ClaimAnchor does not replace any of these systems. It installs underneath them as the independent evidence layer none of them provide.
How It Works
Zero workflow change for producers. The Certificate is the only new artifact.
At the moment a claim document leaves your agency or MGA — via email, portal, or API — it passes through the ClaimAnchor endpoint. Your submission workflow continues unchanged.
ClaimAnchor generates a SHA-256 cryptographic fingerprint of the document, captures a pre-transmission timestamp, and commits the proof to Bitcoin via OP_RETURN. The full payload is stored on Arweave.
A ClaimAnchor Certificate is returned instantly — containing the Bitcoin transaction ID, block height timestamp, Arweave content hash, and document fingerprint. Attach it to the claim file or archive it. Your choice.
Anyone — a carrier, a regulator, a court, an SIU investigator — can verify the certificate by entering the Bitcoin TX ID in any public block explorer. No login. No account. No trusted party required. The record is permanent.
Scope
Clarity on scope before you evaluate.
Determine whether a document is truthful
Prove a specific document existed in a specific form at a specific time
Detect fraud automatically
Preserve independently verifiable evidence for fraud review
Replace claims management systems
Add independent provenance beneath them — zero workflow change
Replace SIU investigations
Reduce uncertainty about document history before investigations begin
Require trusting ICPO X
Anchor to Bitcoin — a public record no single party controls
Who It Serves
Portfolio-level oversight across hundreds of producers. One carrier audit requiring submission reconstruction costs more than a year of ClaimAnchor. Compliance teams have budget authority. The pain is acute.
Gap insurance, medical stop-loss, excess & surplus. Litigation exposure from document authenticity disputes is structural. ClaimAnchor is a control cost, not a product cost.
Network-wide standardization. One platform adoption means provenance controls across thousands of producers — and a documented capability for carrier and regulatory conversations.
One avoided claim dispute covers years of ClaimAnchor. Protects your license, your carrier relationships, and your name — before a dispute starts, not after.
Dispute reconstruction that currently takes weeks of metadata forensics takes 60 seconds. The original submission record exists before the investigation opens.
Gap, stop-loss, supplemental — any line where EOB authenticity, submission timing, or document version is a contested fact in a claim dispute.
Pricing
Every tier includes Bitcoin anchoring, Arweave permanence, and independently verifiable certificates. One avoided dispute covers years of ClaimAnchor.
Agency
Independent producers. Zero workflow change.
One avoided dispute recovers 3+ years.
MGA
Up to 200 producers. Compliance-grade controls.
Less than one carrier audit response.
MGA Enterprise
500+ producers. Carrier-presentable controls.
Documented control for carrier & regulatory conversations.
Enterprise / Carrier
Unlimited records · carrier integrations · white labeling · custom retention · BAA available
Contact for Enterprise Pricing →The Pilot
At the end of the pilot you have a working implementation, 200 independently verifiable claim records, and documented proof of what your agency submitted and when — before a carrier, regulator, or court ever asks.
Pilot investment credited 100% toward first-year subscription at conversion.