The mev-inspect will only identify the trace whose action["input"]=="0x" according to the source code. Therefore, it will ignore all traces whose input is not 0x.
In the transaction 0x3839cb0c3d4c94e9fcb3f59e054f34f5dee025c3e651ff5fc52e36821c300bef, the input of the call is 0x00000000. This link shows the detail traces:
Bug Fix
Can we remove the requirement of action["input"]=="0x"? Is it necessary to filter out other not simple ETH transfer transactions?
Description
The transaction 0x3839cb0c3d4c94e9fcb3f59e054f34f5dee025c3e651ff5fc52e36821c300bef transfers 13.915316914625093691 ETH to coinbase. However, mev-inspect cannot identify this transfer but labels it as 0.
mev-inspect
:Labeled by Etherscan:
Bug Analysis
The mev-inspect will only identify the trace whose
action["input"]=="0x"
according to the source code. Therefore, it will ignore all traces whose input is not0x
.https://github.com/flashbots/mev-inspect-py/blob/26aa190b03cfff865382818a641a125d2118b92f/mev_inspect/transfers.py#L32-L49
In the transaction
0x3839cb0c3d4c94e9fcb3f59e054f34f5dee025c3e651ff5fc52e36821c300bef
, the input of the call is0x00000000
. This link shows the detail traces:Bug Fix
Can we remove the requirement of
action["input"]=="0x"
? Is it necessary to filter out other not simple ETH transfer transactions?