1. Open the Regatta Board and shortlist two events
25 minGo to /hackathons and filter for consumer, trading or the chain you deployed on. Read each event's rule on existing code; many require you to disclose prior work and only judge new progress.
Pick where you want to go. Every route starts with a move you can make within the hour.
Go to /hackathons and filter for consumer, trading or the chain you deployed on. Read each event's rule on existing code; many require you to disclose prior work and only judge new progress.
Choose something visible: a group leaderboard of cancelled trades, or a mobile prompt. That is your disclosed new progress.
Show three losing trades, the brake firing, the question, and the journal entry landing onchain. End on the weekly report.
A trader on the team makes the story credible to judges.
Building a tilt brake for onchain trading this hackathon, base already works and I am adding group leaderboards as the new part. Want to be the trader on the team and help with the demo? About 4 hours total.
State what existed before the event and what you built during it, in the first paragraph.
Hi organizers, I am entering with Cooling Off, which existed before the event. I plan to disclose prior work and build one new feature during the event. Does that fit your rule on existing code?
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.
Prove your trading discipline, not your profits: stops honored, sizing kept, tilt avoided.
Your perp bot follows your rules, and every rule you kept becomes a public, provable track record.