HackProof

PROVE YOU
SHIPPED IT.

Submit your hackathon project with a public proof certificate: evidence stored on Walrus, manifest hash anchored on Sui, and verification read through Tatum Sui RPC.

Create HackProof Verify a submission

HackProof by Vouch

Creates a public certificate with Walrus evidence, Sui proof metadata, and Tatum-powered verification checks for judges.

Project nameShort descriptionGitHub repo URLLive demo URLDemo video URLSui package/object/transactionX/LinkedIn post URLHackathonProject description

Drag evidence files here

Screenshots, READMEs, PDFs, text files, images, or demo proof. Max 5 files, 5MB each.

Choose files

GitHub sign-in required

Judges see the GitHub identity anchored in the proof manifest.

HOW IT WORKS

Hash your evidence

Every file is SHA-256 hashed in the browser before upload. The hash is what gets anchored, not just a link.

Timestamp locked on Sui

Your Sui wallet signs the transaction. The resulting object has an immutable blockchain timestamp — the deadline check is on-chain, not in a spreadsheet.

Evidence stored on Walrus

Files go to Walrus decentralised storage. The blob ID and SHA-256 hash are anchored together. No one can swap the file after submission.

Anyone can verify

Judges paste the object ID into /verify and see all checks run live — hash match, timestamp, GitHub identity. No trust in the organiser required.

For organisers

JUDGE WITH CONFIDENCE.

Ask builders to submit a Vouch proof instead of (or alongside) the usual form submission. You get a permanent, independently verifiable record of what was built, when, by whom. No back-and-forth over deadlines.

Paste any proof URL into /verify — 8 checks run in seconds

GitHub identity anchored at submission time — no impersonation

Evidence files re-hashed live from Walrus — no swapped files

Sui object timestamp is immutable — no deadline disputes

Verification checklist

Sui proof object exists

Proof timestamp found

Walrus manifest blob found

Manifest hash matches on-chain record

Evidence file SHA-256 verified

GitHub account linked to proof

Wallet owner matches proof creator

Verification performed through Tatum RPC

Open verifier

RECENT SUBMISSIONS

Browse all

All proofs on Vouch — each one is a tamper-proof build submission.

WHY IT MATTERS

The problem

Hackathon submissions are not tamper-proof

✕ Git history can be rewritten after the deadline
✕ Demo links can be redirected to updated code
✕ Screenshots can be staged at any time
✕ Google Docs show last-edited date, not created date
✕ Organisers take timestamps on trust

The fix

HackProof anchors everything before the deadline

✓ SHA-256 hash of every file computed in the browser
✓ Evidence uploaded to Walrus decentralised storage
✓ Manifest hash anchored on Sui in a signed transaction
✓ Blockchain timestamp is immutable and publicly verifiable
✓ GitHub identity linked at submission time via OAuth

The problem — without HackProof	The fix — with HackProof
✕Git history can be rewritten after the deadline	✓SHA-256 hash of every file computed in the browser
✕Demo links can be redirected to updated code	✓Evidence uploaded to Walrus decentralised storage
✕Screenshots can be staged at any time	✓Manifest hash anchored on Sui in a signed transaction
✕Google Docs show last-edited date, not created date	✓Blockchain timestamp is immutable and publicly verifiable
✕Organisers take timestamps on trust	✓GitHub identity linked at submission time via OAuth