Cryptographic field photo proof (Ed25519, RFC 3161)

Name: Cryptographic field photo proof (Ed25519, RFC 3161)
Availability: InStock
Author: sudeshss

by sudeshss·Mar 8, 2026·1 point·1 comment

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemNiche GemBig Brain

Crypto-signed field photos with zero backend trust, but disputes aren't new—and adoption requires both sides.

Strengths

•Ed25519 + RFC 3161 TSA stack genuinely removes app trust; verification runs entirely client-side without backend.
•GPS + timestamp anchor makes falsification technically expensive, not just cryptographically impossible.
•Clear UX for a complex domain—10-digit codes, QR scanning, and AI narrative summaries make proof accessible to non-technical workers.

Weaknesses

•Crowded category: Snappr, Handiwork, and traditional photo-timestamping services already address service proof; crypto doesn't solve adoption friction.
•Two-sided adoption problem—worker sends proof, but client must trust the app/process anyway; cryptography doesn't overcome skepticism.

Post Description

Mobile app that cryptographically signs before/after field photos. Ed25519, SHA-256, RFC 3161 timestamped, GPS stamped. Any alteration breaks proof instantly. Zero backend trust required.

For sale. Overview: https://yourbeforeafterwork.netlify.app