# Pre-Launch Bounty

* shorter in duration
* smaller in payout
* more situational in use

Compared with post-launch bug bounties, pre-launch bug bounties are usually:

Pre-launch bug bounties are not the default path for most teams. They are typically used only when launch timing, release complexity, or deployment sequencing creates a meaningful pre-mainnet window.

* giving whitehats an incentive to report issues before deployment
* creating a formal disclosure path during the final stretch before launch
* adding one more layer of external scrutiny before code reaches production

In that window, a pre-launch bug bounty can help by:

A pre-launch bug bounty is a more specific type of Web3 bug bounty used before a protocol goes live. <br>

**Most protocol teams ultimately want a post-launch bug bounty on live code, but a pre-launch bounty can be useful when there is still a gap between audit completion, fix review, and mainnet deployment.**\
\
**Note:** Unlike an audit contest, which is a fixed pre-launch review event designed to pressure-test a codebase at scale, a pre-launch bug bounty is a narrower disclosure program used to keep incentives active during the gap between fix review and mainnet launch.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sherlock.xyz/bug-bounties/pre-launch-bounty.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.