01

Blockchains record
what reaches the chain.
Security decisions made before
signing or submission
leave no on-chain trace.

Pre-signing threat detection · selective disclosure · verifiable off-chain decisions · autonomous exploit proof. TRUST404 is a Web3 security hackathon for building and validating security before execution.

Apply now -> Tracks ->

Trust off the chain

A transaction on-chain gets four properties for free.
A decision that stopped before execution gets none of them.

What a record needs A transaction on the chain A decision made before it
Immutability Replicated by consensus; nobody can rewrite it An institution can revise it afterwards
Completeness Blocks chain together, so a gap is visible Delete a row and nothing outside notices
Independent verification Anyone can check it against their own node You have to take the operator's database on trust
Non-repudiation A signature remains, so it cannot be denied No signature, so it can be

Three moments the chain never sees

  1. A contract is judged malicious and the signature is blocked. Because the user never signed, neither the verdict nor its reasoning exists on-chain.
  2. Eligibility is proven while date of birth, student ID and address stay behind. A third party needs some way to confirm that they really were withheld.
  3. A sanctions screen rejects a transfer. No transaction was ever built, so one row in an internal database is the only evidence there is.

TRUST404 asks how the immutability, completeness, independent verifiability and non-repudiation of an on-chain record can be extended to the security decisions made off it.

02

Who this is for

  • Web3 developers and smart contract engineers
  • Security researchers
  • Frontend, infrastructure and DevOps engineers
  • AI and ML engineers
  • Students in a related field

What the application asks for

  • A GitHub or portfolio link
  • The tracks you are interested in — pick as many as apply
  • Your Discord handle — technical guidance and every announcement go out on Discord
  • What you plan to build — it does not have to be settled. Two to five sentences on the problem and how you would approach it is enough
  • For a team application, every member's name, email and role

Team building

Teams are 1–5 people and solo entries are welcome. If you apply alone and mark that you would like a team, we help match you through Discord.

03

What you get

  • Per-track mentoring and technical Q&A on Discord
  • Public sample sets and participant material for each track
  • Food and drink at Demo Day

Per-track mentoring is run by the ANAM145 engineers who set that track's evaluation criteria. Judges and mentors

Apply now -> FAQ -> Back to overview