The case
Apple Inc. v. Samsung Electronics Co., 888 F. Supp. 2d 976 (N.D. Cal. 2012) was a patent infringement action in which Apple moved for sanctions based on Samsung's failure to preserve relevant evidence. After the duty to preserve attached, Samsung continued operating automatic email deletion routines without implementing adequate litigation holds for employees likely to possess responsive communications. The sanctions motion placed Samsung's organizational response to the hold obligation under scrutiny, not the conduct of any individual custodian.
What the court held
Judge Lucy Koh imposed an adverse-inference instruction, finding that Samsung's failure to suspend routine deletion policies after the preservation duty attached was sanctionable under the federal common law spoliation framework then in effect. The ruling made clear that systemic institutional failure could generate liability without proof that any individual deliberately destroyed evidence. The 2015 amendment to FRCP 37(e) subsequently raised the bar: courts now require a finding that the party acted with "intent to deprive" before imposing an adverse inference, a threshold the pre-amendment negligence standard Judge Koh applied in 2012 did not require.
Where blockchain anchoring fits
The Apple-Samsung sanctions motion illustrates a preservation failure that exists upstream of any individual's choices. Documents weren't deleted because someone decided to delete them. They were deleted because institutional systems kept running on schedule after they should have stopped. The company's own infrastructure became the mechanism of loss.
A blockchain anchor operates entirely outside those institutional systems. Anchoring a SHA-256 hash to Polygon and Bitcoin creates a record on public, immutable ledgers that no internal deletion routine can reach. A system can remove the underlying file. It cannot alter a transaction already confirmed on two independent chains. The record of the file's existence, and its exact content at the time of anchoring, persists regardless of what any company-side system does next.
What an anchor proves is bounded and specific. It proves that a file producing that exact hash existed at the moment of anchoring. Content integrity too: any modification produces a completely different hash. What it doesn't prove is that the original file still exists, or that its contents are factually accurate. Those are distinct questions, and a blockchain timestamp doesn't resolve either of them.
This distinction matters for sanctions analysis. If files were anchored before the deletion routine ran, the hashes on-chain establish that those files existed at a specific point in time with specific content. The files are still gone. But the anchors document the prior existence and the exact state of the content, which is relevant to evaluating prejudice under FRCP 37(e)(1). A party seeking curative measures can point to the on-chain record to establish the scope of what was lost. A party defending against sanctions can demonstrate that the content existed and was preserved in hash form before the deletion occurred.
Verification doesn't require cooperation from the party whose systems are under examination. The public endpoint at https://proofledger.io/api/v1/verify?hash=<sha256> returns proof status, chain transaction IDs, and explorer URLs without authentication. For entirely offline verification, the verify-proof Python package performs the same check against on-chain data without contacting any ProofLedger servers. In a case where one party's infrastructure is itself under scrutiny, the ability to verify through a process that neither party controls is directly relevant to reliability under FRE 901(b)(9).
The dual-chain structure adds corroboration. Polygon provides near-instant finality. Bitcoin's daily batch anchoring uses merkle proofs that let any verifier confirm a specific hash's inclusion in a Bitcoin transaction. Two independent chains, neither controlled by the anchoring party, corroborating the same timestamp: that is the kind of process reliability FRE 901(b)(9) addresses.
The takeaway for practitioners
Apple v. Samsung established that courts will examine institutional preservation processes, not just individual conduct, when assessing sanctions for ESI loss. Under FRCP 37(e)(1), courts retain authority to impose curative measures proportionate to prejudice even where intent to deprive can't be shown. An anchor doesn't replace a litigation hold or restore a deleted document. What it creates is an independent, verifiable record of prior existence on a public chain that institutional processes cannot retroactively alter. For admissibility, FRE 901(b)(9) covers authentication of evidence from a process or system that generates an accurate result. Where self-authentication without live testimony is available, FRE 902(13) permits written certification of machine-generated records.
References
- Apple Inc. v. Samsung Electronics Co., 888 F. Supp. 2d 976 (N.D. Cal. 2012)
- FRCP 37(e) (2015 amendment): ESI preservation, curative measures, and adverse-inference standard
- FRE 901(b)(9): Authentication of evidence from a process or system producing an accurate result
- FRE 902(13): Self-authentication of machine-generated records via written certification
Top comments (0)