I want to make a correction, because previously I said there was an attack vector in the ethereum merge.
What I said was... if the merge happens at a specified block, and since eth2 doesn't validate blocks, it has no way of knowing if the eth1 chain is passing them the true blockchain during the merge... Someone would be able to mine a false block at the merge and eth2 would have no way of knowing if it was correct or not.
Yesterday I learned how this attack is avoided. Instead of the merge happening at a specified block height, it will happen at a specified difficulty level. Since no one can determine when that difficulty level will be reached, no one can pre-pack a false block and re-write the eth1 chain and send it to eth2 at the time of the merge. It's a pretty smart solution.
[link] [comments]
You can get bonuses upto $100 FREE BONUS when you:
π° Install these recommended apps:
π² SocialGood - 100% Crypto Back on Everyday Shopping
π² xPortal - The DeFi For The Next Billion
π² CryptoTab Browser - Lightweight, fast, and ready to mine!
π° Register on these recommended exchanges:
π‘ Binanceπ‘ Bitfinexπ‘ Bitmartπ‘ Bittrexπ‘ Bitget
π‘ CoinExπ‘ Crypto.comπ‘ Gate.ioπ‘ Huobiπ‘ Kucoin.
Comments