Read on Twitter
I would rather lose in the prediction market than a critical bug reach mainnet.
My participation in this PM is to signal my confidence in @prylabs @sigp_io @ethnimbus @PegaSysEng @ChainSafeth, and @ethereum launching phase 0 in 2020 as planned.
1/n https://twitter.com/josephdelong/status/1282085302127951874
My participation in this PM is to signal my confidence in @prylabs @sigp_io @ethnimbus @PegaSysEng @ChainSafeth, and @ethereum launching phase 0 in 2020 as planned.
1/n https://twitter.com/josephdelong/status/1282085302127951874
If I’m wrong, then it would be for a good reason. I would never push forward on a project that I knew had critical issues.
Phase 0 is already working in multiclient testnets. There is still work to do, but it can be done in parallel.
2/n
Phase 0 is already working in multiclient testnets. There is still work to do, but it can be done in parallel.
2/n
Let’s look at the requirements.
1) A public testnet for 2 to 3 months with 3+ clients.
This is already 3 weeks, 9 more weeks of testing at scale to feel confident! We’re running out of bugs to fix at @prylabs.
3/n
1) A public testnet for 2 to 3 months with 3+ clients.
This is already 3 weeks, 9 more weeks of testing at scale to feel confident! We’re running out of bugs to fix at @prylabs.
3/n
2) Incentivized “attack net” for 2 to 3 months.
As far as I know, there is nothing blocking this. We can get started on it right away.
4/n
As far as I know, there is nothing blocking this. We can get started on it right away.
4/n
3) Bug bounty program for 2 to 3 months.
Again, nothing blocking this other than waiting for initial security audits to be completed in client teams. @prylabs is nearly done resolving their initial audit from @Quantstamp. Other teams are nearly done too.
5/n
Again, nothing blocking this other than waiting for initial security audits to be completed in client teams. @prylabs is nearly done resolving their initial audit from @Quantstamp. Other teams are nearly done too.
5/n
4) Differential fuzzing across clients
This is a vague requirement, but @sigp_io has been putting out great work on differential fuzzing and @prylabs runs fuzzing on its own code to find bugs. This requirement could be considered done already.
6/n
This is a vague requirement, but @sigp_io has been putting out great work on differential fuzzing and @prylabs runs fuzzing on its own code to find bugs. This requirement could be considered done already.
6/n
So there you have it. All of the above requirements can happen in parallel.
ETH2 could get a green light to go in as little as 3 months for a Q4 release target.
With all of this in mind, I am confident ETH2 will launch in 2020 and I’m willing to stake my USDC on it.
7/7
ETH2 could get a green light to go in as little as 3 months for a Q4 release target.
With all of this in mind, I am confident ETH2 will launch in 2020 and I’m willing to stake my USDC on it.
7/7
