Computing slippage for individual transactions not possible
Opened this issue · 0 comments
fhenneke commented
Restricting the slippage query to an individual transaction hash in this query is currently broken due to the table
solver-rewards/queries/dune_v2/period_slippage.sql
Lines 263 to 279 in ece65bf
which does not use the same filtering as all the other tables at the top.
Other queries for slippage do work but do not implement the correction for charging protocol fees in the correct token.
Potentially, joining on filtered_trades
might help. Then the filtering on block numbers could be removed as well.