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
# Description
Tackles #2083 and
#2084.
Defines fee policy configuration parameters. Based on them, we can take
the protocol fee as a cut from price improvement or as a percent of the
order volume (fixed fee in absolute value will be implemented later).
On top of that, we also need two flags, for skipping in-market limit
orders and twap orders, since default initial configuration will be to
run the fee experiment only for out-of-market limit orders.
Note that the quote is not forwarded to the `driver` at this moment,
since it is not needed for out-of-market limit orders.
Also note that I am missing the cap for absolute value of protocol fee
(default value 1000$ or 0.5ETH) but this cap is still discussed (will be
added later if needed).
Skipping forwarding protocol fee parameters for in-market limit orders
will be done in a separate PR.
# Changes
<!-- List of detailed changes (how the change is accomplished) -->
- [ ] Defines basic parameters for protocol fee calculation.
- [ ] Forwards protocol fee parameters to the driver.
Problem
Autopilot should have a set of configuration parameters to define the protocol fee. There are two ways we are considering to take the fee:
This task captures the work needed to implement (1).
It should be possible to define parameters
The default values should be:
Acceptance criteria
The text was updated successfully, but these errors were encountered: