In the past three weeks, the information on the progress of Eth2.0 has been extremely calm. But this is for a major reason: everyone is completely focused on interoperability between Eth2.0 clients in a "confinement" party.
Interoperability "confinement"
Last week, in addition to an Eth 2.0 client development team (the Shasper client team), all seven other client teams gathered in a remote lakeside lodge in Ontario, Canada, with the goal of giving each team a beacon. Chain nodes communicate with each other . Join our Ethereum Foundation staff, Whiteblock staff and the Eth 2.0 Phase 2 team (including the ConsenSys Quilt team and the Ewasm team at the Ethereum Foundation). I won't retell the whole story here. Danny Ryan published a related article on the Foundation blog [1], and I will write an article later, so stay tuned. I just want to say that the success of this gathering was something we didn't expect beforehand.
- Understanding the role of different roles in cryptocurrency exchanges
- A paper on how cryptocurrency reforms the traditional derivatives exchange clearing mechanism
- Blockchain startup Upvest secures $ 7.8 million in Series A funding, targeting "10 trillion euros" alternative investment asset class
- Vitalik: Ethereum 1.0 will become the subsystem of Ethereum 2.0, PoW will lose its meaning
- Industry Watch | Where is the future of blockchain, the opportunities and challenges of the US Securities Regulatory Commission's STO opening
- Telegram blockchain network will be compatible with Ethereum
Some related tweets :
• #Eth2Interop is ?[2]
- Agenda of the meeting [19];
- Conference video [20];
- I made meeting notes [21] and Pooja Ranjan's notes [22];
The call was not long and lasted only 45 minutes. I think it's because everyone is tired after the interoperability "confinement" party, and I want to take a breather before the start of the DevCon meeting.
It is worth noting that the Ethereum 2.0 specification version 0.8.4 will be released in the next few days . This will include updates to the networking specification, as well as some special test vectors [23] covering a few unrealized experiences experienced by teams during this interoperability gathering. The core content of the Ethereum 2.0 specification will remain frozen and it is not expected to update the core content .
Constant time is not what we really need in Eth 2.0 – all hash input is public. However , we need to use the new BLS signature algorithm to comply with the new hash-to-curve standard [26].
For reference, I implemented the new hash-to-curve standard for Eth 2.0 in Java, which passed all test vectors [27]. Kirk Baird is also using the Python language to achieve it [28]. Compared to our current Java version [28], my implementation is about 50 times more lines of code?
An important impact of all these pending work is that the time to deploy a certifier's Deposit Contract [29] on the current Ethereum 1.0 chain will likely be delayed .
Initially, we plan to deploy the mortgage contract during the DevCon conference in Osaka, Japan in October, but it seems unlikely that this will happen .
The problem is that part of the verifier registration process involves generating a BLS signature: we cannot ensure that the registration process does not change until the BLS signature scheme is standardized. But we should be able to complete the preparations in the next few weeks, so this should not delay the plan to start the beacon chain in the first quarter of next year .
- In addition to interoperability, the Lighthouse and Prysm clients have been updated. [34] & [35]
- Member of the Lighthouse client team Mehdi's presentation during the EthBerlin conference PPT: Performance and Security of Ethereum 2.0 [36]
- David Hoffman shared the questions and answers of Vitalik during the Ethreal Summit [37], some of which are great about Eth2.0.
- Colin Schwartz's article on Medium: Ethereum 2.0: A Complete Guide. Ewasm [38]
- Julin Chiu's explanatory article on Casper FFC: " Casper FFG: Consensus Protocol for the Realization of Proof-of-Stake " [39]
