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
According to the lighthouse guys this happens because Erigon returns a [] instead of a null for withdrawals. I was able to temporarily fix this by making lighthouse allow empty arrays for that region of blocks. (also confirmed that it works correctly with reth+lighthouse)
System information
Erigon version: erigon version 2.60.5-ea49defc
OS & Version: Linux
Commit hash: ea49defc
Erigon Command (with flags/config): nothing relevant set
{
"code": 500,
"message": "UNHANDLED_ERROR: ExecutionLayerErrorPayloadReconstruction(0xa93514c91306a086c40bba2282c1dc4f8ba61fb062f7f596d2d7412e514a601f, InvalidPayloadBody(\"block 0xa935…601f is merge but payload body has withdrawals\"))",
"stacktraces": []
}
Steps to reproduce the behaviour
configure lighthouse & erigon
request block at slot 6176903 from lighthouse
The text was updated successfully, but these errors were encountered:
invis-bitfly
changed the title
incompatability with lighthouse for certain pre-capella post-merge blocks
incompatibility with lighthouse for certain pre-capella post-merge blocks
Oct 14, 2024
Apparently we saved some pre-Shappella blocks into snapshots with empty
rather than nil withdrawals. This is a work-around for issues like
#12297 to avoid regenerating block snapshots. You can see the problem by
running
```
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x103716A",false],"id":1}' http://localhost:8545
```
Apparently we saved some pre-Shappella blocks into snapshots with empty
rather than nil withdrawals. This is a work-around for issues like
#12297 to avoid regenerating block snapshots. You can see the problem by
running
```
curl -X POST -H "Content-Type: application/json" --data '{"jsonrpc":"2.0","method":"eth_getBlockByNumber","params":["0x103716A",false],"id":1}' http://localhost:8545
```
Context
According to the lighthouse guys this happens because Erigon returns a
[]
instead of anull
forwithdrawals
. I was able to temporarily fix this by making lighthouse allow empty arrays for that region of blocks. (also confirmed that it works correctly with reth+lighthouse)System information
erigon version 2.60.5-ea49defc
ea49defc
lighthouse v5.2.1
mainnet
Expected behaviour
curl http://127.0.0.1:{lighthouse_port}/eth/v2/beacon/blocks/6176903 | jq
Actual behaviour
curl http://127.0.0.1:{lighthouse_port}/eth/v2/beacon/blocks/6176903 | jq
Steps to reproduce the behaviour
6176903
from lighthouseThe text was updated successfully, but these errors were encountered: