When should we run a security contest, relative to mainnet launch?
Start once your code is complete and before you go to mainnet. That window is what our programs are built for. Whichever one you run, leave a buffer between the end of the work and your launch date.
Code complete, before mainnet
The work belongs in the window between code complete and launch. Before that, researchers compete on code that is still moving, and findings land on functions that are about to be rewritten. After launch, every issue found is an issue found against live funds.
Leave a buffer before the launch date
A contest that ends the week you ship leaves nowhere to put the result. What follows a contest is a Mitigation Review: fixes are written, then reviewed by the researchers who found the issues. That sequence needs room in the calendar.
The buffer is the part teams underestimate. Plan for the fixes and their review, not only for the contest window.
What runs in the meantime
The Bridge is built for exactly this window, and it is a sequence rather than a single event: a full-stack security review, an AutoGuard round where AI agents and static analyzers compete first, the guard contest itself, a Mitigation Review, and finally a pre-launch bug bounty running in parallel with formal verification.
Scoping that sequence against your launch date is the conversation to have early. Book a call and we will map it to your timeline.
Scope it with us.
Book a live walkthrough of the platform. We will answer anything your team needs before getting to work.