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
Have been trying to fire up a private network based largely upon the Goerli dumpgenesis with Clique PoA
If I keep the following lines in the genesis that make the network think it's post-merge (so I can use PUSH0), it switches to PoS and searches for a beacon chain before falling over quite quickly:
If I remove these options, then the network remains PoA but PUSH0 does not work (i.e. London)
I note a similar issue was raised under #27327 which resulted in code changes, which fires up a simulated beacon chain by using the --dev switch. But this is PoS and not PoA.
Is it possible to run a private PoA network that is compatible with Shanghai/PUSH0?
The text was updated successfully, but these errors were encountered:
To make the beacon chain permissioned (as in PoA), you would have to modify the deposit contract (as Sepolia does). But I'm not sure the Geth team can help you with that, it's pretty much out of scope for the client development.
Is it possible to run a private PoA network that is compatible with Shanghai/PUSH0?
Unfortunately not. Clique was a very simple change of PoW/Ethash to make it work with signatures. The switch to PoS introduced a lot of new changes that cannot be backported into Clique itself.
Whilst the PUSH0 might be doable, that would mean forks mean different things on different networks, which we are against with Geth. We've always committed to follow the Ethereum specs, so any network based off of Geth needs to do the same to.
TL;DR: You need a merged private network with all the bells and whistels.
Have been trying to fire up a private network based largely upon the Goerli
dumpgenesis
with Clique PoAIf I keep the following lines in the genesis that make the network think it's post-merge (so I can use PUSH0), it switches to PoS and searches for a beacon chain before falling over quite quickly:
If I remove these options, then the network remains PoA but PUSH0 does not work (i.e. London)
I note a similar issue was raised under #27327 which resulted in code changes, which fires up a simulated beacon chain by using the
--dev
switch. But this is PoS and not PoA.Is it possible to run a private PoA network that is compatible with Shanghai/PUSH0?
The text was updated successfully, but these errors were encountered: