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/maxeb/index.md
+17-18Lines changed: 17 additions & 18 deletions
Original file line number
Diff line number
Diff line change
@@ -35,20 +35,19 @@ maxEB = the MAXimum Effective Balance of a validator. Until the Pectra hard fork
35
35
36
36
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
37
38
-
<Detailssummary="What’s a withdrawal credential?">
38
+
### What's a withdrawal credential?
39
39
40
-
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).
40
+
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
41
42
-
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.
42
+
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.
46
+
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
-
</Details>
50
+
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**"
52
51
53
52
|**Allowed**|**Not allowed**|
54
53
| --- | --- |
@@ -59,14 +58,14 @@ A validator opts into the maxEB change by converting from **Type 1** to **Type 2
59
58
60
59
## Risks
61
60
62
-
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:
61
+
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:
63
62
64
-
- The source validator’s pubkey and withdrawal address match the validator they control
65
-
- The target validator’s pubkey is correct and belongs to them
66
-
- The request is a conversion, not a consolidation, if they don’t intend to send funds to another validator
63
+
- The source validator's pubkey and withdrawal address match the validator they control
64
+
- The target validator's pubkey is correct and belongs to them
65
+
- The request is a conversion, not a consolidation, if they don't intend to send funds to another validator
67
66
- The transaction is being signed by the correct withdrawal address
68
67
69
-
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.
68
+
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.
70
69
71
70
# 2. Technical details
72
71
@@ -83,7 +82,7 @@ To consolidate validators, you must have a *target validator* that has a **Type
83
82
84
83
## Requirements for converting to Type 2
85
84
86
-
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.*
85
+
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.*
87
86
88
87
The validator must...
89
88
@@ -94,7 +93,7 @@ The validator must...
94
93
95
94
## Requirements for consolidating
96
95
97
-
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.
96
+
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.
98
97
99
98
In this case, the source validator has all the same requirements as above plus:
100
99
@@ -157,7 +156,7 @@ A minimum of 27.3 hours but consolidations are also subject to a queue. This que
157
156
158
157
### Can I keep my validator index?
159
158
160
-
Yes. In-place conversion keeps the same validator index. If you consolidate multiple validators, you’ll only be able to keep the index of the *target validator*.
159
+
Yes. In-place conversion keeps the same validator index. If you consolidate multiple validators, you'll only be able to keep the index of the *target validator*.
161
160
162
161
### Will I miss attestations?
163
162
@@ -177,7 +176,7 @@ Yes. With **Type 2** credentials, rewards above 32 ETH are automatically restake
177
176
178
177
### Can I still get automatic sweeps after converting?
179
178
180
-
Automatic sweeps will only happen with excess balances over 2048. For all other partial withdrawals, you’ll need to manually trigger them.
179
+
Automatic sweeps will only happen with excess balances over 2048. For all other partial withdrawals, you'll need to manually trigger them.
181
180
182
181
### Can I change my mind and go back from Type 2 to Type 1?
183
182
@@ -189,7 +188,7 @@ Yes. As long as it's active (not exited) and you can sign with its withdrawal ad
189
188
190
189
# Resources
191
190
192
-
-[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
191
+
-[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
193
192
- 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*
194
193
-[pectrified.com](https://pectrified.com/): View the state of consolidations, deposits, and queue waiting times
195
194
-[Ethereal](https://github.com/wealdtech/ethereal): Community-created CLI tool for managing common validator tasks
0 commit comments