-
Notifications
You must be signed in to change notification settings - Fork 82
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: Protocol Fees Tracker 2: PriceImprovement over Quotes #2287
Comments
Maybe we should make this dependent on having shipped fee = 0 before then to avoid this work? (cc @olgafetisova & @harisang). Right now an order can either have a fixed user signed fee or a fee that is taken from the surplus, but never both. |
Do we also need to make sure integrators are not sending us the orders with user signed fee != 0? Otherwise, if we do not support protocol fees for those, then those orders will not pay protocol fees? |
# Description Closes task n1 from #2287
decided with @olgafetisova that it is fine to wait for fee=0 before releasing price improvements over quotes. |
# Description Closes task n3 from the #2287 ## How to test TBD --------- Co-authored-by: Martin Beckmann <[email protected]>
# Description Closes task n2 from #2287
Closing in favor of individual tasks |
Problem
In previous stage we implemented protocol fees for out-of-market limit orders: #2114
In next stage we want to charge the fee from in-market orders (both market and limit orders).
Tasks
PriceImprovement
fee policy in autopilot arguments. This fee policy should containfactor
,max_volume_cap
.PriceImprovement
fee policy in autopilot domain for each order and forward it to thedriver
. This time, fee policy additionally contains the attachedquote
.Implement custom clearing prices for market orders in SettlementEncoder.WARNING: this potentially requires A LOT of time. It would require allowing an order to have both signed
user_fee
andsurplus_fee
(through which we model protocol fees).fee_policies
and implement storing Persist Price Improvement protocol fee #2478The text was updated successfully, but these errors were encountered: