Skip to content

Commit 7d22640

Browse files
authored
Smooth pectra update (#476)
* smooth pectra docs
1 parent 1514043 commit 7d22640

File tree

3 files changed

+45
-0
lines changed

3 files changed

+45
-0
lines changed
Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,27 @@
1+
# Consolidations
2+
3+
Since the [Pectra](https://ethereum.org/en/history/#pectra) update on May 7, 2025, validators can stake up to 2048 ETH. Instead of having to manage multiple 32 ETH validators, users can now choose to stake an arbitrary amount of ETH in a single validator.
4+
5+
To make a validator able to stake more than 32 ETH, users will have to **Upgrade the validator's withdrawal credentials**: From 0x01 to 0x02.
6+
7+
It is also possible to **Consolidate** multiple 32 ETH validators into a single validator with a higher stake. This requires an extra step: a **consolidation**. In a consolidation, two validators are merged into a single one. The _"source"_ validator will exit the chain, transferring its stake to the _"target"_ validator.
8+
9+
Both these steps can be done through the [Staking Launchpad](https://launchpad.ethereum.org/en/) interface.
10+
11+
## How Smooth manages consolidations
12+
13+
Since the _source_ validator will exit the chain, it will not be able to propose blocks anymore and therefore convert its Smooth's _pending rewards_ into _accumulated rewards_. Effectively losing them.
14+
15+
To avoid this, Smooth will automatically detect when a validator is the source of a consolidation. Upon doing so, it will transfer all the _pending rewards_ from the source validator to the target validator. This way, no pending rewards will be lost during the consolidation process. Smooth will also remove the source validator from the pool.
16+
17+
## As a Smooth user, what do I need to do?
18+
19+
Consolidation is not required—Smooth will continue to work normally even if you don’t consolidate your validators.
20+
21+
However, if you want to consolidate any of your validators, we recommend upgrading your validator’s withdrawal credentials to 0x02 and performing the consolidation through the [Staking Launchpad](https://launchpad.ethereum.org/en/) interface. You will not need to do anything else; Smooth will take care of the rest.
22+
23+
:::danger
24+
DO NOT manually unsubscribe any validator before consolidating it. Manually unsubscribing a validator will remove its pending rewards and Smooth will not be able to transfer them to the target validator.
25+
:::
26+
27+
A consolidation may take a few days to complete. Once your source validator exits the chain, Smooth will transfer the pending rewards to the target validator. We recommend checking [Smooth's dashboard](https://smooth.dappnode.io/dashboard) to see if the transfer was successful.

docs/smooth/deep-dive-into-smooth/rewards.md

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,19 @@ There are 2 main sources of rewards in Smooth:
1515

1616
When a validator has an active subscription to the pool (`Active` or `YellowCard` state) it is eligible for rewards, meaning that it will receive a given share of each reward that is sent to the pool. Validators in `RedCard` are considered subscribed, but don't earn rewards until they become active again.
1717

18+
<div align="center"><strong>
19+
Validator Share = (Validator Effective Balance / Total Effective Balance) × Rewards to Distribute
20+
</strong></div>
21+
22+
Where:
23+
- **Validator Effective Balance**: The staked amount of ETH of the validator.
24+
- **Total Effective Balance**: The sum of all the effective balances of eligible validators in the pool (in `Active` or `YellowCard` state).
25+
- **Rewards to Distribute**: The amount of rewards that entered the pool. Normally, these come from block proposals or donations.
26+
27+
:::info
28+
Since the Pectra Fork on May 7, 2025 (10:05:11 UTC), validators can stake up to 2,048 ETH. The more ETH a validator stakes, the more frequently they are expected to be selected to propose blocks. In Smooth, this directly affects how rewards are distributed: for example, a validator staking 64 ETH will earn twice as much as one staking 32 ETH. This applies to all types of rewards, including donations.
29+
:::
30+
1831
Smooth's distributes rewards to the validators as `Pending Rewards`. These are rewards that are not _consolidated_ yet, meaning that they belong to the validator but they can not be claimed yet, until a valid block proposal is sent to [Smooth](https://smooth.dappnode.io/) by that validator.
1932

2033
Later on, when a validator sends a valid block proposal to [Smooth](https://smooth.dappnode.io/), all its `Pending Rewards` are transformed into `Accumulated Rewards`. These rewards are consolidated and can be claimed by the validator.

sidebars.js

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -657,6 +657,11 @@ const sidebars = {
657657
label: "Avoid proposing Vanilla Blocks",
658658
id: "smooth/deep-dive-into-smooth/vanilla-blocks",
659659
},
660+
{
661+
type: "doc",
662+
label: "Validator Consolidations In Smooth",
663+
id: "smooth/deep-dive-into-smooth/consolidations",
664+
},
660665
],
661666
},
662667
{

0 commit comments

Comments
 (0)