> 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/security-reviews/guards/how-lead-guards-are-selected.md).

# How Lead Guards are Selected

The Lead Guard status is not permanent, it is contest-relative.

Each of the 2 Lead Guards receives a guaranteed payout that is 8% of the total prize pool.

### For now

DualGuard hand-picks the Lead Guards based on strong track records on other platforms.

### For the Long run

Lead Guards will be chosen from the Guarding Leaderboard by applying the filters that correspond to the protocol that will be reviewed. 

Those leaderboard filters include:

* languages
* protocol category
* fork origin, if the protocol is forked

The leaderboard might shape up very differently depending on the filters that are selected:

The 2 Guards that will be invited to lead the security review contest for a DEX protocol that is forking Uniswap V3 written in solidity will most probably be different guards from those who will be selected to lead the security review contest for a Lending protocol written in Cairo from scratch.

In order to be a Lead Guard, you must pass 2 criteria:

1. **Compete in ≥ 42 days on DualGuard for each of the specs that are found in the protocol that will be reviewed**
2. **Be inside the top-5 of the corresponding leaderboard**

Check out the [Scoring System](/dualguard/security-reviews/guards/scoring-system.md) to know what really matters for your leaderboard ranking.