The Bridge
Every stage we run, in order, connecting the end of development to mainnet. A full-stack review, the AutoGuard and Guard contests, a mitigation review, then formal verification with a pre-launch bug bounty live alongside it. Five stages, one engagement.
Why the stages are sequential
Each review method is good at something the others are not, and each one works better on a surface the previous stage has already cleaned. Tools find the obvious before humans spend time on it. Humans find what tools cannot. Fixes get reviewed rather than trusted. Proofs cover what review cannot guarantee. A bounty catches what everything before it missed.
Run out of order, each stage does less work than it could.
Stage 1: Full-stack security review
Valkyri Security review the agreed scope across infrastructure, web2 and web3 components. This establishes the first structured pass over the whole product surface, not just the contracts.
Stage 2: AutoGuard contest
Guards using AI agents and static analysers review the frozen scope, competing for 10% of the prize pool. This surfaces the straightforward and semi-obvious issues before the human contest, so researchers are not paid to rediscover them.
Stage 3: Guard contest
Researchers review the scope with their own methods and attack paths, competing for the remaining 90%. Two Lead Guards anchor coverage; two Lead Judges assess the submissions.
Stage 4: Mitigation review
Lead Guards who finish in the top-10 join the review, along with any guards who outrank them and finish inside the top-10. The full-stack partner returns to check that the fixes introduce no new vulnerabilities. The people who found the issues are the people who check the fixes.
Stage 5: Formal verification and the bug bounty
These two run at the same time. Dowsers specify and prove the critical properties of the selected contracts, while a pre-launch bug bounty gives researchers a clear channel to disclose anything still standing before your contracts hold real money.
When it fits
The Bridge is the right choice when your launch needs coverage across applications, infrastructure and contracts; when your protocol has critical properties that benefit from formal verification; and when you want a defined workflow through to pre-launch readiness rather than a sequence of separately negotiated engagements.
The DualGuard contest and bug bounty are priced as usual. Work delivered by partners is priced by those partners.
Scope it with us.
Tell us what you are shipping and when you launch. We come back with scope, timeline and a price, usually within two working days.
