One article to understand the ETH2 pledge process

Eth2 will use Proof of Stake (proof of equity) to maintain network security, but the implementation of PoS requires each active participant ("validator") to have certain assets to pledge. If the assets are held in the eth1 account, then these assets need to be transferred to the verifier of eth2 before they can be pledged.

The role of the verifier is mainly to propose blocks and attest to other blocks, while the pledger (staker) provides funds for pledge. The validator and staker roles can be the same or different entities, and best practices suggest keeping the two separate for maximum security of funds.

The process of transferring funds from eth1 to eth2 and defining stakers and validators is called staking, and the first step is to send a staking deposit transaction on eth1. The detailed information contained in the pledge deposit transaction includes the identity of the pledger, the identity of the verifier, etc., and is collectively referred to as the deposit agreement. This article will explore collateral deposits in detail and explain the process of submitting ETH to eth2 validators on eth1.

Create a deposit agreement

image description

Figure 1: The deposit protocol and its participants

image description

text

Note that since the verifier is authenticated in eth2, the eth2 public key is used instead of the eth1 public key.

pledge amount

image description

Figure 3: Stake Amount

Withdrawal IDs are used to provide accounts from which validators make deposits. Stakers can identify withdrawal accounts by adding a manipulated public key to the protocol:

1. The public key is hashed to compress its size;

image description

Figure 4: Proof of identity for withdrawal

Note that the withdrawal identity certificate also uses the public key of eth2. As such, it must be provided directly by the staker and cannot be recovered from transaction signatures as is usually the case with eth1 smart contracts.

Also note that if the validator and staker are the same entity, different keys should be used for validator identification and withdrawal identification. This way, the withdrawal key can be kept securely offline until the staker is ready to withdraw.

image description

Figure 5: Validator authorization

image description

Figure 6: Submit the deposit agreement

There are two points to note here:

1. The pledger did not explicitly authorize in the deposit agreement, but added his signature to the transaction to provide the required authorization before the transaction broadcast;

2. The transaction must be accompanied by the exact amount of ETH involved in the deposit agreement, any other amount will cause the transaction to be rejected by the deposit agreement.

secondary title

Activate deposit agreement

Unlike the previous steps, the activation contract is mainly carried out in eth2.

Eth2 tracks updates from eth1 for deposit receipts. Every eth2 node includes the latest deposit receipt in its proposed block. As these blocks are finalized, deposits become part of the overall state of eth2. The deposit receipt will be stored in eth2 as validator state.

image description

Figure 7: Activation of deposit protocol

image description

Figure 8: Pledge deposit process

Original link:https://www.attestant.io/

For more Ethereum information, please pay attention to:

Public account: ETH Chinese website

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.

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.