1. Pick your next two events
30 minOpen the Regatta Board at /hackathons and choose two. Paste each rule page into the cockpit and check each event's rule on existing code.
Pick where you want to go. Every route starts with a move you can make within the hour.
Open the Regatta Board at /hackathons and choose two. Paste each rule page into the cockpit and check each event's rule on existing code.
Post in the event's team finding channel with what you already bring (Hack Week Pilot, live) and the one skill you are missing. Be specific so the right person self selects.
Forming a team for [track]. I run a cockpit that plans scope and flags rule traps. Need [skill]. DM me.
Scope one feature for a sponsor track: use the timeline. cut until it fits. Write the 90 second demo script first, then cut the feature until that demo is possible in the time you have.
Generate README and demo script, then edit every line.
Draft README and demo script are in. Everyone edit your section by 10am, we record at 11.
Record a short demo that shows a real flow end to end, write a README that separates what existed before from what you built at the event, and submit hours before the deadline. Submit well before deadline.
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.
Post a small local job with USDC held in escrow, released when the neighbourhood confirms it is done.
Every commit, deploy, and demo you ship becomes a signed, timestamped builder diary.
A project-in-a-box: contracts, site, docs and impact metrics shaped for grant applications.