mirror of
https://github.com/sigp/lighthouse.git
synced 2026-03-02 16:21:42 +00:00
Revise consolidation info in Lighthouse book (#7351)
One of the information in the consolidation section in Lighthouse book is wrong. I realise this after reading https://ethereum.org/en/roadmap/pectra/maxeb/ and a further look at [EIP 7251](https://eips.ethereum.org/EIPS/eip-7251) which states: ` Note: the system contract uses the EVM CALLER operation (Solidity: msg.sender) to get the address used in the consolidation request, i.e. the address that calls the system contract must match the 0x01 withdrawal credential recorded in the beacon state. ` So the withdrawal credentials of both source and target validators need not be the same.
This commit is contained in:
@@ -19,11 +19,11 @@ Let's take a look at an example: Initially, validators A and B are both with 0x0
|
||||
- validator A has 64 ETH
|
||||
- validator B has 0 ETH (i.e., validator B has exited the beacon chain)
|
||||
|
||||
The consolidation process can be repeated to consolidate more validators into validator A.
|
||||
The consolidation process can be repeated to consolidate more validators into validator A. The request is made by signing a transaction using the **withdrawal address** of the source validator. The withdrawal credential of the target validator can be different from the source validator.
|
||||
|
||||
It is important to note that there are some conditions required to perform consolidation, a few common ones are:
|
||||
|
||||
- the **withdrawal address** of the source and target validators **must be the same**.
|
||||
- both source and target validator **must be active** (i.e., not exiting or slashed).
|
||||
- the _target validator_ **must** have a withdrawal credential **type 0x02**. The source validator could have a 0x01 or 0x02 withdrawal credential.
|
||||
- the source validator must be active for at least 256 epochs to be able to perform consolidation.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user