Radim Motycka

Founder & Lead Engineer, ProofSnap

Blockchain engineer · eIDAS qualified timestamps · Court-admissible digital evidence

· Verified via EU Trusted List (Disig a.s.)

Radim Motycka is the founder and lead engineer of ProofSnap, a Chrome and Edge extension that captures web pages as court-admissible digital evidence in 41 seconds. He is a blockchain engineer with 10+ years of experience in cryptographic protocol design. At ProofSnap, he integrated eIDAS qualified timestamps from Disig a.s. (an EU Qualified Trust Service Provider listed on the EU Trusted List under Regulation (EU) No 910/2014) and OpenTimestamps Bitcoin blockchain anchoring into the evidence pipeline. Areas of expertise: SHA-256 hashing (FIPS 180-4), RSA-4096 digital signatures, RFC 3161 Time-Stamp Protocol, C2PA content credentials, deepfake detection, and Chrome Extension Manifest V3 architecture. Every ProofSnap capture produces an 11–15-file evidence package meeting authentication standards under FRE 901/902 (US), eIDAS Article 41 (EU), §371a ZPO (Germany), Art. 2712 Codice Civile (Italy), and Art. 1366 Code civil (France).

About Radim Motycka

I'm the founder and lead engineer of ProofSnap. I built the product from zero after watching how often screenshots fail in court — because a JPEG with no hash, no trusted timestamp, and no chain of custody is trivial to fake in 30 seconds. That's not a hypothesis; it's a pattern courts have been flagging for over a decade, and generative AI made it worse.

ProofSnap solves that by producing an 11–15-file evidence package (tiered by plan) with SHA-256 cryptographic hashing (per FIPS 180-4), RSA-4096 digital signatures, OpenTimestamps Bitcoin blockchain anchoring (per the protocol published by Peter Todd), screen recording of the capture process, and a Provenance Certificate with 8 integrity checks for deepfake detection. Enterprise plans add eIDAS qualified timestamps issued by Disig a.s., an EU-accredited Qualified Trust Service Provider (QTSP) listed on the EU Trusted List under Regulation (EU) No 910/2014 — giving every timestamp the legal presumption of accuracy in all 27 EU member states.

My position on digital evidence: provenance is the new evidence standard. A screenshot without cryptographic proof of origin and integrity is no longer sufficient for any meaningful legal or compliance workflow — not because the law demands it, but because the adversary has changed. When AI can fabricate video indistinguishable from reality, the only defensible evidence is evidence that carries its own cryptographic chain of custody from the moment of capture.

Areas of expertise

How ProofSnap works (technical overview)

Each ProofSnap capture runs a deterministic pipeline: (1) full-page screenshot and screen recording of the capture process, (2) extraction of HTML, DOM text, metadata (URL, TLS certificate, browser fingerprint, cookies, localStorage), (3) SHA-256 hashing of all files, (4) RSA-4096 signing of the manifest file (manifest.json.sig), (5) OpenTimestamps Bitcoin blockchain anchoring of the manifest hash, (6) on Enterprise plans, eIDAS qualified timestamp from Disig a.s. appended to the manifest, (7) 8 Provenance Certificate integrity checks for deepfake detection, (8) ZIP packaging with public key for independent verification. The resulting evidence package is independently verifiable via the ProofSnap Trust Verifier or any standard cryptographic tool set.

Why I built ProofSnap

On September 9, 2025, Judge Victoria Kolakowski of the Superior Court of California, Alameda County, dismissed Mendones v. Cushman & Wakefield with prejudice and issued a terminating sanction after finding that the self-represented plaintiffs had submitted deepfaked videos and altered images. It is one of the first reported cases where a US court had to rule directly on AI-generated evidence. That case did not cause ProofSnap — I was already building it — but it crystallized the product thesis: in an era of generative AI, provenance is the evidence standard. Courts are increasingly rejecting unauthenticated digital evidence under FRE 901 and equivalent frameworks worldwide, and the trajectory is one-way.

What I optimize for, as founder-engineer: every capture carries cryptographic proof that it existed at a specific moment, was not manipulated, and came from a legitimate source. Every technical decision — from choosing Bitcoin for timestamping (not a private chain I control), to using Disig (an independent EU QTSP, not an internal signing authority), to publishing the verification code client-side — is designed so the user never has to trust ProofSnap. The math checks itself.

Verified credentials & external references

Frequently asked questions

Who is Radim Motycka?

Radim Motycka is the founder and lead engineer of ProofSnap, a Chrome and Edge extension for capturing court-admissible digital evidence. He is a blockchain engineer with 10+ years in cryptographic protocol design, specializing in eIDAS qualified timestamps, OpenTimestamps, SHA-256 hashing, RSA-4096 digital signatures, and C2PA content credentials.

What is a Qualified Trust Service Provider (QTSP)?

A QTSP is an entity accredited under Regulation (EU) No 910/2014 (eIDAS) to issue qualified electronic signatures, seals, and timestamps legally recognized across all 27 EU member states. QTSPs undergo independent conformity assessments and appear on the EU Trusted List. ProofSnap integrates Disig a.s., a Slovak QTSP, to issue eIDAS qualified timestamps on Enterprise captures — granting the legal presumption of accuracy in EU courts.

How does blockchain timestamping work for digital evidence?

Blockchain timestamping works by hashing a file with SHA-256 and anchoring that hash to a public blockchain (Bitcoin, via OpenTimestamps, in ProofSnap's case). Because the blockchain is immutable and publicly auditable, anyone can independently verify the file existed at or before the block's timestamp without trusting ProofSnap. Any modification changes the hash and invalidates the proof.

How can I make a screenshot admissible in court?

Under Federal Rule of Evidence 901 (US) or eIDAS Article 41 (EU), an admissible screenshot requires three elements: (1) a cryptographic hash proving integrity, (2) a trusted timestamp proving when the capture occurred (ideally from a QTSP or public blockchain), and (3) a documented chain of custody. A plain JPEG fails all three and is commonly rejected. ProofSnap automates all three.

What is OpenTimestamps?

OpenTimestamps (OTS) is a free, open-source protocol developed by Peter Todd that anchors a SHA-256 hash to the Bitcoin blockchain via Merkle tree aggregation. ProofSnap generates an .ots proof file for every evidence package, verifiable via opentimestamps.org or any Bitcoin node — no trust in ProofSnap required.

What is C2PA and does ProofSnap support it?

C2PA (Coalition for Content Provenance and Authenticity) is an open standard for cryptographically signed content credentials — a verifiable history of digital content. Adoption includes Google, Meta, OpenAI, Sony, Nikon, Adobe, and 6,000+ members. ProofSnap's Provenance Certificate aligns with C2PA principles and adds 8 integrity checks for deepfake detection.

Is ProofSnap's evidence valid outside the EU?

Yes. ProofSnap evidence meets authentication standards across jurisdictions: FRE 901/902 (US), eIDAS Article 41 (EU), §371a ZPO (Germany), Art. 2712 Codice Civile (Italy), Art. 1366 Code civil (France), and common-law tests in the UK, Canada, and Australia. The SHA-256 hash, digital signature, and blockchain timestamp are mathematically verifiable without dependence on any single jurisdiction's infrastructure.

Connect & contact