Judging Process
Overview
The judging phase represents a critical component of Cyfrin CodeHawks' competitive audits, designed to maintain "integrity, transparency, and fairness" across contests.
How the CodeHawks Judging Process Works
Submission and Initiation
Once a competition's submission period closes, the judging period commences.
Lead Judging Phase
A Cyfrin team member or appointed community expert serves as Lead Judge. The typical judging duration is approximately 2.5 weeks, though submission volume affects timeline.
During this phase, the Lead Judge evaluates each submission's validity and severity.
Valid Findings: When a submission is deemed valid, judges assign a "Finding Tag" that categorizes the vulnerability and indicates its type and severity level.
Invalid Findings: Submissions deemed invalid receive an "invalidation reason" label. Judges may provide additional explanatory comments about the rejection.
Competition Conclusion
Following preliminary judgments on all submissions, competitions advance to the Appeals Period. After appeals are considered and final reviews completed, a "final report" is generated and the competition closes.
Standards
CodeHawks maintains "the highest standards of fairness and clarity" in judging methodology, continually refining processes to reflect best practices and provide participants with thorough, unbiased evaluation.