Ethereum 2.0 releases final specification
Editor's Note: This article comes fromBlue Fox Notes (ID: lanhubiji), reprinted by Odaily with authorization.
Editor's Note: This article comes from
Blue Fox Notes (ID: lanhubiji)
Blue Fox Notes (ID: lanhubiji)https://www.iacr.org/archive/asiacrypt2001/22480516.pdf, reprinted by Odaily with authorization.
Foreword: The final specification of Ethereum 2.0 has finally been released, and it is one step closer to its full launch. This release primarily concerns the integration of the IETF BLS standard into the specification for eth2. This article is from trustnodes, translated by Blue Fox Note "JeTe".
Danny Ryan, the coordinator of Ethereum 2.0, announced the final release of version 0.1 of the Ethereum 2.0 specification.
"The release is focused on integrating the IETF BLS standard into the eth2 specification, and this release also includes a deep and much-needed reorganization of the file/directory..." said Ryan. (Blue Fox Note: The BLS signature algorithm was proposed by Dan Boneh, Ben Lynn and Hovav Shacham of Stanford University. The paper can be found here:
, it can implement signature aggregation and key aggregation, that is, multiple signatures are aggregated into one signature, and multiple keys are aggregated into one key. When multiple verifiers want to sign a block, through this signature aggregation algorithm, which can ensure system security and save storage space)
He went on to say: "The rest of the changes are small optimizations and cleanups. Most of these are generally backwards compatible, and all integrations should be pretty straightforward. V0.10.1 is marked as a Phase for multi-client testnets and security reviews Stable target of 0. We expect some revisions in February/March pending the results of each of them."
Ben Edgington of PegaSys (one of the ethereum 2.0 clients) clarified that this release was “intended to be another freeze release, as a basis for testnets and audits.”
In addition to the audit of the Beacon chaincode, the review of the deposit contract is also underway, and the eth2.0 client waits for this release before planning any multi-client testnet launch.
Although its stated changes were about signature standards, the Beacon chain design itself had some changes late last year, and the changes are now all finalized.
It's unclear how many of these changes have been incorporated by the eth2.0 client, and major ones will have to restart their testnets for client specs.
However, this release of the version specification is a critical step towards a full rollout, and coders and everyone else are now awaiting the audit report, which may call for further changes.
