1. Open the Regatta Board and pick one event
30 minGo to /hackathons and filter for identity, dev tooling or public goods tracks. Read each event's rule on existing code; many require only new work during the event, and some have continuity tracks.
Pick where you want to go. Every route starts with a move you can make within the hour.
Go to /hackathons and filter for identity, dev tooling or public goods tracks. Read each event's rule on existing code; many require only new work during the event, and some have continuity tracks.
Good picks: a Figma connector, a team directory, or a recruiter shortlist export. Write what is new versus what existed before so judges see the line clearly.
Find a designer or frontend builder in the event Discord. A design teammate is ideal because design proofs are your differentiator.
Looking for a designer for Craft Graph: verified contribution maps for builders. This weekend we're adding design proofs so Figma work counts next to code. Your work would literally be the demo. Interested?
Show a real profile before and after the new feature. State the problem in one sentence, show it working, end with the contract address.
Submit before the deadline, then message the relevant sponsor team with your link. Prizes are never guaranteed; the contact often matters more.
Hi Sade, we built a design proof connector for Craft Graph at the hackathon on your chain. Demo (link). Would love two minutes of feedback on whether it fits your builder program.
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.
Timestamp your original prompts and creative process so you can prove the idea was yours first.
Every commit, deploy, and demo you ship becomes a signed, timestamped builder diary.