The final specification of Ethereum 2.0 is finally released, which is one step closer to its full launch. This release mainly involves the integration of IETF BLS standard into eth2 specification. This article is from trustnodes and translated by blue fox note “jete”.

Danny Ryan, the coordinator of Ethereum 2.0, announced the final release of Ethereum 2.0 specification version 0.1.

Ryan said, “the release focuses on the integration of IETF BLS standards into the specification of eth2. The release of this version also includes in-depth and urgently needed reorganization of the text / directory…”. (blue fox notes: the BLS signature algorithm was proposed by Dan Boneh, Ben Lynn and hovav shacham of Stanford University. The paper can be consulted here:

https://www.iacr.org/archive/asiacrypt2001/22480516.pdf , it can realize signature aggregation and key aggregation, that is to aggregate multiple signatures into one signature and multiple keys into one key. When multiple verifiers want to sign blocks, this signature aggregation algorithm can ensure system security and save storage space.)

He added: “the remaining changes are some small optimizations and cleanups. Most of them are usually backward compatible, and all integration should be very simple. V0.10.1 is marked as the stable goal of phase 0 for multi client test network and security review. We expect some revisions in February / March to wait for the results of each of them.”

What is the final specification for Ethereum 2.0 release

Ben Edgington of Pegasys (one of Ethereum 2.0 clients) clarified that the release of this version is “intended as another frozen release as the basis for test network and audit.”

In addition to the review of beacon chain code, the review of deposit contracts is also under way. Eth2.0 clients wait for the release of this version before planning the launch of any multi client test network.

Although the change in its statement is about the signature standard, the beacon chain design itself also made some changes at the end of last year, and now all the changes have been determined.

It is not clear how many of these changes have been merged by the eth2.0 client. The main thing is to restart the test network of its client specification.

However, this release of the specification is a key step towards full launch. Coders and everyone else are now waiting for the audit report, which may require further changes.

Edgington said: “there are 13000 verifiers waiting in line. New verifiers entered at the maximum speed of four a week at the beginning, so according to my calculation, there is a backlog of two weeks!”

Some of the test networks have been upgraded to the main network configuration, and there are many potential Pledgors. It seems that they have been tested. You may think that they will run in this state for some time while waiting for the audit, and the launch of multi client test network is the key indicator.

Justin Drake, ETH researcher of Ethereum foundation, set an unofficial deadline of July 30 as the release date of Genesis block. This schedule seems to be a reasonable estimate. It actually estimates when to go online, while the multi client test network needs about 3 months of smooth running time.

If the test network is launched in winter and everything goes well, the POS chain may be released in late spring and early summer or at the time point after bitcoin is halved.

Responsible editor: CT

Leave a Reply

Your email address will not be published. Required fields are marked *