Merge pull request #738 from lidofinance/v3-docs-health

V3 docs health

Author: TheDZhon

run-on-lido/stvaults/building-guides/basic-stvault.md

@@ -9,15 +9,15 @@ import TabItem from '@theme/TabItem';
 
 ## Intro
 
-This guide is aimed to help Node Operators, Builders, Protocols, Liquidity Providers create and operate an stVault with optional liquidity.
+This guide is aimed at helping Node Operators, Builders, Protocols, and Liquidity Providers create and operate an stVault with optional liquidity.
 
 ### Product value proposition
 
 Competitive offering to native staking — users stake with the same Node Operator and get optional liquidity through stETH.
 
 ### The vault strategy
 
-ETH is deposited to validators and generate staking rewards, stETH is minted on demand by the Vault Owner.
+ETH is deposited to validators and generates staking rewards; stETH is minted on demand by the Vault Owner.
 
 ## Environments
 
@@ -30,11 +30,10 @@ ETH is deposited to validators and generate staking rewards, stETH is minted on
 
 ### Mainnet
 
-:::info
-
-      *Coming this autumn*
-
-::::
+- UI: https://stvaults.lido.fi/ (will be available on [Phase 2 of the Rollout plan](https://research.lido.fi/t/lido-v3-design-implementation-proposal/10665/8))
+- CLI: https://lidofinance.github.io/lido-staking-vault-cli/get-started/configuration
+- Contracts: https://docs.lido.fi/deployed-contracts/
+- Etherscan: https://etherscan.io/
 
 ## Steps
 
