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
Long story short, this is a valid tx hash that had a valid state transition and emit logs on the EVM. The responses are just missing in some RPC methods.
Seid version
Chain ID
Sei Pacific - 1329
Describe the bug
Running
eth_getBlockReceipts
on block98182138
returns invalid EVM tx hash0x20060de0db9b36ccc8006267b254ea4526739bd95493c51fe3a82952fdbb4cb0
To Reproduce
eth_getBlockByNumber
doesn't return the tx hasheth_getBlockReceipts
doesTrying to lookup information about that hash returns
null
{"jsonrpc":"2.0","id":1,"result":null}
Expected behavior
0x20060de0db9b36ccc8006267b254ea4526739bd95493c51fe3a82952fdbb4cb0
should not be in the result ofeth_getBlockReceipts
.Additional context
The transaction looks to be a non-evm tx ], removing the
0x
from the hash, it shows up on the explorer https://seistream.app/transactions/20060DE0DB9B36CCC8006267B254EA4526739BD95493C51FE3A82952FDBB4CB0The text was updated successfully, but these errors were encountered: