mirror of https://github.com/ethereum/go-ethereum
I know there has been prior discussions on handling that. I think it would be fine to add the last extra miles so it's possible to better test the chain in various conditions, for me around tracing in particular. It appears the code of the simulated beacon is now already architectured to enable easily support different forks with the `newPayload` function that determines how to construct the right payload based on the the parameters pass to it. Seems that it's relatively easy to also select the right payload version based on the blockchain state. I understand that could be seen as an extra maintenance burden though. If there is consensus on merging the PR, happy to check to also handle V1 is seen important.pull/31084/head
parent
3fcbb6735e
commit
452c349e7f
Loading…
Reference in new issue