The merge from Eth1 to Eth2 will come quickly, however with such a large change, there might be many points that pop up. This EIP covers not solely the merge itself, but in addition adjustments made to ensure this as easy as attainable.
What if the PoS chain will get linked onto a minority fork?
This might occur if the block quantity was arduous 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 large number.
Fortunately, we do not have to fret about this because it’s the problem that’s arduous 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 current sensible 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 problem opcode, which might be set to 0.
One other space of concern is randomness. In case your sensible contract relied on block hash for pseudo-randomness, it is much more insecure underneath PoS since block proposers can change the block quantity.
We’re simply as excited as you might be concerning the merge, so comply with us for extra threads like these. Due to u/EthCatHerders and u/mkalinin2 for the information and the picture this thread was primarily based on: https://youtu.be/zNIrIninMgg
Here is one other useful resource: https://eips.ethereum.org/EIPS/eip-3675