| The ETH2 'beacon chain' is a meta-chain that's supposed to checkpoint a bunch of 'sub chains' for scalability. But they have launched it with many big questions unanswered. What does a 'sub chain' actually look like to interact with? How do you coordinate with many of them? All these questions have answers in theory, but not answers in solid production ready interoperable code. Furthermore some of these problems like 'how do you store a bunch of sub-chains' are questions not even properly answered in ETH1 nodes for the much simpler one chain case. By launching the beacon chain early the organizations developing ETH2 can validate and make money while all these questions are figured out. This is where the money goes instead of the improvement of ETH1 since that's a tragedy of the commons as this point. ETH2 is only worth money if these questions are figured out and ETH1 is somehow brought under the beacon chain's governance. Exactly how this is to happen... well I haven't even seen anything credible on this. Greenfield addition of chains under the ETH2 beacon chain is generously described as 'incomplete' moving ETH1 under ETH2 is much more challenging and I have not seen a plan with any level of detail. Given that everyone is making bridges to ETH1 now and typical development timelines. I would give a medium to high chance that ETH2 will miss it's window by a couple of years and activity will move to other faster chains that are available now and capable of siphoning off traffic from Ethereum using bridges until they reach their own critical mass. If I had to put money on it I would place 'proof of stake Ethereum' (defined as ETH1 under the POS beacon chain) more than 2 years out. I could see the sub-chains (greenfield) working by EOY, although I wouldn't grant it a high probability. Also if I had to put money on it I will bet on a halt of the Ethereum 1 chain for a time greater than 24 hours within that period, due to lack of maintenance on ETH1 nodes and increased stress from DeFi activity. ----- ETH2 is kinda like 5G, yes there is a very real 5G network protocol, but in terms of pubic messaging, everything is 5G and communicating anything about how it works or when it will be available is filled with pitfalls and nuances that are difficult for the highly technical, much less the general public, to understand. |
That could create a lot of momentum/adoption for ETH2, very quickly. And it wouldn’t take much: all these substrate projects are intentionally architected so that you can just develop for them as if you were developing for an ETH1 side-chain, and defer all the operational questions to network launch time. They’ve intentionally commoditized themselves!
So, as long as ETH2 is the best choice for a substrate when these projects go to mainnet, it’s what they’ll pick. And, for many reasons (that all mostly come down to “lifetime cost of bridging to either ETH1 and/or chain-foo-where-DEX-foo-lives”), ETH2 may be the best choice.
(Imagine if you developed your project against some Postgres-ish-DB-aaS cloud provider like Greenplum Cloud, but only used regular Postgres features; and then, when you went to production, you looked around and decided that Amazon RDS was good enough—and on top of that, required no re-engineering, since you weren’t doing anything fancy.)