HN Showcase
Back to browse
GitHub Repository

Reproducible SHA-256 integrity receipts for official public-source byte identity.

2 starsJavaScript

EV424 – Evidence Definition (Don't Trust, Verify)

by lws9262·Feb 21, 2026·2 points·1 comment
Visit ProjectView on HN

AI Analysis

●●SolidBig BrainNiche Gem

SHA-256 receipts prove docs unchanged over time, but spec-only with no working implementation.

Strengths
  • •Genuinely clever non-custodial model avoids hosting liability while enabling verification
  • •Reproducible receipt design (exit code + hash + normalized JSON) is cryptographically sound
  • •Transparent about limitations—doesn't judge truth, safety, or legality
Weaknesses
  • •Contract spec only; implementation roadmap missing and unclear when tools ship
  • •Niche use case; requires users understand reproducible verification workflows
Category
Security
Target Audience

Legal/compliance teams, document auditors, archivists needing tamper-proof verification

Similar To

Proof of Existence · OpenTimestamps

Post Description

EV424 Evidence Definition

• Don’t Trust, Verify • Not a single byte changes. • If it cannot be reproduced, it is not evidence.

I’m publishing a contract-only spec for a non-custodial integrity receipt workflow (exit code + SHA-256 + normalized JSON). Feedback I want: is the NOT_COVERED fence strict enough to prevent over-claims?

https://github.com/ev424verify/ev424-hub

Similar Projects