-
Notifications
You must be signed in to change notification settings - Fork 126
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
Fix misclassified transactions #13
Comments
this tx 0x83dd147043e1ceec0e51adc4be46db68e9351cce71103236d8bb7c72713e76b7 classified as a MEV profit of $954,665.13 shows up as a reverted tx on Etherscan: https://etherscan.io/tx/0x83dd147043e1ceec0e51adc4be46db68e9351cce71103236d8bb7c72713e76b7 |
0x8837130fe51f7ef3b27955bca9f6074a4785ebff8fc919ea8883ea5e05592123 this one's revenue feels suspicious, it's a volume of ~$3m and recorded a revenue of ~$3m, seems unlikely or a hack These are all DRC transactions that seem like deflationary token hacks, I wonder if we should exclude them? They currently make up most of our top MEV txs leaderboard |
This the yearn recycler, I've patched it here and should be manually removed from the db. Re: DRC transactions, I'd remove them from the db, and I'll add it to the type of things we ignore. Re: reverted with >0 profit, that's intended, it might be best to just filter your SQL queries where status != reverted. |
DRC transactions are no longer processed since #38 |
Just a comment it's a good thing we don’t seem to be categorising the Eminence exploits (like this one https://etherscan.io/tx/0x3503253131644dd9f52802d071de74e456570374d586ddd640159cf6fb9b8ad8) We have these two txs in our db but aren't accounting any revenue for it when they're highly profitable (each ~153 eth it seems): Not really misclassified but potentially smth to look out for here: for this tx we seem to have a diff revenue than Arthur Gervais et. al. paper (they have 92.23 ETH, we seem to have 72 ETH) 0xdc1f3dea442c587799a0c4740f12e4e2ad10c5c45157612a3c9c3f082698a4cd |
|
drops mic |
https://etherscan.io/tx/0x7461f9261d1f50adaafca7377642b70504094f235ffd6c85113df1556e80f43a this one tx is categorized as profit of ~$100k USD when it just seems like a 1Inch swap? in our db, revenue is 625,303,946,340,502,100,000 🤔 |
Good catch, #39 fixed here |
I'll have more soon but all these are Flashloan-based, MakerDAO-loan opening based arbs we classify in our db as 0 revenue when I don't believe they are 0x448b94d1eed3449d7427f769341d7789474a2db60820b9ed9c494af0ae6b049c Different behaviours that are worth checking: |
another zapper address: 0x80c5e6908368cb9db503ba968d7ec5a565bfb389 |
The Maker CDP +Curve transactions (e.g. 0x448b9, 0x0fa6b) are part of Abstracted Finance's CloseShortDAI script. They basically call their dsproxy which calls to their script to automate some actions. Shouldn't be flagged as revenue generating! |
Aren't there still arbs in these txs? Like the very first one looks like they walked off 33k USDc after reimbursing their DyDx flashloans? |
We classified this arb as 865k revenue https://etherscan.io/tx/0x2d346682871ecb407ee25af4de2b9998e70b4621116acafae7e07b6b79f585e3 Another example of the same issue (classified as $303k revenue in our db): https://etherscan.io/tx/0xde13ef98fd52c4116703ee9c8d4d82a9fb449612112e35450cefc1570b556153 classified this Aave liquidation as $837k revenue https://etherscan.io/tx/0xa72072f5041bcde89c560ba12cc00b22a87779ee369dbff81a78bba26d35e989 when it's a (828.6k - 797.7k) DAI 'true' revenue. It seems we overlook the 'Liquidator Repay' step of the liquidation process Other examples of the same issue: |
https://etherscan.io/tx/0x8b89589c6afb0e7a6e11afe04efa21312e078764986b692ef7b4c76f3f28ceef this is 0x exchange proxy we've classified as |
https://etherscan.io/tx/0x21bdb4fffb209d6f7f0a28df5cfd6b8f736bc5ad529a1d33eba0c661476d826e this is an arb of profit ~1ETH classified as $217k in our db, it looks like we ignore either the first or second step of ETH transfer to either Uniswap or Uniswap Another example: https://etherscan.io/tx/0xf67ec3abc9ce22be956ca7efa951115834fc37541f75f2e0da8b1b27c5370563 |
Txs below:
The text was updated successfully, but these errors were encountered: