-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Analysis without other submissions #142
Comments
Agreed. Otherwise, it turns into chatbot driven analysis reward pot farming. |
Majority of the analysis reports don't add anything to the Sponsors as the reports only provide functionality features, summary of the contracts etc. I definitely agree with that there should be an access control to submit analysis reports. |
Totally agree with you. Maybe we should also add a requirement where the analysis can get a reward only if there is at least 1 valid H/M submitted by the Warden? Unless the contest has zero valid H/M submissions, in that case this rule shouldn't be applied. |
@dmvt is the requirement that they are valid H/Ms ? |
Not necessarily. More that effort was put into them. |
so this adds another hoop a judge has to jump through to manually validate? IE is this H/M satisfactory enough in order for me to consider their Analysis report? |
@dmvt from a tooling perspective, an option that might be simpler to implement would be to restrict access to the Analysis submission form to only wardens who have at least one valid HM on the C4 leaderboard. (This could be all-time or time-constrained.) What do you think of that option, vs submitting a well-argued HM to the same audit? |
What about both?
|
I've also noticed the recent increase in professional chatbot wardens who only submit Analyses. Perhaps the simplest solution would be to limit Analysis submission to Wardens with backstage access?
|
I propose a change to only allow the submission of an advanced-analysis if at least 1 high or medium risk issue has been submitted.
The text was updated successfully, but these errors were encountered: