The merge from Eth1 to Eth2 will come quickly, however with such an enormous change, there might be many points that pop up. This EIP covers not solely the merge itself, but additionally modifications made to ensure this as easy as potential.
What if the PoS chain will get linked onto a minority fork?
This might occur if the block quantity was exhausting coded into the EIP and a malicious miner created a fork by proposing the precise block quantity on a transaction and it could be a multitude.
Fortunately, we do not have to fret about this because it’s the issue that’s exhausting coded into the EIP that determines when the terminal PoW block will get mined and when the primary PoS block (the transition block) begins.
What about present good contracts?
As a part of the improve, a number of opcodes might be deprecated, and new ones added in.
One notable deprecation that may have an effect on fairly just a few contracts is the issue opcode, which might be set to 0.
One other space of concern is randomness. In case your good contract relied on block hash for pseudo-randomness, it is much more insecure below PoS since block proposers can change the block quantity.
We’re simply as excited as you might be in regards to the merge, so observe us for extra threads like these. Because of u/EthCatHerders and u/mkalinin2 for the data and the picture this thread was based mostly on: https://youtu.be/zNIrIninMgg
This is one other useful resource: https://eips.ethereum.org/EIPS/eip-3675