You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
Description
The transaction 0x3839cb0c3d4c94e9fcb3f59e054f34f5dee025c3e651ff5fc52e36821c300bef transfers 13.915316914625093691 ETH to coinbase. However, mev-inspect cannot identify this transfer but labels it as 0.
Labeled by
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
.mev-inspect-py/mev_inspect/transfers.py
Lines 32 to 49 in 26aa190
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?The text was updated successfully, but these errors were encountered: