Coordination-Thread: Merge Göerli execution-testnet with Prater consensus-testnet

[q9f]

This is an early notice to the Göerli validators that the intention is to merge(TM) the Goerli execution-testnet with the Prater consensus-testnet. In case of a merge, Clique-POA validators will be relieved from their duty and replaced by the Beacon-POS validator set of the Prater network.

Tagging current validators @q9f @roninkaizen @igorbarinov @jparyani @prestonvanloon @tkstanczak @egalano @Errorific @karalabe - if you want to continue validating after the merge, make sure you have a Prater validator.

• Prater: eth-clients/eth2-networks/shared/prater
• Deposit Contract: 0xff50ed3d0ec03aC01D4C79aAd74928BFF48a7b2b (Göerli -> Prater)

cc @parithosh

[prestonvanloon]

Thanks @q9f!

As I understand it, Goerli sealers will continue to perform their work until the terminal total difficulty is reached and then these sealers can be safely turned down/off.

How will we coordinate a difficulty change in Goerli clique?

[q9f]

I don't think there should be much of a difference, we just have to select a sensible terminal total difficulty. Each block in clique adds 1 or 2 difficulty.

[q9f]

Updated the website https://goerli.net/ 🤓

[q9f]

I activated 20k validators on Prater on behalf of Goerli.

https://prater.beaconcha.in/blocks?q=Goerli

[q9f]

created a web app for block numbers and difficulties: https://ttd.goerli.net/

[ryanschneider]

@q9f will we need to update our current Clique validator to run alongside a CL pair or will configuring them w/ a new EL that accepts the TTD be enough?

[q9f]

@q9f will we need to update our current Clique validator to run alongside a CL pair or will configuring them w/ a new EL that accepts the TTD be enough?

I have my EL authority on a different machine than the CL validators, but it should be perfectly fine to have both on the same machine.

[timbeiko]

Goerli has now merged 🎉 ! Should we close this?

[q9f]

🎉

[ryanschneider]

Sorry i should’ve been more clear. I maintain the Infura clique signer. What updates, if any, are required for the existing clique signers to make sure the chain completes the merge? For example do we need to enable the engine API on our signer and pair it with a CL, or update the EL to a new version that accepts a TTD, or simply do nothing and shut down the clique signer once the merge completes?

…

On Fri, Jun 10, 2022 at 1:18 AM Afri ***@***.***> wrote: @q9f <https://github.com/q9f> will we need to update our current Clique validator to run alongside a CL pair or will configuring them w/ a new EL that accepts the TTD be enough? I have my EL authority on a different machine than the CL validators, but it should be perfectly fine to have both on the same machine. — Reply to this email directly, view it on GitHub <#98 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAANCEBY5YOLFGNISO5UMO3VOL24BANCNFSM5ROOXPTQ> . You are receiving this because you commented.Message ID: ***@***.***>

[parithosh]

Now that Goerli has been merged, there's no reason to run the clique signers anymore. They can be shutdown.