It's still early to prepare for the merge

[remyroy]

Some instructions on https://launchpad.ethereum.org/en/merge-readiness might need to wait for an actual TTD value to be published or some clients to update with a baked in TTD value for Mainnet before stakers actually apply them on their machine. Phrasing or notices should be added to account for that.

[hwwhww]

Hi @remyroy 👋

I was hesitating about it for this reason as well, but I think we could find a balance between (i) providing the readiness now and (ii) letting stakers understand that we still need the last puzzle to solve it.

@remyroy @wackerow what do you think about we add more warnings around "I am running my own EL/CL client"? For example:

• add introduction of TTD and make it clear that mainnet TTD is unset
• invalidate the checkbox for now?

[wackerow]

Yeah, I think see your point. @remyroy are you saying that even if users check off all these boxes, they will still have a few things to do before the actual upgrade?

The intent was certainly not to imply that, and I can definitely see how it could add some confusion.

Assuming I understand you correctly, I agree with @hwwhww that we should just make a note of this. Hesitant to remove everything entirely as it's otherwise public info that is out there, just consolidated to help stakers get ready. @hwwhww I kind of like the idea of adding a final checkbox that is disabled, regarding setting the TTD, and we can add a note to make it clear this is not yet available, and to stay tuned.

I am happy to put up a fix for this

[remyroy]

For instance, some execution client will not open their Engine API endpoint until a TTD is configured (either manually or through their baked in network configuration). There might be a chance to break a validator setup is someone tries to configure everything too early.