Hackathon demo · 3 minutes
The demo script that wins rooms
Scenario: a developer proves version 1.0 existed on September 5, 2026 — then proves tampering is detectable.
Demo data Sample records below are demo data, not blockchain transactions, until you anchor them yourself.
- 1Open ProofFlow and connect a testnet wallet (MetaMask → Sepolia).
- 2Click Create Proof and upload the sample release document below.
- 3Watch SHA-256 generate locally. Point out: the document itself never goes on-chain.
- 4Submit the hash. Narrate the modal honestly: wallet confirmation → broadcast → on-chain confirmation.
- 5Open the generated verification page (/verify/[proofId]) and share the link.
- 6Upload the same document → HASH MATCH ✓ → VERIFIED ✓.
- 7Modify one character in the document, upload again → HASH MISMATCH ✕ → NOT VERIFIED. That's the wow moment.
Sample release document
Save this as release-v1.txt, anchor it, then modify one character to trigger the mismatch.
ProofFlow Demo — Release v1.0 Project: ProofFlow Version: 1.0.0 Date: 2026-09-05 Approved by: Demo Maintainer Checksum-scope: entire file bytes Note: hash this exact file to reproduce the demo.Download release-v1.txt
Demo honesty rules
- Never present the local/demo path as an on-chain transaction — the UI labels it automatically.
- Say “transaction confirmed” only after the modal reaches on-chain confirmation.
- Say “verified” only after the hashes visibly match.