@@ -51,15 +50,15 @@ Creating an stVault is permissionless. There are two main ways to do it:
 2. **Node Operator Manager address**. One of the two administrative roles in an stVault. From the Node Operator perspective, this role manages permissions and can update key vault parameters. Multiple addresses are supported.
 3. **Vault Owner address**. One of the two administrative roles in an stVault. From the Vault Owner (Staker) perspective, this role manages permissions and can update key vault parameters. Multiple addresses are supported.
 4. **Node Operator Fee**. The share of gross staking rewards that the Node Operator charges for providing validation services. Expressed in basis points [0 (0%) .. 10'000 (100%)].
-5. **Confirmation Lifetime**. The key parameter of the multi-role confirmation mechanism. It defines the maximum time interval between proposal and confirmation. This mechanism is used to update certain stVault parameters by requiring consensus between the two stVault representatives: the Vault Owner and the Node Operator Manager. Measured in seconds [86'400 sec (24 hours) .. 25'920'000 sec (30 days)]. For security reasons, it is strongly recommended to keep it as sort as possible, ideally the minimal 86'400 sec.
+5. **Confirmation Lifetime**. The key parameter of the multi-role confirmation mechanism. It defines the maximum time interval between proposal and confirmation. This mechanism is used to update certain stVault parameters by requiring consensus between the two stVault representatives: the Vault Owner and the Node Operator Manager. Measured in seconds [86,400 sec (24 hours) .. 25,920,000 sec (30 days)]. For security reasons, it is strongly recommended to keep it as short as possible, ideally the minimum 86,400 sec.
 
 #### 1. Two-step process (recommended)
 
 This approach enables a Node Operator to create an stVault without providing their own ETH. It is recommended because it prevents ETH commingling and streamlines the experience for Stakers and Vault Owners.
 
 ##### 1.1. **Node Operator** creates an stVault that is not yet connected to Lido Core.
 
-Creating stVault is a permissionless operation, but in this 2-steps process it is usually performed by the Node Operator.
+Creating an stVault is a permissionless operation, but in this two-step process it is usually performed by the Node Operator.
 
 <details>
   <summary>by Command-line Interface</summary>
@@ -125,14 +124,20 @@ This is a permissioned operation. By default, this permission belongs to the Vau
 - `currentSettledGrowth` the amount of unaccounted growth accrued on the vault while it was disconnected. 0 for newly created vaults via create without connecting method. Settled growth is the part of the total growth that has already been charged by the node operator or is not subject to fee (exempted), such as unguaranteed or side deposits, and consolidations accrued while the vault was disconnected.
 
 
-
 <details>
   <summary>using stVaults Web UI</summary>
+      1. Open the stVaults mainpage (see [#Environments](#environments))
+
+      2. Connect wallet on the "My Vaults" page.
 
-      *Will be supported later this Autumn*
+      3. Open an stVault overview page by the URL ```https://<domain>/vaults/<StakingVault_address>```
+      
+      ![Connect and accept tier](/img/stvaults/guide-basic-stvault/guide_1_scr_8.png)
 
-</details>
+      4. Review parameters and click "Approve and supply 1 ETH".
 
+      5. Sign transaction in the wallet.
+</details>
 <details>
   <summary>by Command-line Interface</summary>
       ```bash
@@ -159,13 +164,16 @@ This is a permissioned operation. By default, this permission belongs to the Vau
 
 #### 2. One-step process (for experienced Vault Owners / Stakers)
 
-In this approach, the Vault Owner creates an stVault that automatically connects to Lido Core, enabling stETH minting. This requires supplying 1 ETH, which will be locked as collateral for the connection to Lido Core. All completed in a single transaction, so despite it is a permissionless operation, it is usually performed by the Vault Owner of the future stVault.
+In this approach, the Vault Owner creates an stVault that automatically connects to Lido Core, enabling stETH minting. This requires supplying 1 ETH, which will be locked as collateral for the connection to Lido Core. All completed in a single transaction, so despite being a permissionless operation, it is usually performed by the Vault Owner of the future stVault.
 
 <details>
   <summary>using stVaults Web UI</summary>
       1. Open the stVaults mainpage (see [#Environments](#environments))
       2. Connect wallet on the "My Vaults" page.
       3. Click "Create vault".
+
+      ![Create vault](/img/stvaults/guide-basic-stvault/guide_1_scr_9.png)
+
       4. Fill out the form and click "Continue".
       5. Sign transaction in the wallet.
 </details>
@@ -198,10 +206,10 @@ Tier changes are performed via a multi-role confirmation mechanism, where the No
 
 Both parties must submit the request with identical parameters within the confirmation lifetime of 24 hours for the change to take effect.
 
-Addresses perform this operation must have the following roles ([Read more about roles](../roles-and-permissions)):
+Addresses performing this operation must have the following roles ([Read more about roles](../roles-and-permissions)):
 
-- From the Vault Owner: Vault Owner (Admin DEFAULT_ADMIN_ROLE, or delegated VAULT_CONFIGURATION_ROLE].
-- From the Node Operator: Node Operator (registered in the`OperatorGrid` contract).
+- From the Vault Owner: Vault Owner (Admin DEFAULT_ADMIN_ROLE, or delegated VAULT_CONFIGURATION_ROLE).
+- From the Node Operator: Node Operator (registered in the `OperatorGrid` contract).
 
 :::info
 Confirming tier change request requires applying fresh report to vault.
@@ -256,7 +264,7 @@ Confirming tier change request requires applying fresh report to vault.
 <details>
   <summary>using Etherscan UI</summary>
 
-      The Node Operator and Vault Owner use same-named metods in different contracts to perform this change.
+      The Node Operator and Vault Owner use same-named methods in different contracts to perform this change.
 
       **Node Operator:**
       1. Open **Etherscan** and navigate to the **Operator Grid** contract by its address (available in the stVaults contract addresses list, see [#Environments](#environments)).
@@ -410,6 +418,13 @@ Supplying ETH to the stVault increases its balance. The Node Operator can then d
 
 **The Predeposit Guarantee (PDG)** contract, as part of the stVaults platform, helps prevent deposit frontrunning caused by the vulnerabilities described in [LIP-5](https://research.lido.fi/t/lip-5-mitigations-for-deposit-front-running-vulnerability/1269). PDG secures the Vault Owner’s ETH deposits to validators from being front-run by the Node Operator.
 
+:::warning
+According to the [updated V3 rollout plan](https://research.lido.fi/t/lido-v3-design-implementation-proposal/10665/8), the Predeposit Guarantee (PDG) contract is now paused on the Hoodi Testnet and will also be paused on Mainnet during the soft-launch in late December 2025.
+
+Phase 2 (Full Launch Mode), including the fully functional PDG, is expected in late January 2026.
+:::
+
+
 One of the key benefits of using PDG is the avoidance of commingling: it keeps the finances of the Vault Owner and the Node Operator strictly separated.
 
 PDG enables three main use cases:
@@ -444,13 +459,13 @@ The amount of ETH required for rebalancing to bring the Utilization Ratio to 100
 <details>
   <summary>by Formula</summary>
 
-      ETH for rebalance = stETH Liability - (1 - Reserve Ratio * Total Value ) / Reserve Ratio
+      ETH for rebalance = (stETH Liability − (1 − Reserve Ratio) × Total Value) / Reserve Ratio
 
 </details>
 <details>
   <summary>by Command-line Interface</summary>
 
-      *Will be supported later on testnet-3*
+      See the [CLI documentation](https://lidofinance.github.io/lido-staking-vault-cli/) for rebalance commands.
 
 </details>
 <details>
@@ -470,5 +485,7 @@ The amount of ETH required for rebalancing to bring the Utilization Ratio to 100
 
 ## Useful links
 
+- [Health Monitoring Guide](../health-monitoring-guide.md)
+- [Health Emergency Guide](../health-emergency-guide.md)
 - [stVaults Roles](../roles-and-permissions)
 - [stVaults Metrics](../parameters-and-metrics)

run-on-lido/stvaults/consolidation.md

@@ -17,10 +17,10 @@ Use [these instructions](https://lidofinance.github.io/lido-staking-vault-cli/)
 - Set `NODE_OPERATOR_REWARDS_ADJUST_ROLE` to the address of your original validator's withdrawal credentials:
   - CLI
     - `yarn start dashboard -w role-grant [{"account": <withdrawal_credentials>, "role": <node_operator_role_in_hex>}]`
-  - StVault UI
-    - go to `https://stvaults-hoodi.testnet.fi/vaults/<vault_address>/settings/permissions`. **TODO: update links to mainnet.**
-    - navigate to "Node Operator Manager Permissions" section, "Adjust rewards on the validators" item.
-    - add the address of your original validator's withdrawal credentials.
+  - stVault UI
+    - Go to `https://stvaults.lido.fi/vaults/<vault_address>/settings/permissions`.
+    - Navigate to the "Node Operator Manager Permissions" section, "Adjust rewards on the validators" item.
+    - Add the address of your original validator's withdrawal credentials.
 - Source validators
   - withdrawal credentials must be `0x01` or `0x02` (`0x00` is not supported).
   - must be active (i.e., not exiting or slashed).
@@ -29,13 +29,13 @@ Use [these instructions](https://lidofinance.github.io/lido-staking-vault-cli/)
   - must have a withdrawal credentials of type `0x02` equal to stVault's `withdrawalCredentials()` function result.
   - must be active (i.e., not exiting or slashed).
 
-> **Note:** You can check a validator’s credentials or state at [Beaconcha](https://beaconcha.in/validator/<pubkey>).
+> **Note:** You can check a validator's credentials or state at [beaconcha.in](https://beaconcha.in/validator/<pubkey>).
 
 ## 3. Prepare input data
 
 - A list of source pubkeys of validators that you want to consolidate from.
 - A list of target pubkeys of validators that you want to consolidate to.
-- Dashboard contract's address used to control the stVault [can be discovered via CLI](https://lidofinance.github.io/lido-staking-vault-cli/get-started/additional-helpers#find-dashboard-by-vault).
+- The Dashboard contract address used to control the stVault [can be discovered via CLI](https://lidofinance.github.io/lido-staking-vault-cli/get-started/additional-helpers#find-dashboard-by-vault).
 - To cover the consolidation fee costs, you'll need some amount of ETH. The exact amount depends on the number of public keys and the current state of the blockchain. You can determine the fee for a single consolidation request by calling the view function `getConsolidationRequestFee` on the `ValidatorConsolidationRequests` contract. The total amount required will be calculated as the number of consolidations multiplied by the fee per request.
 
 ## 4. Run consolidation command
@@ -66,7 +66,6 @@ yarn start consolidation w <dashboard> --file <path-to-json-with-pubkeys> --wall
 - If your wallet does not support `EIP-5792`, the consolidation request will be executed using the `eth_sendTransaction` method, processing the transaction calls one by one instead of in a batch.
 
 > **Note:** Alternatively, you can list pubkeys directly in the command as parameters:
-> If you prefer it's possible to list pubkeys in command as parameters:
 
 ```bash
 yarn start consolidation w <dashboard> \
@@ -81,11 +80,11 @@ yarn start consolidation w <dashboard> \
 
 Consolidation request transactions may succeed on the execution layer but fail on the consensus layer.
 
-- Navigate to: `https://hoodi.beaconcha.in/validator/<pubkey>#consolidations`. **TODO: update links to mainnet.**
+- Navigate to: `https://beaconcha.in/validator/<pubkey>#consolidations`.
 - Check the consolidation request status for each validator you consolidated to.
 
 ### 5.2 Revoke NODE_OPERATOR_REWARDS_ADJUST_ROLE role
 
-- go to `https://stvaults-hoodi.testnet.fi/vaults/<vault_address>/settings`. **TODO: update links to mainnet.**
-- navigate to "Node Operator Manager Permissions" section, "Adjust rewards on the validators" item.
-- remove withdrawal credentials address.
+- Go to `https://stvaults.lido.fi/vaults/<vault_address>/settings`.
+- Navigate to the "Node Operator Manager Permissions" section, "Adjust rewards on the validators" item.
+- Remove the withdrawal credentials address.