524288 ETH! V God personally pledged on the field, is Ethereum 2.0 stable?
In the early hours of November 5th, Vitalik tweeted that the ETH2 pledge contract has been opened. If all goes well, Ethereum 2.0 is expected to start the genesis block at 20:00 Beijing time on December 1st.
The condition for triggering the genesis block is that at least 16,384 validators were born 7 days before December 1, and each validator pledged 32 ETH, that is, there are at least 524,288 ETH in the deposit contract; if the threshold is not reached, then The genesis block is generated 7 days after reaching.
According to the data of the OKLink Ethereum block browser, as of the time of writing, the deposit balance of the contract address has reached 19,685ETH. OKLink has monitored that as of 18:00 today, Vitalik has made a pledge, and its wallet address starts with 0x1db3.
By querying the transfer records of the contract address, OKLink found that there were transfer failures during the process.
Ethereum developer ConsenSys reminded, "Do not send any tokens directly to this contract. Sending ETH directly to this contract address will cause the transaction to fail. This does not mean that you are using Ethereum 2.0. To participate in Ethereum 2.0 network, use the dedicated Launchpad and follow the instructions, or join a service provider."
The ETH2 pledge contract address is:
0x00000000219ab540356cbb839cbe05303d7705fa
secondary title
Participate in staking, what you need to know
image description
(ETH2.0 roadmap, no fixed timetable)
Phase 0 introduces the Beacon Chain as the "command and control" center of the entire Ethereum 2.0 network; Phase 1 introduces shard chains, allowing data to be stored on these shard chains but not on the shard chain Processing transactions; Phase 2 introduces shard virtual machines, allowing transactions to be processed on shard chains.
Since the beacon chain of phase 0 will run the POS protocol Casper, it is regarded as the starting point of Ethereum's new journey into POS.
(1) 32 ETH is the minimum threshold
Phase 0 accepts users to pledge ETH to become a beacon chain validator, and can obtain pledge income. The minimum threshold for user pledge is - 32 ETH. After ETH is transferred to the beacon chain, it will be converted into BETH 1:1, that is, 32 BETHs will become a validator.
If a user has 64 BETHs, they must run two validators, and so on. This is to avoid excessive concentration of verification power and ensure the equality of power and status of each verifier.
In addition, currently only supports switching from ETH1.0 to ETH2.0, and does not support reverse operations. After ETH is transferred to the ETH2.0 deposit contract, it is destroyed to generate BETH, and BETH cannot be reversely restored to ETH.
(2) Responsibilities and Rewards of Verifiers
In phase 0 and phase 1, decentralized delegation cannot be realized, and ETH holders cannot pledge ETH to nodes for mining.
income:
income:
Proof rewards: Validators are rewarded for making proofs that most other validators agree on (LMD-GHOST and Casper FFG votes), and proofs in finalized blocks are worth more. In Phase 1 of ETH2.0, validators will also be rewarded with cross-linking.
Proposer Reward: The proposer who finalizes the block is rewarded. A validator who stays online and does a good job increases their total reward by roughly 1/8 when they propose a block with a new proof.
expenditure:
expenditure:
Computational costs for beacon nodes and validator clients are roughly estimated at $120 per year.
Prover Penalty: Validators are penalized for not proving or proving incomplete blocks.
Inactivity penalty: Inactivity penalty is one of the ways ETH2.0 is designed to avoid the doomsday crisis. If more than 1/3 of validators are eliminated, offline validators will find their balances reduced to such an extent that they cannot participate in validating again.
Serious violations: The ETH2 protocol includes a mechanism called slashing, which is used to punish validators who submit malicious data to the network, with penalties ranging from more than 0.5 ETH to the entire amount of the validator. The protocol also imposes additional penalties based on how many other validators were slashed at the same time, e.g. if a third of validators committed a serious crime at the same time, they would lose their entire balance .
(3) Exit with caution
If the user does not want to participate in the verification, they can also choose to withdraw. Verifiers can also "voluntarily exit" after serving 2048 epochs (equal to 9 days); the pledge of honest verifiers (32 BETH) will be refunded within 27 hours; if the number of beacon chain verifiers is greatly reduced, the highest possible This resulted in a network delay of 8192 epochs (about 36 days).
If a user has voluntarily logged out, or was forced to log out due to slashing, then it will not be possible to rejoin. This means that if you want to become a validator again, you will need to re-stake 32 ETH and a new validator account.
Quote:
