Skip to content

fix: add missing anchor IDs on maxeb page #15672

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pettinarip merged 1 commit into from
Jun 16, 2025
Merged

fix: add missing anchor IDs on maxeb page #15672

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions public/content/roadmap/pectra/maxeb/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,57 +140,57 @@ There are several tools available to manage consolidations. The official tool, c
| Ethereal | [GitHub](https://github.com/wealdtech/ethereal) | Yes, Apache 2.0 | [Jim McDonald](https://www.attestant.io/team/) | No | Command line | Full feature set for validator and node management |
| Siren | [GitHub](https://github.com/sigp/siren) | Yes, Apache 2.0 | [Sigma Prime](https://sigmaprime.io/) | No | Some command line, but primarily web UI | Only works if you're using the Lighthouse consensus client |

## FAQ {#FAQ}
## FAQ {#faq}

### Does opting-in change my proposal luck or rewards?
### Does opting-in change my proposal luck or rewards? {#change-luck-or-rewards}

No. Opting in does not decrease your change of proposal - your duties and proposal selection remain the same. For example, if you have two 32 ETH validators vs one 64 ETH validator, you will have the same total chances of being selected to propose a block and earn rewards.

### Does opting in change my slashing risk?
### Does opting in change my slashing risk? {#change-slashing-risk}

For smaller or unprofessional operators, the short answer is no. The longer answer is that, for professional operators running many validators per node with fast alerting, consolidating into fewer validators may reduce their ability to react to a slashing and prevent cascade events. The initial slashing *penalty* for all validators has been dramatically reduced from 1 ETH (per 32 ETH) to 0.0078125 ETH (per 32 ETH) to offset this risk.

### Do I have to exit my validator to convert?
### Do I have to exit my validator to convert? {#exit-validator}

No. You can convert in place without exiting.

### How long will it take to convert / consolidate?
### How long will it take to convert / consolidate? {#how-long}

A minimum of 27.3 hours but consolidations are also subject to a queue. This queue is independent of the deposit and withdrawal queues and is not affected by them.

### Can I keep my validator index?
### Can I keep my validator index? {#keep-validator-index}

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*.

### Will I miss attestations?
### Will I miss attestations? {#miss-attestations}

During a consolidation into another validator, the source validator is exited and there is a ~27 hour waiting period before the balance is active on the target validator. This period **does not affect performance metrics**.

### Will I incur penalties?
### Will I incur penalties? {#incur-penalties}

No. As long as your validator is online, you will not incur penalties.

### Do the withdrawal addresses of the validators being consolidated have to match?
### Do the withdrawal addresses of the validators being consolidated have to match? {#withdrawal-addresses-match}

No. But the *source* must authorize the request from its own address.

### Will my rewards compound after converting?
### Will my rewards compound after converting? {#rewards-compound}

Yes. With **Type 2** credentials, rewards above 32 ETH are automatically restaked — but not instantly. Because of a small buffer (called [*hysteresis*](https://eth2book.info/capella/part2/incentives/balances/#hysteresis)), your balance needs to reach **about 1.25 ETH more** before the extra is restaked. So instead of compounding at 33.0 ETH, it happens at 33.25 (effective balance = 33 ETH), then 34.25 (effective balance = 34 ETH), and so on.

### Can I still get automatic sweeps after converting?
### Can I still get automatic sweeps after converting? {#automatic-sweep}

Automatic sweeps will only happen with excess balances over 2048. For all other partial withdrawals, you'll need to manually trigger them.

### Can I change my mind and go back from Type 2 to Type 1?
### Can I change my mind and go back from Type 2 to Type 1? {#go-back-to-type1}

No. Converting to **Type 2** is irreversible.

### If I want to consolidate multiple validators, do I have convert each one to Type 2 first?
### If I want to consolidate multiple validators, do I have convert each one to Type 2 first? {#consolidate-multiple-validators}

Nope! Convert one validator to Type 2 then use that as the target. All other validators consolidated into that Type 2 target can be Type 1 or Type 2

### My validator is offline or below 32 ETH - can I still convert it?
### My validator is offline or below 32 ETH - can I still convert it? {#offline-or-below-32eth}

Yes. As long as it's active (not exited) and you can sign with its withdrawal address, you can convert it.

Expand Down