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
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -140,57 +140,57 @@ There are several tools available to manage consolidations. The official tool, c
140
140
| 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 |
141
141
| 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 |
142
142
143
-
## FAQ {#FAQ}
143
+
## FAQ {#faq}
144
144
145
-
### Does opting-in change my proposal luck or rewards?
145
+
### Does opting-in change my proposal luck or rewards? {#change-luck-or-rewards}
146
146
147
147
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.
148
148
149
-
### Does opting in change my slashing risk?
149
+
### Does opting in change my slashing risk? {#change-slashing-risk}
150
150
151
151
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.
152
152
153
-
### Do I have to exit my validator to convert?
153
+
### Do I have to exit my validator to convert? {#exit-validator}
154
154
155
155
No. You can convert in place without exiting.
156
156
157
-
### How long will it take to convert / consolidate?
157
+
### How long will it take to convert / consolidate? {#how-long}
158
158
159
159
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.
160
160
161
-
### Can I keep my validator index?
161
+
### Can I keep my validator index? {#keep-validator-index}
162
162
163
163
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*.
164
164
165
-
### Will I miss attestations?
165
+
### Will I miss attestations? {#miss-attestations}
166
166
167
167
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**.
168
168
169
-
### Will I incur penalties?
169
+
### Will I incur penalties? {#incur-penalties}
170
170
171
171
No. As long as your validator is online, you will not incur penalties.
172
172
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}
174
174
175
175
No. But the *source* must authorize the request from its own address.
176
176
177
-
### Will my rewards compound after converting?
177
+
### Will my rewards compound after converting? {#rewards-compound}
178
178
179
179
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.
180
180
181
-
### Can I still get automatic sweeps after converting?
181
+
### Can I still get automatic sweeps after converting? {#automatic-sweep}
182
182
183
183
Automatic sweeps will only happen with excess balances over 2048. For all other partial withdrawals, you'll need to manually trigger them.
184
184
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}
186
186
187
187
No. Converting to **Type 2** is irreversible.
188
188
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}
190
190
191
191
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
192
192
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}
194
194
195
195
Yes. As long as it's active (not exited) and you can sign with its withdrawal address, you can convert it.
0 commit comments