The Judging Process
Last updated
Last updated
The judging phase is critical to Cyfrin CodeHawks' competitive audits, ensuring its contests' integrity, transparency, and fairness.
Here's an in-depth look at how the judging process works.
We split the judging process into two phases:
Lead judging
Both happen after the contest's closed submission window, lasting an average of ~ three weeks. Once judging begins, further submissions through the CodeHawks Audit Portal will be disabled.
All eligible community members can join the community judging phase as judges.
Community Judges will use the CodeHawks portal to submit their assessments to the Lead Judge for each contest, to earn rewards based on their performances and accuracy.
Find more information on Community Judging and how it works .
You can check out more eligibility information !
A member of the Cyfrin team or an appointed, reputable, and esteemed community member may be invited to assist in judging.
While submission volume certainly plays a part, the average judging period is ~2.5 weeks.
The judging process at CodeHawks is meticulously designed to uphold the highest standards of fairness and clarity. We're continually evolving our methods to reflect the best practices and ensure that every participant receives thorough, unbiased feedback.
For further inquiries or more detailed insights into our processes, please .