If you've ever run, judged, or entered a hackathon or competition, you've probably seen the same problems: scoring lives in spreadsheets, judges can influence each other, results get finalized with little context, and participants often get no useful feedback on where they actually stood. I built OpenScore to fix that. OpenScore is a self-hosted platform for running judged competitions end to end: define a detailed rubric, import submissions from GitHub, assign judges, score independently, generate useful feedback, publish leaderboards and result breakdowns, and keep a full audit trail of how the final outcome was reached. What makes it different: - Independent judging — judges don't see each other's scores while evaluating. - Detailed rubric scoring — score individual sub-metrics, not just broad categories. - Useful feedback — comments, quick tags, and optional generated summaries. - Locked means locked — changes after finalization require a reason and are audited. - Configurable transparency — choose exactly what participants and the public can see. - GitHub snapshots — lock judging to the exact commit that was reviewed. - Verifiable results — assessment sets can be Merkle-rooted and committed to Nimiq. - Full audit history — overrides, role changes, snapshot changes, corrections, and publishing actions are traceable. The goal is also to make competitions more useful for builders. If you didn't win, you should still be able to understand where you lost points, what judges valued, and whether improving the same idea for another round actually makes sense. 🔗 Live demo: https://openscore.nimiqminiapps.com/c/miniappscycle1 💻 Source: https://github.com/NimMiniApps/OpenScore Would love feedback from anyone who's run or participated in hackathons, grant rounds, bounty programs, or other judged competitions.