> 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/community-judging.md).
# Community Judging
#### What’s in it for the Community Judges?
**5%** of the value of the contest pot will be set aside **as rewards for judges**. If a contest has a $50,000 pot, then the portion of the judging pot that will be publicly available is $2,500.
There’s no requirement to judge all of the issues submitted in a contest. When judging an issue you think is valid, there's no requirement to judge the likelihood or impact of that issue.That being said, participating in a community judging will always affect your ranking on the judges leaderboard.
On the long run, you might be selected as one of the 2 Lead Judges based on your performance.\
As you participate in community judging, you will accumulate Judging Points for each spec(Language, protocol category, fork origin), that score starts at 10. Only the community judging will affect your leaderboard ranking and chances of being selected as a Lead Judge.
#### How can I Become a Judge?
All contest participants can participate in the community judging.
#### What is Community Judging?
Community Judging is a contest where hundreds of Judges can contribute to judging issues submitted during the security review contest. **5%** of the contest pot is allocated to the judging pot. Judges get rewarded if they are in the **top-5**.
If you want to participate, you can click on any issue to view the issue description, vote on the validity status (valid / invalid), the likelihood (High / Medium / Low) and the impact (High / Medium / Low).
#### Community Judging Timeline
Judging starts right after the security review contest ends. You can find it in the [Contests](https://staging.dualguard.xyz/contests?status=JUDGING\&page=%221%22) section of the DualGuard website. It will be available for any contest in the “Community Judging” stage.
Lasts a fixed number of days (# of issues / 50) days (for example 500 issues would be 10 days), with a minimum of 2 days.
#### Key Features of Community Judging
* You can judge only a subset of the issues and still get paid, there are no penalties for guessing
* You can judge only the validity status of issues and still get paid
* Judging contests are finalised after the deadline set before the start of the community judging phase
* Check out the flow chart below to know how to score points when judging an issue
#### How do I get Rewarded?
The Community Judging Pot will be distributed amongst the **top-5 participants** as each will receive **1%** of the Total Prize Pool, the Community Judging Pot being **5%** of the Total Prize Pool. The **ranking** will be base on the **points accumulated from the judging contest**.
#### How do I Earn Judging Points for a Certain Spec?
This is very similar to the scoring system for the guards' leaderboad. We tailored an example so it's clearer for you.
#### Example
For simplicity purposes we're considering there was only 3 submissions in this example showing the results of the 3-day judging contest for a Lending Protocol in Rust.
**These are the Lead Judges final decisions:**
* issue A: Valid - Impact: High - Likelihood: Low
* issue B: Valid - Impact: Medium - Likelihood: High
* issue C: Invalid
**These were the community judges' votes:**
* Alice judged issue A as Invalid
* Alice judged issue B as Valid
* Alice judged issue C as Invalid
* Bob judged issue A as Valid - Impact: High
* Bob judged issue B as Valid - Likelihood: Medium
* Bob judged issue C as Valid - Impact: High - Likelihood: Medium
* Eve judged issue A as Valid
* Eve judged issue B as Valid - Impact: Medium - Likelihood: High
* Eve judged issue C as Valid
**Points Scored by the Judges in the contest:**
* Alice: -1 + 1 + 1 = 1
* Bob: 1.5 + 0.5 + -1 = 1
* Eve: 1 + 2 + -1 = 2
**Judging Points Earned by the Judges Before this Contest:**
| Judges | Lending Score | # of Contest Days |
| ------ | ------------- | ----------------- |
| Alice | 30 | 50 |
| Bob | 70 | 40 |
| Eve | 10 | 0 |
| Judges | Rust Score | # of Contest Days |
| ------ | ---------- | ----------------- |
| Alice | 30 | 30 |
| Bob | 10 | 0 |
| Eve | 20 | 10 |
**Now we apply this formula:**
NewScore = PrevScore x (ContestDaysBeforeThisContest / TotalContestDays) + (contestScore / SumOfContestScores) x SumOfPrevScores x (ContestDaysForThisContest / TotalContestDays)
**We obtain these scores for the Lending Spec:**
* Alice: 30 x (50 / 53) + (1 / 4) x 110 x (3 / 53) = 29.86 ⇒ 30
* Bob: 70 x (40 / 43) + (1 / 4) x 110 x (3 / 43) = 67.03 ⇒ 67
* Eve: 10 x (0 / 3) + (2 / 4) x 110 x (3 / 3) = 55 ⇒ 55
**We obtain these scores for the Rust spec:**
* Alice: 30 x (30 / 33) + (1 / 4) x 60 x (3 / 33) = 28.64 ⇒ 29
* Bob: 10 x (0 / 3) + (1 / 4) x 60 x (3 / 3) = 15 ⇒ 15
* Eve: 20 x (10 / 13) + (2 / 4) x 60 x (3 / 13) = 22.31 ⇒ 22
#### How can I escalate an issue if I disagree with the outcome?
Escalations happen right after the preliminary results are released, you should find the contest you participated in right [here](https://staging.dualguard.xyz/contests?status=ESCALATIONS_OPEN\&page=%221%22). To escalate an issue you need to leave a quality comment on that issue. There are 72 hours to escalate an issue after the release of the preliminary results.
#### What if I submit spam issues in the contest so I can earn rewards for them in the judging contest?
If a Guard does not meet the Payout Threshold after a contest, the issues they submitted in the contest will not count for judging rewards.
#### What happens with the score of the Lead Judges?
It stays the same, it can only change through a participation in a judging competition.