Merge pull request #1129 from multiversx/main

Main into development

Author: andreibancioiu

docs/learn/multiversx-ecosystem.md

@@ -33,7 +33,7 @@ A blockchain is a database of transactions that is continually updated and share
 
 ## **Why would I use MultiversX?**
 
-MultiversX is a collaborative story written by all of us, inviting any builder to discover the digital universes that can be built together no matter that it is in DeFi, Gaming or Payments area. MultiversX nodes are distributed to more than 125 different staking providers, ensuring a robust and secure network. It becomes invaluable for individuals facing uncertainty regarding the security, stability, or mobility of their assets due to external forces beyond their control, and thanks to the ESDT standard and guardians that enhance its security.
+MultiversX is a collaborative story written by all of us, inviting any builder to discover the digital universes that can be built together no matter whether it is in DeFi, Gaming, or Payments area. MultiversX nodes are distributed to more than 125 different staking providers, ensuring a robust and secure network. It becomes invaluable for individuals facing uncertainty regarding the security, stability, or mobility of their assets due to external forces beyond their control, and thanks to the ESDT standard and guardians that enhance its security.
 
 With transaction costs averaging just $0.002, MultiversX allows anyone to send value at very low costs, making it highly accessible and economical. Whether you are an individual or an enterprise, the low transaction fees ensure that transferring value is affordable and efficient. More on that, if you are a company that does not need any tokens or gas to be paid but only the benefits of a decentralized network, MultiversX offers Sovereign Chains. This solution acts as a response to the appchains movement in the industry. Proven to be the fastest, cheapest, and most composable solutions available, providing enterprises and institutions the opportunity to keep all their operations on-chain. Whether they are permissioned or permissionless, those chains are seamlessly connected to the entire ecosystem of blockchains, thanks to the multi-VM feature, opening up endless possibilities for secure, scalable, and interconnected digital operations.
 

docs/validators/staking-v4.md

@@ -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)
 
@@ -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`.
 
@@ -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)
+