Comments (4)
Bot Races are difficult to judge
We have reached a point where it's almost impossible to manually judge each report fairly. Judges have only 24 hours to assess 20 reports, some of which exceed 100k lines each (!).
Recommended Solution
- Reduce report length by dropping some categories (e.g. NC and R)
- Reduce the number of available spots as 20 is too many
Bot Races abuse "farming" issues
Currently, each variant of an issue can be "farmed" to get more points. Some concrete examples include:
This floods the report with a lot of issues, it's unfair as this behavior gets more points, and increases judging efforts
Recommended Solution
Issues that share the same root cause, and are split, should be penalized instead of awarded.
NC/R issues do not provide value to the sponsor
We need a sponsor survey to prove this, but I don't think these issues are valuable to sponsors. Nevertheless, most NC/R issues are subjective (e.g., tests should always have 100% coverage), yet they still contribute points. These issues are very easy to add, so bot racers are more inclined to include them instead of focusing on security issues.
Recommended Solution
- NC/R categories should no longer be considered valid issues
or - NC/R categories should get a fraction of L issues point-wise (e.g. 1/10 or less)
from org.
Recommended Solution For Different Severity Definitions
I think bot racer should not be able to edit reports. There should be a c4 server that our bots are running and everyones report should be automatically generated & published without any changes by racer.
from org.
Advance Knowledge of Bot Race Judge
Because of their role at Code4rena, some, but not all, bot racers know in advance who will be the judge for a bot race. Because there is a great deal of variance in how bot races are judged, and because recognizable judging patterns have arisen over time, the knowledge of who will be the judge in advance of the race represents an unfair advantage. A bot racer that knows in advance who the judge will be can tailor their report to receive a better grade by that judge. Bot racers that do not know who will judge the race are left at a disadvantage to the racers that do. (This issue was raised in #147.)
Recommended Solution
To level the playing field, one of the following options should be implemented:
- No bot racer should be allowed to know in advance who will judge a race.
- The judge for a race is known in advance to all bot racers at the same time. No bot racer would know before any other.
from org.
Bot Race Judging is Inconsistent
As there are no standardized guidelines for bot race judging, each bot race judge makes up and follows their own rules for each race. In addition, a given judge may change their judging process from one race to the next. There is not always full transparency in how bot reports are evaluated.
Recommended Solution
Bot race judging standards, designed to maximize the value of a bot race report to the sponsor, should be developed and implemented. The standards should accommodate a mostly automated judging process, allowing for human review that can more easily, effectively, and fairly be done in the short allotted time frame for judging.
from org.
Related Issues (20)
- To ensure accurate assessment of performance, a gas benchmark must be included in all gas reports. HOT 1
- Invitation audits should take into account Gas auditors HOT 1
- The bot-race pot should be splitted like the contest-pot
- Analysis without other submissions HOT 9
- Attacks which only waste gas and cost the attacker more than the victim HOT 3
- Uniques as partial credit HOT 2
- Duplicates labeled with partials (partial-25/50/75) decrease duplicates weigth, but also reduce the primary finding weigth in the overall award calculation HOT 70
- Advance Knowledge of Bot Race Judge HOT 3
- Bot Benefits HOT 4
- ERC compliance on non-EVM rollups and blockchains (e.g. Starknet) HOT 1
- Can't log in my code4rena account. HOT 2
- Disposing of warden/sponsor severity agenda in pipeline HOT 2
- Bias in Judging HOT 1
- ERC Compliance Absurdity HOT 2
- Issue identified the root causes and effects, but was considered ineffective, hoping for justice. HOT 2
- ❗️PJQA Guidelines❗️
- Discussion about Hunter/Gatherer Role HOT 7
- Validator role HOT 30
- Submissions invalidated despite being duplicates of valid reports HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from org.