-
Notifications
You must be signed in to change notification settings - Fork 90
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
feat: Reject solution with violated solution quality #2713
Comments
nit: I think larger score should still be allowed (as long as each order was filled at least as good as promised). |
With the new plan, where we want to completely remove However, since |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
This issue has been marked as stale because it has been inactive a while. Please update this issue or it will be automatically closed. |
Problem
Inspired by #2712, we should also check if the reported winning score (part of the
/solve
response) is equal to score calculated from winning calldata (part of the/reveal
response).This is to make sure that solvers are not reporting one score for competition and then intending to settle other score. This is a direct violation of competition rules and solver should not be allowed to settle.
The same checks should be added for reported trades and clearing prices.
Suggested solution
Implement check at the competition time and reuse decoded settlement from #2712.
Alternatives considered
The check could be implemented in the postprocessing as well, but early rejection during competition makes more sense to me, as it can catch bugs with driver score calculation early and avoid circuit breaking a solver because of score violation.
Acceptance criteria
If scores are different, solution should be rejected.
If orders are different, solution should be rejected.
If clearing prices are different, solution should be rejected.
The text was updated successfully, but these errors were encountered: