Open ncocchiaro opened 4 months ago
Updated the title of the issue. I was able to verify that this also happens on Ethereum Mainnet, with empty blocks after the Merge block (0xed14f1
), for example 0xed175b
.
On Sepolia, the blocks we were testing with happened to be on either side of the Merge, so for 0x1621a8
(last block before the Merge) we get a full-fledged response, whereas for 0x1621a9
(first Merge block) we get the empty result.
This behavior also looks to be present in erigon 2.58.1.
System information
Erigon version:
./erigon --version
:erigon version 2.60.1
OS & Version: Windows/Linux/OSX:
Linux Ubuntu 22.04
Commit hash:
9471c44e04f43a735dc9f40b74f552d706d05f78
Erigon Command (with flags/config):
Consensus Layer:
teku/v24.2.0/linux-x86_64/-ubuntu-openjdk64bitservervm-java-17
Consensus Layer Command (with flags/config):
Chain/Network:
Ethereum Sepolia
Expected behaviour
Calling
trace_block
on an empty Sepolia block like 1450408 (0x1621a8
) or 1450409 (0x1621a9
) should produce a response like the following:We would expect the two empty blocks to produce similar responses.
Actual behaviour
The call from the example above produces the expected response when made against Sepolia block 1450408 (
0x1621a8
). However, when the call is made against block 1450409 (0x1621a9
), the result field is entirely empty:Steps to reproduce the behaviour
Run the listed versions of erigon and teku to sync Ethereum Sepolia from scratch, then make the
trace_block
calls as shown viacurl
.