HN Showcase
Back to browse
Tamper-proof work verification with Ed25519 and RFC 3161 TSA

Tamper-proof work verification with Ed25519 and RFC 3161 TSA

by sudeshss·Feb 20, 2026·4 points·1 comment
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainBold Bet

Clever crypto stack (Ed25519 + RFC 3161 TSA + GPS) but solves a niche dispute problem solo can't fix.

Strengths
  • •Genuine cryptographic rigor: Ed25519 signatures, SHA-256 hashing, external RFC 3161 timestamp authority create true tamper-evidence
  • •Client-side verification eliminates backend trust requirement; any photo/GPS/metadata edit invalidates signature immediately
  • •Clear use case (gig economy disputes) with real pain point
Weaknesses
  • •Fundamentally limited: signature proof only works if *both* worker and client agree to verify; won't prevent bad-faith denial of service
  • •No marketplace integration, no dispute resolution mechanism, no recovery for worker if client disputes despite valid signature — it's a witnessing tool, not a binding contract
Category
Other
Target Audience

Gig workers (cleaners, contractors, delivery); clients needing tamper-proof work proof

Similar To

OpenTimestamps · Notarization services · Docusign timestamp features

Post Description

Built a mobile app that generates cryptographically verifiable proof of completed service work. Before/after photos hashed with SHA-256, signed with Ed25519, timestamp anchored via freetsa (RFC 3161 compliant), GPS coordinates embedded. Client side verification only. No backend trust required. Signatures verified locally in an ephemeral memory sandbox. Any tampering in photos, timestamps, GPS or metadata immediately invalidates the signature. Stack: React Native, Golang, Ed25519, SHA-256, RFC 3161 TSA, AI work narratives via Groq. Built for the gig economy trust problem. Target markets: contractors, cleaners, delivery, property management. Looking to sell full IP and source code. [email protected]

Similar Projects