See top keepers: https://app.keeperdao.com/.
But only their "hiding game" should be excluded from MEV. This is their whitelisted order system on 0x that is generating massive MEV over the last 3.5 weeks. Finding hiding game orders is quite a bit more difficult. would need to parse MEV txs and exclude any arbitrages that include a 0x order with a defined tx.origin address. these orders are not in-scope for MEV-geth, and are not executable by anyone other than KeeperDAO whitelisted addresses.
See this arb: https://etherscan.io/tx/0x469dc411488a64d48be57541d042bf7cda823b66188c30068bb536de71564460
they have a trace to 0x exchange proxy with the following txdata: 0xaa77476c000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48000000000000000000000000fa5047c9c78b8877af97bdcb85db743fd7313d4a00000000000000000000000000000000000000000000000000000003f5476a000000000000000000000000000000000000000000000000020aa4c2a57ce98000000000000000000000000000cd1630a9789ddf0ca780397d74b57a340776e2500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bd49a97300e10325c78d6b4ec864af31623bb5dd000000000000000000000000000000000000000000000000000000000000002d00000000000000000000000000000000000000000000000000000000603a6e8a0000000000000000000000000000000000000000000000000005bc53757668780000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000001b07366285db87fd0b6b3061b5e93c4805ec0daf9848def2b330649467730b31636aa34eda29cdf4c15462bb669d3a5ce48bd2c61969e625d70ea180c1832c235f00000000000000000000000000000000000000000000000178fc5d6f7ec06331
the "bd49a97300e10325c78d6b4ec864af31623bb5dd" section of the txdata is the tx.origin argument for this 0x v4 order. Only addresses that have been whitelisted by 0xbd49a97300e10325c78d6b4ec864af31623bb5dd are able to take this order. so Ankur recommends just excluding 0x3D71d79C224998E608d03C5Ec9B405E7a38505F0 until we build parsing logic to identify + exclude all txs that involve whitelisted 0x orders.
List:
0x3D71d79C224998E608d03C5Ec9B405E7a38505F0 (account for ~$11.4m in Extracted MEV)
0xbd184c08f82f40e5f3e62ba66f668448fa6c764a
0xa99a878c64c0699d112d2e5da73f043b19663ecb
0xc31247e806c58d8ebe4788ce5d737caebc8e9696
0x85115a7e17fed39252313ad32d0271a786398142
obadiaa
commented
3 years ago
See top keepers: https://app.keeperdao.com/. But only their "hiding game" should be excluded from MEV. This is their whitelisted order system on 0x that is generating massive MEV over the last 3.5 weeks. Finding hiding game orders is quite a bit more difficult. would need to parse MEV txs and exclude any arbitrages that include a 0x order with a defined tx.origin address. these orders are not in-scope for MEV-geth, and are not executable by anyone other than KeeperDAO whitelisted addresses.
See this arb: https://etherscan.io/tx/0x469dc411488a64d48be57541d042bf7cda823b66188c30068bb536de71564460 they have a trace to 0x exchange proxy with the following txdata:
0xaa77476c000000000000000000000000a0b86991c6218b36c1d19d4a2e9eb0ce3606eb48000000000000000000000000fa5047c9c78b8877af97bdcb85db743fd7313d4a00000000000000000000000000000000000000000000000000000003f5476a000000000000000000000000000000000000000000000000020aa4c2a57ce98000000000000000000000000000cd1630a9789ddf0ca780397d74b57a340776e2500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000bd49a97300e10325c78d6b4ec864af31623bb5dd000000000000000000000000000000000000000000000000000000000000002d00000000000000000000000000000000000000000000000000000000603a6e8a0000000000000000000000000000000000000000000000000005bc53757668780000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000001b07366285db87fd0b6b3061b5e93c4805ec0daf9848def2b330649467730b31636aa34eda29cdf4c15462bb669d3a5ce48bd2c61969e625d70ea180c1832c235f00000000000000000000000000000000000000000000000178fc5d6f7ec06331the "bd49a97300e10325c78d6b4ec864af31623bb5dd" section of the txdata is the tx.origin argument for this 0x v4 order. Only addresses that have been whitelisted by 0xbd49a97300e10325c78d6b4ec864af31623bb5dd are able to take this order. so Ankur recommends just excluding 0x3D71d79C224998E608d03C5Ec9B405E7a38505F0 until we build parsing logic to identify + exclude all txs that involve whitelisted 0x orders.
List: 0x3D71d79C224998E608d03C5Ec9B405E7a38505F0 (account for ~$11.4m in Extracted MEV) 0xbd184c08f82f40e5f3e62ba66f668448fa6c764a 0xa99a878c64c0699d112d2e5da73f043b19663ecb 0xc31247e806c58d8ebe4788ce5d737caebc8e9696 0x85115a7e17fed39252313ad32d0271a786398142