-
Notifications
You must be signed in to change notification settings - Fork 11
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
Analyse sandwich attacks on v3 #206
Comments
Aggregated view here |
To view all transactions: https://dune.com/queries/4532901/7566569 |
V3 had a high percentage of sandwich attacks on 25/12, but on average it has been below V1 and V2 |
trend has been of growth over the past 2 days for v3 |
switched to dex.sandwiches |
|
Looking at the codes dex.sandwiches (dbt_subprojects/dex/macros/models/dex_sandwiches.sql) identifies the attack transactions, while dex.sandwiched (dbt_subprojects/dex/macros/models/dex_sandwiched.sql) identifies the victims so, for the purpose of this analysis I believe it makes more sense to look at dex.sandwiches (i.e. the percentage of the volume of a pool that is due to sandwich attacks, representing a very toxic flow) |
Here is a query for the sandwiched trades on V3 considering both dex.sandwiches and dex.sandwiched: https://dune.com/queries/4665624. Checking if results actually make sense. WIll leave the issue open so we discuss on call |
first scope: dex_sandwiched table
The text was updated successfully, but these errors were encountered: