The weights are suggestions. Change them to fit your event, and publish the final rubric with your rules before building starts.
Eligibility check
Before scoring, confirm each project meets the submission requirements. Run check_submissions.py to confirm every contract is deployed on testnet and verified. Decide in advance whether an unverified contract disqualifies a project or only loses points.Criteria and suggested weights
Scoring scale
Score each criterion from 1 to 5, then multiply by its weight.
Example. Scores of 4, 3, 5, 3, 4 give
(4 × 0.30) + (3 × 0.20) + (5 × 0.20) + (3 × 0.15) + (4 × 0.15) = 3.85 out of 5.
Score sheet
Copy this into a spreadsheet, one row per project per judge:score-sheet.csv
Track prizes
If your event has tracks, judge each track with the same rubric, and add a track-fit question under Use of BOT Chain: does the project solve a problem the track is about?Fair judging
- At least two judges per project. Discuss differences of 2 or more points on any criterion.
- Judges declare conflicts of interest (mentored the team, know a member) and skip those projects.
- Score what you saw working, not what the team plans to build.
- Don’t penalize teams for BOT Chain limitations, such as no WebSockets. Reward good workarounds.
Next steps
Verify submissions
Check every contract before judging.
Run a hackathon
The full logistics checklist.