An article to understand the current stage of development of ETH2: stage 0
source|Quantstamp Labs
source|
We are now in Phase 0 where the Beacon Chain, the heart of the Proof of Stake (PoS) system in ETH 2.0, will be tested and launched. This post will explain the role of the beacon chain and the work we are doing now for its official launch.
first level title
What is the goal of the beacon chain?
One of the goals of ETH 2.0 is to expand transaction throughput by sharing the work of processing and storing transactions through sharding. Sharding is a valuable attempt, because currently in ETH 1.0, each full node needs to verify transactions on the entire Ethereum network and store the entire Ethereum state, which means that each full node is managing all Economic activity.
In ETH 2.0, sharding mitigates these limitations by coordinating and finalizing data on the beacon chain. The beacon chain serves as the source of truthful information.
secondary title
The beacon chain uses PoS to reach consensus and finalize data on shards
The beacon chain will use PoS to validate data on shards. In proof-of-work (PoW) blockchains, miners are incentivized if they perform well, and if they choose to attack the network by forking while mining, they will not receive block rewards and transaction fees to fill the electricity and sunk costs of mining equipment, etc.
In order to be eligible to validate ETH 2.0 and earn benefits from it, potential validators first need to submit (i.e. pledge) at least 32 ETH to the system. If a validator attempts to submit incorrect data to the network, or if they are offline for too long, some or all of their previously submitted ETH will be deducted.
secondary title
Development Status of Phase 0Starting the Beacon Chain is a delicate undertaking. To ensure a smooth process, the developers are following theThese beacon chain specifications
Test the client implementation.
Clients are at the heart of a decentralized system because they solve the problem of a central point of failure. In ETH 1.0, the full node eliminates central point failures in the following three ways:
Save the entire state of Ethereum (i.e. all economic activity, balances, etc.)
Share the latest blockchain information with peers (other clients), such as newly mined blocks and transactions waiting to be validated, and
After receiving the information, verify it first and then share it with other clients to implement network rulesPrysmatic LabsAt this stage, the development of ETH 2.0 is mainly carried out by multiple independent teams to develop and test the client. Prysm is adevelopment andAudited by QuanstampETH 2.0 client. This client is currently runningFor testing, anyone can download the client and simulate running ETH 2.0's beacon chain.
Click hereLearn how to run the Prysm client on the Topaze ETH 2.0 testnet!
List the most recent phase 0 milestone events by time
first level title
Multiple implementations can guarantee the security of ETH 2.0
Thriving on ETH 2.0 requires multiple clients to be active at beacon chain launch. If we relied on a single client, a single bug in that client could have devastating effects on the network, including putting the entire network in a non-consensus state or preventing blocks from being finalized.
When there are multiple client implementations on the network, the possibility of a bug in a single client having a devastating impact on the network is greatly reduced. If a bug occurs in one client, that client will not be able to participate in consensus, but the entire network will continue to operate and finalize transactions, because other clients are unlikely to have the same bug. In other words, other clients maintain consensus. Therefore, the coexistence of multiple clients can improve network security.
The purpose of creating the test network is to simulate the real situation of putting the beacon chain on the main network. To test for bugs when multiple clients share information (blocks, transactions, etc.), the ETH 2.0 client implementation is actively communicating on the multi-client testnet.
Schlesi, the first multi-client testnet, was launched on April 27th of this year. At one point there were 4 synced client implementations running the testnet beacon chain in them, they were:
Prysm by Prysmatic Labs
Teku by PegaSys, funded by ConsenSys
Lighthouse for Sigma Prime, and
Nimbus by StatusOn May 17, a consensus bug appeared in a certain client, which caused a fork on the Schlesi multi-client testnet. After finding the bug, the client's developers decided to close the Schlesi testnet and start over. It’s worth noting that finding bugs on the testnet is a normal part of the development process. In the test network before the official release of ETH 1.0, many such bugs were also found.
sourcesource：beaconcha.in
first level title
The launch and follow-up of the beacon chain
Once the Ethereum community reaches a certain level of social consensus on the stability of the testnet, the Deposit Contract will be released on ETH 1.0.deposit contractdeposit contract
The usefulness of is to collect the pledge of future ETH2.0 verifiers so that they are eligible to perform verification work on the beacon chain. When the pledged ETH reaches the predetermined amount, the beacon chain will be activated, and then a new block will be generated on the chain.
The launch of the beacon chain will mark the end of Phase 0. After that, ETH 1.0 and 2.0 will exist in parallel for a while. ETH 1.0 will eventually transition to a shard on the ETH 2.0 system.TwitterFollow us on and visit ourblogFor more Ethereum information, please pay attention to:
For more Ethereum information, please pay attention to:
Public account: ETH Chinese website
Website: ethereum.cn
Disclaimer: ECN's translation work aims to deliver high-quality information and learning resources for the Chinese Ethereum community. The copyright of the article belongs to the original author. Reprints must indicate the source of the original text and ethereum.cn. For long-term reprints, please contact ethereumcn@gmail.com Authorize.
