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
Are you referring to the fee solvers set to cover execution costs?
Then we would have to coordinate with solvers as they would have the change their algorithms.
In the (hopefully somewhat) near future we might change the accounting to never use the fee computed by the autopilot: protocol fees are not computed there anyways[0] and the network fee would just count towards slippage. Then it does not matter how it is computed. It would just be a way of communicating the directional price of orders to the driver.
[0]: It would be great if they were, though. E.g. as additional entry in the fee_policies table or a new table. Having code for protocol fees in the autopilot to check scores and populate protocol fees for consumption in our accounting would really help.
Problem
#2701 (comment)
Should we skip converting the total fee to sell token before converting it into native token?
This might introduce difference in the final result, since we use different external prices to convert into native token.
Solver team might also have some comments on this cc @harisang @fhenneke
The text was updated successfully, but these errors were encountered: