1. Find one event and read its existing code rule
30 minPick a hackathon with a developer tooling or security track and check whether existing code is allowed.
Pick where you want to go. Every route starts with a move you can make within the hour.
Pick a hackathon with a developer tooling or security track and check whether existing code is allowed.
For example, invariant tests generated from written invariants, or a new chain in the deployment plan.
Post in the event chat that you will scan any public repo and send back a plain-words summary.
Before you submit: I can run open source checks on your public repo and send back each finding in one plain sentence, plus what the tools cannot check. It takes ten minutes and it is not an audit. Reply with your repo link.
Record a two minute demo and state clearly which parts were built at the event.
Leave an email and we nudge you at 24 and 72 hours with your next move. Optional.
Or to keep this voyage on your profile.
A hackathon cockpit that plans your scope, tracks bounties, and drafts a judge-ready submission.
A project-in-a-box: contracts, site, docs and impact metrics shaped for grant applications.
An AI agent that watches your own launch and warns you of misconfigurations before you ship.