You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: public/content/roadmap/pectra/index.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The current effective balance of the validator is exactly 32 ETH. It's the minim
30
30
31
31
But the benefit of a better reward system for validators is only a part of this improvement. [Stakers](/staking/) running multiple validators can now aggregate them into a single one, which enables easier operation and reduces network overhead. Because every validator in Beacon Chain submits a signature in every epoch, the bandwidth requirements grow with more validators and a large number of signatures to propagate. Aggregating validators will take load off of the network and open new scaling options while keeping the same economic security.
32
32
33
-
Read a deeper dive on maxEB [here](./maxeb/)
33
+
Read a deeper dive on maxEB [here](/roadmap/pectra/maxeb/)
Copy file name to clipboardExpand all lines: public/content/roadmap/pectra/maxeb/index.md
+28-39Lines changed: 28 additions & 39 deletions
Original file line number
Diff line number
Diff line change
@@ -1,51 +1,40 @@
1
-
*tl;dr:* The Pectra hard fork allows Ethereum validators to opt into a higher max effective balance and compounding by converting from **Type 1** to **Type 2** withdrawal credentials. The official tool to do this is the Launchpad. This operation cannot be reversed.
2
-
3
-
# Contents
4
-
5
-
### 1. Overview
1
+
---
2
+
title: Pectra MaxEB
3
+
description: Learn more about MaxEB in the Pectra release
4
+
lang: en
5
+
---
6
6
7
-
- Who is affected?
8
-
- What is "MaxEB"?
9
-
- How does a validator opt in?
10
-
- Risks
7
+
# MaxEB {#maxeb}
11
8
12
-
### 2. Technical details
13
-
14
-
- The flow
15
-
- Requirements for converting to Type 2
16
-
- Requirements for consolidating
17
-
- The consolidation request
18
-
- Partial withdrawals
19
-
20
-
### 3. FAQ
9
+
*tl;dr:* The Pectra hard fork allows Ethereum validators to opt into a higher max effective balance and compounding by converting from **Type 1** to **Type 2** withdrawal credentials. The official tool to do this is the Launchpad. This operation cannot be reversed.
21
10
22
-
#1. Overview
11
+
## Overview {#overview}
23
12
24
-
## Who is affected?
13
+
###Who is affected? {#who-is-affected}
25
14
26
-
Anyone who runs a validator - this is likely someone who knows the index (e.g. [Validator #12345](https://beaconcha.in/validator/12345)) of a validator that they control. If you use a protocol to run a validator (e.g. Lido CSM or Rocket Pool), you will have to check with them to see if and when they support maxEB
15
+
Anyone who runs a validator - this is likely someone who knows the index (e.g. [Validator #12345](https://beaconcha.in/validator/12345)) of a validator that they control. If you use a protocol to run a validator (e.g. Lido CSM or Rocket Pool), you will have to check with them to see if and when they support maxEB.
27
16
28
17
If you stake using a liquid staking token (e.g. rETH or stETH), no action is required or recommended.
29
18
30
-
## What is "maxEB"?
19
+
###What is "maxEB"? {#what-is-maxeb}
31
20
32
21
maxEB = the MAXimum Effective Balance of a validator. Until the Pectra hard fork, every validator earns on a maximum 32 ETH. After Pectra, validators have the option to earn on any balance between 32 and 2048 ETH, in 1 ETH increments by opting in to the change.
33
22
34
-
## How does a validator opt in?
23
+
###How does a validator opt in? {#how-does-a-validator-opt-in}
35
24
36
25
A validator opts into the maxEB change by converting from **Type 1** to **Type 2** withdrawal credentials. This can be done on the [Launchpad](https://launchpad.ethereum.org/) after the Pectra hard fork goes live. As with **Type 0** → **Type 1**, converting from **Type 1** → **Type 2** is an irreversible process.
37
26
38
-
### What's a withdrawal credential?
27
+
### What's a withdrawal credential? {#whats-a-withdrawal-credential}
39
28
40
29
When you run a validator, you have a set of withdrawal credentials. These can be found in your deposit data json or you can view them on your validator's beaconcha.in [deposit tab](https://beaconcha.in/validator/12345#deposits).
41
30
42
31
1.**Type 0** withdrawal credentials: If your validator's withdrawal credentials begin with `0x00...`, you deposited before the Shapella hard fork and do not yet have a withdrawal address set.
2.**Type 1** withdrawal credentials: If your validator's withdrawal credentials begin with `0x01...`, you deposited after the Shapella hard fork or already converted your **Type 0** credentials to **Type 1** credentials.
3.**Type 2** withdrawal credentials: This new withdrawal credential type will begin with `0x02...` and will be enabled after Pectra. Validators with **Type 2** withdrawal credentials are sometimes called "**compounding validators**"
51
40
@@ -56,7 +45,7 @@ When you run a validator, you have a set of withdrawal credentials. These can be
56
45
|| ❌ Type 2 → Type 1 |
57
46
|| ❌ Type 2 → Type 0 |
58
47
59
-
## Risks
48
+
###Risks {#risks}
60
49
61
50
MaxEB enables a validator to send its entire balance to another validator. Users submitting a consolidation request should verify the source and contents of the transaction they're signing. The official tool for taking advantage of maxEB features is the Launchpad. If you do decide to use a third-party tool, you should verify that:
62
51
@@ -67,9 +56,9 @@ MaxEB enables a validator to send its entire balance to another validator. Users
67
56
68
57
We **strongly recommend** discussing any third-party tool you plan to use with the [EthStaker community](https://ethstaker.org/about). It's a helpful place to sanity-check your approach and avoid mistakes. If you use a malicious or misconfigured tool, **your entire validator balance could be sent to a validator you don't control** — with no way to get it back.
69
58
70
-
#2. Technical details
59
+
## Technical details {#technical-details}
71
60
72
-
## The flow
61
+
###The flow {#the-flow}
73
62
74
63
There will be two uses of the `ConsolidationRequest` operation:
75
64
@@ -80,7 +69,7 @@ In a conversion of a **Type 1** to a **Type 2** validator, both the *source* and
80
69
81
70
To consolidate validators, you must have a *target validator* that has a **Type 2** withdrawal credential. This is the destination of any validator balances being consolidated, and the index being preserved.
82
71
83
-
## Requirements for converting to Type 2
72
+
###Requirements for converting to Type 2 {#requirements-for-converting-to-type-2}
84
73
85
74
This will be required for the first validator you convert to **Type 2**. This validator's index is preserved and active. For a conversion, the *source validator* == the *target validator.*
86
75
@@ -91,9 +80,9 @@ The validator must...
91
80
- not be in an exiting state (or slashed)
92
81
- not have pending manually-triggered withdrawals (does not apply to sweeps)
###Requirements for consolidating {#requirements-for-consolidating}
97
86
98
87
This is the *same operation* as converting but is when the *source validator* is different from the *target validator*. The target validator's index is preserved and accepts the balance from the source validator. The source validator's index is put into an `EXITED` state.
The consolidation request will be signed by the withdrawal address associated with the source validator and have:
114
103
@@ -118,11 +107,11 @@ The consolidation request will be signed by the withdrawal address associated wi
118
107
119
108
In a conversion, 2 & 3 will be the same. This operation can be done on [the Launchpad](https://launchpad.ethereum.org/).
120
109
121
-
## Signing requirements
110
+
###Signing requirements {#signing-requirements}
122
111
123
112
To submit a `ConsolidationRequest`, the **withdrawal address of the source validator** must sign the request. This proves control over the validator funds.
124
113
125
-
### What is signed?
114
+
### What is signed? {#what-is-signed}
126
115
127
116
A domain-separated [signing root](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) of the `ConsolidationRequest` object is used.
128
117
@@ -136,11 +125,11 @@ The resulting **BLS signature** is submitted alongside the request.
136
125
137
126
Note: The signing is done by the withdrawal address, not the validator key.
138
127
139
-
## Partial withdrawals
128
+
###Partial withdrawals {#partial-withdrawals}
140
129
141
130
Validators with **Type 1** credentials get automatic, gasless sweeps of their excess balance (anything over 32 ETH) to their withdrawal address. Because **Type 2** allows a validator to compound balances in 1 ETH increments, it will not automatically sweep balances until it reaches 2048 ETH. Balances on **Type 2** validators must be manually triggered and will cost gas.
142
131
143
-
#3. FAQ
132
+
## FAQ {#FAQ}
144
133
145
134
### **Does opting-in change my proposal luck or rewards?**
146
135
@@ -190,7 +179,7 @@ No. Converting to **Type 2** is irreversible.
190
179
191
180
Yes. As long as it's active (not exited) and you can sign with its withdrawal address, you can convert it.
192
181
193
-
# Resources
182
+
##Resources {#resources}
194
183
195
184
-[Electra consensus specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): This is the ‘truest' version that you should rely on. When in doubt, read the specs
196
185
- Not everybody is comfortable wading through code, so [this maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) can help interpret the specs. *Disclaimer: The specs, not the AI, should be relied on as truth, as the AI may misinterpret information or hallucinate answers*
0 commit comments