In the early days (before many exotic interactions were happening) this case statement was a fairly-accurate count of the number of dex swaps in a batch. However now we are seeing many other function selectors occurring in settlement interactions. Its probably too difficult to capture/classify dex swaps
Recommend deprecating this field.
|
sum( |
|
case |
|
when selector != 0x2e1a7d4d -- unwrap |
|
and selector != 0x095ea7b3 -- approval |
|
then 1 |
|
else 0 |
|
end |
|
) as dex_swaps, |
(also copied over through all networks where cow is deployed).
cc @harisang, @fhenneke
In the early days (before many exotic interactions were happening) this case statement was a fairly-accurate count of the number of dex swaps in a batch. However now we are seeing many other function selectors occurring in settlement interactions. Its probably too difficult to capture/classify dex swaps
Recommend deprecating this field.
spellbook/dbt_subprojects/hourly_spellbook/models/_project/cow_protocol/arbitrum/cow_protocol_arbitrum_batches.sql
Lines 39 to 46 in b111316
(also copied over through all networks where cow is deployed).
cc @harisang, @fhenneke