You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A solver is allowed to return multiple solutions to the driver. The driver will then simulate, score and rank all the solutions and only remember the winning solution. Then on every new block it will check if the winning solution still works. That was done to prevent the driver promising solutions that would no longer work which would result in penalties for the connected solver.
Acceptance criteria
The current approach can lead to issues where on a new block only the best solutions starts reverting but not the other solutions provided by the solver. In that case the driver should pick the best still working solution of the bunch and not just invalidate the previously best solution and give up.
The text was updated successfully, but these errors were encountered:
I think this requires a bit of a refactor. The /settle endpoint receives a solution_id from autopilot which should be different for each settlement. Else we can make auction_id mandatory and just execute the best available settlement for the given auction_id.
I think you are right this is problematic. Driver shouldn't submit a solution different to the one that autopilot allowed it to settle based on the best score, otherwise the whole competition is useless.
Background
A solver is allowed to return multiple solutions to the driver. The driver will then simulate, score and rank all the solutions and only remember the winning solution. Then on every new block it will check if the winning solution still works. That was done to prevent the driver promising solutions that would no longer work which would result in penalties for the connected solver.
Acceptance criteria
The current approach can lead to issues where on a new block only the best solutions starts reverting but not the other solutions provided by the solver. In that case the driver should pick the best still working solution of the bunch and not just invalidate the previously best solution and give up.
The text was updated successfully, but these errors were encountered: