From 92569af40f476017fb29f54f84128972144772a6 Mon Sep 17 00:00:00 2001 From: Katunopolis <128485012+katunopolis@users.noreply.github.com> Date: Wed, 22 May 2024 12:45:03 +0200 Subject: [PATCH 1/2] Update staking-v4.md Updated a few sections in accordance with Marius Ciuca --- docs/validators/staking-v4.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/docs/validators/staking-v4.md b/docs/validators/staking-v4.md index 86c133577..2ac37274d 100644 --- a/docs/validators/staking-v4.md +++ b/docs/validators/staking-v4.md @@ -102,9 +102,12 @@ 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) @@ -114,7 +117,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`. @@ -372,3 +375,6 @@ 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 + From 4eba941a1b95222c83c7914cbc3dc785fb14df4e Mon Sep 17 00:00:00 2001 From: Katunopolis <128485012+katunopolis@users.noreply.github.com> Date: Wed, 22 May 2024 12:58:44 +0200 Subject: [PATCH 2/2] Update staking-v4.md Fixed links --- docs/validators/staking-v4.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/docs/validators/staking-v4.md b/docs/validators/staking-v4.md index 2ac37274d..a1760a68b 100644 --- a/docs/validators/staking-v4.md +++ b/docs/validators/staking-v4.md @@ -106,8 +106,7 @@ In the first step, we will completely **remove the staking queue** and **unstake 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 +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) @@ -375,6 +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 +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)