Skip to content
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

Update and extend unusual slippage query to all chains #98

Merged
merged 3 commits into from
Dec 23, 2024

Conversation

harisang
Copy link
Contributor

@harisang harisang commented Dec 20, 2024

This PR updates the outdated version of the query that was in this repo (the phalcon explorer view link was missing) and also extends it to work for all chains.

Changes have already been applied and can be tested here:
https://dune.com/queries/2332678?start_time_d83555=2024-12-10+00%3A00%3A00&end_time_d83555=2024-12-17+00%3A00%3A00

Copy link
Contributor

@fleupold fleupold left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, would it be possible to add a column with "network + protocol fee" to this table? This would make it easier to review as from the phalcon link I get the total slippage (including fee) from which I have to deduct the fee in order to check if the value align with our slippage accounting.

@harisang
Copy link
Contributor Author

Nice, would it be possible to add a column with "network + protocol fee" to this table? This would make it easier to review as from the phalcon link I get the total slippage (including fee) from which I have to deduct the fee in order to check if the value align with our slippage accounting.

Will address it in a follow-up PR. Opened a relevant issue
#101

@harisang harisang merged commit 5f30a95 into main Dec 23, 2024
2 checks passed
@harisang harisang deleted the extend_unusual_slippage_query_to_all_chains branch December 23, 2024 12:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants