Scoring fix live; stricter plagiarism check coming
Share
Oro deployed a scoring pipeline improvement that increased composite scores to 1.0 across all categories by removing a guard clause blocking supplemental searches. The fix is now live. Starting after today's race, the subnet will enforce stricter code-similarity checks on agent submissions to prevent cosmetic forks; non-compliant submissions will be rejected at submission time.
- •Scoring composite moved 0.8571 → 1.0 via guard-clause removal enabling broader LLM judging.
- •Stricter plagiarism check rolls out post-race #44; light edits and renames no longer evade detection.
- •Cosmetic forks will bounce; miners encouraged to do real differentiating work before next submission.
- •Team monitoring improvement under live traffic; edge-case feedback requested.
Distilled from 22 team messages in the official Bittensor Discord. Generated by Claude Haiku 4.5.
View original messages
- Discord message 1508997122886729859
- Discord message 1508997862594183169
- Discord message 1509001045781774456
- Discord message 1509003285401436180
- Discord message 1509005192690012181
- Discord message 1509008699102859425
- Discord message 1509009443956985976
- Discord message 1509010534190546964
- Discord message 1509018535114965102
- Discord message 1509020021270118553
- Discord message 1509021397111013437
- Discord message 1509022871886893126
- Discord message 1509028084651659405
- Discord message 1509056850866475089