> Hypothetical scenario — illustrative only. Not based on a specific customer engagement.
The scenario
A homeowner files a claim after a major hurricane, providing inspection photos they describe as pre-storm documentation of the roof and exterior. The carrier questions the timing. File metadata shows timestamps, but EXIF data is mutable on any device, and notarizing a later statement that the photos were taken pre-storm proves attestation, not timing.
How ProofLedger applies
Before storm season, the property owner anchors SHA-256 hashes of their inspection photos to both Polygon and Bitcoin via ProofLedger. The files stay on their own device; only the hash goes on-chain. Polygon provides an immediate timestamp record; Bitcoin's daily batch anchor adds a second independent chain via merkle proof. If a dispute arises later, any party, including opposing counsel or an independent examiner, can verify the timestamp using the public verify URL or the verify-proof package, without contacting ProofLedger.
Expected outcome
The dual-chain timestamp would establish that those specific file hashes existed on-chain before the storm's recorded landfall date, creating a foundation for authentication under FRE 901(b)(9) as output from a process that produces an accurate result. This could support the policyholder's position in a coverage dispute and would give counsel a chain-of-custody record mathematically tied to the original files. Independent verifiability across two public chains is what distinguishes this from mutable file metadata or a notarized statement about when photos were taken.
Takeaway
When the question is timing, the answer needs to come from a record that can't be edited after the question is raised.