> For the complete documentation index, see [llms.txt](https://dualguard.gitbook.io/dualguard/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dualguard.gitbook.io/dualguard/bug-bounties/pre-launch-bug-bounty.md).

# Pre-Launch Bug Bounty

Sometimes there is a gap between mitigation review and mainnet launch.

DualGuard uses a **Pre-Launch Bounty** to create a clear incentive for whitehats to disclose issues during that window.

That matters because waiting until mainnet creates worse outcomes.

An undisclosed bug can be found and exploited by a blackhat first.

It can also force the team to go through a painful relaunch or worse, have their protocol drained from its funds.

DualGuard creates a Pre-Launch Bounty for every cooperating protocol team.

The bounty starts small and increases as the launch date gets closer.

Each submission also carries a fee-on-submission amount agreed with the protocol team.

For now, that is the main way DualGuard limits AI spam.

The program also pressure-tests the mitigation review.

The payouts reserved to the 2 guards who led the contest (**≤ 8% for each)** and participated in the mitigation review is locked until the Pre-Launch Bounty window ends.

That amount is released only if no new issue of medium severity or highe,r that should have been caught during mitigation review or the contest, appears.

### Disclaimer

Protocol teams can run a pre-launch bug bounty on DualGuard without running a DualGuard contest first.

They can also run one without a prior security review. We do not recommend that approach.

For the strongest coverage, run a contest before launch on any platform, ideally on DualGuard.