Skip to content

Update staking-v4.md #888

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
merged 2 commits into from
Jul 10, 2025
Merged

Update staking-v4.md #888

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
92569af
Update staking-v4.md
katunopolis May 22, 2024
4eba941
Update staking-v4.md
katunopolis May 22, 2024
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
12 changes: 8 additions & 4 deletions docs/validators/staking-v4.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -102,9 +102,11 @@ Staking phase 4 will unfold in three consecutive steps, each corresponding to a

## Staking v4. Step 1.

In the first step, we will completely **remove the staking queue** and place all nodes in an **auction list**. This
process will occur automatically at the end of the epoch and requires no interaction from validators. Nodes'
distribution remains unchanged.
In the first step, we will completely **remove the staking queue** and **unstake all nodes from the staking queue**.
This process will occur automatically at the end of the epoch and requires no interaction from validators.
Nodes' distribution remains unchanged.

For owners which had **unstaked** nodes, these can be **restaked** using 'RestakeUnstakedNodes' complete details [here](https://docs.multiversx.com/validators/delegation-manager/#restaking-nodes)

![Staking V4 Step 1](/validators/stakingV4/stakingV4-step1.png)

Expand All @@ -114,7 +116,7 @@ Starting with this epoch:

- Every **newly staked** node will be placed in the **auction list**.
- Every **unjailed** node will be placed in the **auction list**.
- The **number of new nodes** that can be staked is **uncapped**.
- The global **number of new nodes** that can take part in the system is **uncapped**.
- Owners with **insufficient base staked EGLD** for their nodes will have them **removed** at the end of the epoch in
the following order: `auction` -> `waiting` -> `eligible`.

Expand Down Expand Up @@ -372,3 +374,5 @@ the `TotalNumOfEligibleNodes` for a given epoch is 1600 nodes, this means owners
The specific parameters, including the initial limit and `NodeLimitPercentage`, can be decided through a governance
vote. This ensures community involvement in determining the rules governing node ownership.

The actual limit is 50 nodes per provider with the calculation details from the 'systemSmartContractsConfig.toml' [here](https://github.com/multiversx/mx-chain-mainnet-config/blob/2ca2da07427c5a802202d1ed364a923f0e366f13/systemSmartContractsConfig.toml#L15)