Ethereum 2.0

secondary title

Ethereum 2.0

If you are a Solidity developer planning to deploy ETH2.0 smart contracts, then you will encounter many changes. ETH2.0 will completely replace ETH1.0. Smart contracts written on ETH1.0 may need to be rewritten in ETH2.0, because ETH2.0 contracts will be completely reconstructed. But fortunately, we have about 2 years to prepare and build the ecology.

The first stageAccording to Vitalik, tranquility will be divided into 4 different stages, and it will take about 2 years in total:

The first stagesecond stage,

The third phaseThe third phase

fourth stageThere will be adjustments and optimizations to Ethereum, the new world computer

beacon chain

secondary titlebeacon chain。

The beacon chain is a very core part of the architecture of Ethereum 2.0. It is actually a brand new blockchain.

This chain undertakes two important responsibilities. The first is to serve as the gateway of the pledge system, allowing verifiers to safely participate in the pledge system and become new miners. The other is to store the index of the shard status

Any information stored on the current Ethereum blockchain will not be stored on the beacon chain, including account balances, contracts related to tokens, dApp status, etc. It only stores two things: the validator list and Attestation (proof information).In order to smoothly transition to POS, the siege lions will deploy a registration contract on the existing Ethereum chain, so in the near future we will see Ethereum where POW and POS coexist. (In the second stage, the PoW chain will become a fragment of the beacon chain or a master archive contract—the main storage contract).

If you want to become a miner of Ethereum 2.0, you need to pledge 32 ETH in the registry contract first, and get a receipt (that is, an event (event) that the blockchain client can read), this receipt is "Pass" indicates that the committer (that is, the pledger) is qualified to serve as a verification node. It is worth mentioning that this process is one-way and cannot be withdrawn from this system and returned to the existing PoW chain.

Once 32ETH is submitted to the pledge system, the deposit can only be returned to a specific shard (after the shard is deployed), but not to the EVM.

After registering on the beacon chain, verifiers will be randomly assigned to verify for one or two shards. Validators will combine the data on their shard with the data on the beacon chain to form new blocks.

Unlike Bitcoin or the current Ethereum, under the POS rules, the threshold for becoming a validator node is very low, and the client can be very lightweight, just pledge 32 Ethereum, and sign their attestation, when needed When it is time to send it back to the Ethereum network.The validator client will use the data provided by the beacon chain nodes to construct blocks. If the validator client is malicious or offline, they themselves will bear the consequences - the mortgaged 32 ETH will be confiscated (that is, the rights will be reduced)., but it may not be easy to implement - the network bandwidth required to maintain smooth network communication and frequent hard disk read and write operations will quickly drain the battery of the mobile phone (once offline, the mortgaged 32 Ethereum will also be confiscated) .

Fragmentation

secondary title

Fragmentation

The simplest Sharding method is called Beanstalk, which will run many chains and call a chain a "shard". Each block will have an independent set of validators (Validator), through the voting mechanism to verify transactions and network participants who generate blocks.The sharding scheme can theoretically increase the number of nodes participating in the network to achieve a solution for infinite network expansion, but the solution of the Beacon Chain concept is not very realistic. why? Because the beacon chain needs to do some bookkeeping calculations, it needs to assign verifiers to each shard chain and take snapshots of the shard chain blocks. These calculations are proportional to the number of shards in the system ( That is, the larger the number of shards, the more computational workload). Since the beacon chain itself is also a blockchain, its processing power is limited by the computing power of the nodes running the beacon chain, so the number of shards is naturally limited.However, the structure of the sharded network does result in a multiplier effect of node improvements.

It is currently difficult to measure exactly how much sharding is feasible, but in the foreseeable future, it is unlikely that the throughput needs of blockchain users will exceed what secondary sharding can provide. To safely handle such a large transaction volume, the number of nodes required for a large number of shards will be several orders of magnitude larger than the total number of nodes in all blockchains today.

Summarize

secondary title

Summarize