Skip to content

Commit a55ec91

Browse files
committed
fix: add missing anchor IDs on maxeb page
1 parent 9496bbf commit a55ec91

File tree

1 file changed

+14
-14
lines changed
  • public/content/roadmap/pectra/maxeb

1 file changed

+14
-14
lines changed

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

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -140,57 +140,57 @@ There are several tools available to manage consolidations. The official tool, c
140140
| 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 |
141141
| 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 |
142142

143-
## FAQ {#FAQ}
143+
## FAQ {#faq}
144144

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

147147
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.
148148

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

151151
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.
152152

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

155155
No. You can convert in place without exiting.
156156

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

159159
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.
160160

161-
### Can I keep my validator index?
161+
### Can I keep my validator index? {#keep-validator-index}
162162

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

165-
### Will I miss attestations?
165+
### Will I miss attestations? {#miss-attestations}
166166

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

169-
### Will I incur penalties?
169+
### Will I incur penalties? {#incur-penalties}
170170

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

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

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

177-
### Will my rewards compound after converting?
177+
### Will my rewards compound after converting? {#rewards-compound}
178178

179179
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.
180180

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

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

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

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

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

191191
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
192192

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

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

0 commit comments

Comments
 (0)