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

# How Lead Judges are Selected

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

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

### For now

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

### For the Long run

Lead Judges will be chosen from the Judging 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 Judges that will be invited to lead the judging for the contest of a DEX protocol that is forking Uniswap V3 written in solidity will most probably be different Judges from those who will be selected to lead the judging for the contest of a Lending protocol written in Cairo from scratch.

In order to be a Lead Judge, you must pass 3 criteria:

1. **Compete as a Judge 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 Judging Leaderboard**
3. **Be a non-participant for the contest for which you were assigned**