Ethereum 2.0 major changes! At the last moment, the shards are reduced from 1024 to 64, and the accelerated shard design is grounded.

Guide: 1. The developer changed the Ethereum 2.0 at the last minute, reducing the number of fragments from 1024 to 64.

2. Completely remove the Shard (sharding) and Crosslink concepts in phase 0.

3, eliminating a lot of complexity, "to promote Ethereum 2.0 can be used earlier, the risk is lower. Puzzle-3223941_1280

Image source:

According to Ethanfang 2.0 coordinator Danny Ryan, Ethereum developers seem to have made some changes to Ethereum 2.0 at the last minute, reducing the shard from 1024 to 64, while designing the “clean state” of phase 0 to the stage. Above.

Ryan recently made some changes to the code "based on the discussion around the alternative Phase 1 proposal" to "completely remove the concept of Shard (sharding) and Crosslink).

He pointed to the proposal of Ethereum co-founder Vitalik Buterin, who called it a “fundamental alternative” that eliminated many of the complexities and “ promoted Ethereum 2.0 to be used earlier with less risk.”

The proposal removed the concept of a “persistent shard chain”. Instead, each tile is directly cross-linked. The proposer proposed that the chain committee approve and complete.

All of this will make the Ethereum 2.0 test network easier to launch because they will remove all sharding and cross-linking mechanisms and incorporate them back into Phase 1.

Buterin said:

"Let's give up the word 'crosslink' because we are not 'linking' to a slice chain, we can use the word 'shard block' directly."

The proposal essentially links "shards" by "a way" in which a slot-N+1 block of any slice knows all slot-N blocks of all slices. So, we Now there is a level 1 single slot cross-sliced ​​communication (via Merkle receipt)…

Beacon block N + 1 has been released, which includes these proofs for all shards. The state transition function of block N + 1 processes these certificates and updates the "latest state" of all slices.

In plain language, according to our understanding, you don't have to send all the content through Beacon through the different shards "the universe" that must "talk" to each other, basically completing all the "conversations".

This makes Beacon itself a bottleneck, but obviously the "receipt" compresses the data, so it is far from the current bottleneck of the node.

The last change of Ethereum 2.0 was because even if you moved ETH between one shard and another, it took a long time for one shard "Universe" to talk to another.

Probably they don't quite understand how to reduce this time requirement, so they made considerable changes in Phase 1 and Phase 2.

On stage 0, they are deleting something that makes it easier to implement, but before Sigma Prime's eth2.0 client, Age Manning of Lighthouse, it sounds like there is still a lot to be done. They said last month:

"We are debugging and experimenting with interoperability between clients. There are many stages to accomplish."

There will be an eth2.0 conference call tomorrow, and there are expected developments and, of course, developments in the Ethereum 2.0 deposit contract.

According to a draft currently under consideration, the deposit contract uses BLS signature, which is a new encryption technology, but has not yet been standardized.

Justin Drake, the developer responsible for encryption technology, and other developers have decided to reach an agreement between different projects that use BLS to reach standards without having to wait for technical committee approval, and Dfinity developers It seems to be working hard. Ben Edgington of PegaSys told Trustnodes:

“I am not a decision maker, but I have already talked with the parties concerned. (1) The new BLS specification has been stable for some time and it is considered unlikely to change further. (2) Soon (weeks) adopt this method The blockchain will agree to freeze its technical specifications. Please note that formal standardization will take longer, but we are not worried about it. (3) A tool for signing deposit data based on new methods will be implemented. The deposit contract will take effect. I hope this is the last step, but this is only speculation. But I don't think it will take longer."

In addition, one of the test network checklists seems to require at least some work on some of its components, because it seems that Phase 0 is unlikely to go live in January next year.

The optimistic estimate may be in March next year, but the simplification of Phase 0 may be of great help. However, there seems to be a lot of changes in Phase 0, and I hope that tomorrow's Ethereum 2.0 conference call will be more clear.