Skip to content

Commit 4823aa5

Browse files
committed
markdown doesn't work in details component i guess
1 parent 31fe87a commit 4823aa5

File tree

1 file changed

+17
-18
lines changed
  • public/content/roadmap/pectra/maxeb

1 file changed

+17
-18
lines changed

public/content/roadmap/pectra/maxeb/index.md

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -35,20 +35,19 @@ maxEB = the MAXimum Effective Balance of a validator. Until the Pectra hard fork
3535

3636
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.
3737

38-
<Details summary="Whats a withdrawal credential?">
38+
### What's a withdrawal credential?
3939

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 validators 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).
4141

42-
1. **Type 0** withdrawal credentials: If your validators 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.
4343

44-
![Type 0 withdrawal credential](/images/maxeb/0x00-wd.png)
44+
![Type 0 withdrawal credential](/images/maxeb/0x00-wd.png)
4545

46-
2. **Type 1** withdrawal credentials: If your validators 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.
4747

48-
![Type 1 withdrawal credential](/images/maxeb/0x01-wd.png)
48+
![Type 1 withdrawal credential](/images/maxeb/0x01-wd.png)
4949

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**"
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**"
5251

5352
| **Allowed** | **Not allowed** |
5453
| --- | --- |
@@ -59,14 +58,14 @@ A validator opts into the maxEB change by converting from **Type 1** to **Type 2
5958

6059
## Risks
6160

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 theyre 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:
6362

64-
- The source validators pubkey and withdrawal address match the validator they control
65-
- The target validators pubkey is correct and belongs to them
66-
- The request is a conversion, not a consolidation, if they dont 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
6766
- The transaction is being signed by the correct withdrawal address
6867

69-
We **strongly recommend** discussing any third-party tool you plan to use with the [EthStaker community](https://ethstaker.org/about). Its 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 dont 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.
7069

7170
# 2. Technical details
7271

@@ -83,7 +82,7 @@ To consolidate validators, you must have a *target validator* that has a **Type
8382

8483
## Requirements for converting to Type 2
8584

86-
This will be required for the first validator you convert to **Type 2**. This validators 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.*
8786

8887
The validator must...
8988

@@ -94,7 +93,7 @@ The validator must...
9493

9594
## Requirements for consolidating
9695

97-
This is the *same operation* as converting but is when the *source validator* is different from the *target validator*. The target validators index is preserved and accepts the balance from the source validator. The source validators 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.
9897

9998
In this case, the source validator has all the same requirements as above plus:
10099

@@ -157,7 +156,7 @@ A minimum of 27.3 hours but consolidations are also subject to a queue. This que
157156

158157
### Can I keep my validator index?
159158

160-
Yes. In-place conversion keeps the same validator index. If you consolidate multiple validators, youll 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*.
161160

162161
### Will I miss attestations?
163162

@@ -177,7 +176,7 @@ Yes. With **Type 2** credentials, rewards above 32 ETH are automatically restake
177176

178177
### Can I still get automatic sweeps after converting?
179178

180-
Automatic sweeps will only happen with excess balances over 2048. For all other partial withdrawals, youll 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.
181180

182181
### Can I change my mind and go back from Type 2 to Type 1?
183182

@@ -189,7 +188,7 @@ Yes. As long as it's active (not exited) and you can sign with its withdrawal ad
189188

190189
# Resources
191190

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
193192
- 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*
194193
- [pectrified.com](https://pectrified.com/): View the state of consolidations, deposits, and queue waiting times
195194
- [Ethereal](https://github.com/wealdtech/ethereal): Community-created CLI tool for managing common validator tasks

0 commit comments

Comments
 (0)