Beacon root contract in dev mode and private chains

[s1na]

EIP-4788 introduces a system contract which is deployed as a normal contract to the state. However it is required for networks which have the Cancun fork enabled. It is a bug when a dev chain or private chain with Cancun enabled is deployed and it is missing the beacon root contract.

For dev-mode, we should add the beacon root contract to the genesis alloc. As for private chain, IMO the least we should do is refuse geth init in case Cancun is enabled and the genesis alloc is missing the beacon root code at the correct address.

[holiman]

For dev-mode, we should add the beacon root contract to the genesis alloc.

I agree

the least we should do is refuse geth init in case Cancun is enabled and the genesis alloc is missing the beacon root code at the correct address.

Why?
If they want it: deploy it. If they don't fine, the system call will have zero side-effects.

[holiman]

Sorry, I forgot there was still a task to do here (add the beacon root contract to the genesis alloc.)

[hopinheimer]

Hi @holiman can I work on this?

[0xbeny]

WIP, The PR is finishing soon :)

Hi @holiman can I work on this?

[0xbeny]

Kindly find the implementation here: #29655