diff --git a/docs/docs/guides/defi/boost-feature.mdx b/docs/docs/guides/defi/boost-feature.mdx index 8a6a72c..26e4880 100644 --- a/docs/docs/guides/defi/boost-feature.mdx +++ b/docs/docs/guides/defi/boost-feature.mdx @@ -81,8 +81,8 @@ Monitor your position regularly and exit Boost if APY remains negative for more ::: :::custom-notes[Further Reading] -- [Maximize Your Rewards With StakeWise Boost ↗](https://stakewise.medium.com/maximize-your-rewards-with-stakewise-boost-8799ae1e5731) -- [How StakeWise Boost Keeps Your Rewards Juicy & Your Stake Safe ↗](https://x.com/stakewise_io/status/1883194716843348259) +- [Maximize Your Rewards With StakeWise Boost ↗](https://blog.stakewise.io/productUpdate/maximize-your-rewards-with-stakewise-boost) +- [How StakeWise Boost Keeps Your Rewards Juicy & Your Stake Safe ↗](https://blog.stakewise.io/caseStudy/how-stakewise-boost-keeps-your-rewards-juicy-and-your-stake-safe) :::
diff --git a/docs/docs/guides/intro.mdx b/docs/docs/guides/intro.mdx index 894ce5d..ea83fe6 100644 --- a/docs/docs/guides/intro.mdx +++ b/docs/docs/guides/intro.mdx @@ -12,7 +12,7 @@ Welcome to the StakeWise Guides! This section provides step-by-step tutorials to ### ETH [Staking →](/docs/guides/staking/intro) Learn how to stake your ETH and GNO with StakeWise. Choose from one-click staking, Vault staking, or solo staking options. -### 🏗️ [Running a Vault →](/docs/guides/running-a-vault/how-to-create-a-vault) +### 🏗️ [Running a Vault →](/docs/guides/running-a-vault/intro) Create and manage your own StakeWise Vault. Set up custom parameters, branding, and start accepting deposits. ### 💰 [Fee Splitter →](/docs/guides/fee-splitter) diff --git a/docs/docs/guides/running-a-vault/getting-your-vault-running.mdx b/docs/docs/guides/running-a-vault/getting-your-vault-running.mdx index 9e01c13..912fb42 100644 --- a/docs/docs/guides/running-a-vault/getting-your-vault-running.mdx +++ b/docs/docs/guides/running-a-vault/getting-your-vault-running.mdx @@ -14,7 +14,7 @@ Follow the steps below to get everything running. ## Setup Checklist ✅ -**1. Execution Client** – A fully synced execution client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/api-documentation/). +**1. Execution Client** – A fully synced execution client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/). Supported clients include Nethermind, Besu, Erigon, Geth, and Reth. [Detailed setup instructions →](/operator/Prerequisites#execution-client). diff --git a/docs/docs/guides/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx b/docs/docs/guides/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx index 963e4e8..b694347 100644 --- a/docs/docs/guides/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx +++ b/docs/docs/guides/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx @@ -9,12 +9,12 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ``` -#### Migrating your stake in the legacy StakeWise Pool to StakeWise V3 +

Migrating your stake in the legacy StakeWise Pool to StakeWise V3

This guide will walk you through the process of migrating your stake in the StakeWise Pool (known as StakeWise V2) to StakeWise V3. Follow the simple steps below to proceed. :::custom-info[Migration Information] -Please consult our [blog post](https://stakewise.medium.com/transitioning-to-stakewise-v3-the-migration-plan-f44d7602e955) about the migration to StakeWise V3 to learn about the reasons and mechanics behind the migration. +Please consult our [blog post](https://blog.stakewise.io/guide/transitioning-to-stakewise-v3-the-migration-path) about the migration to StakeWise V3 to learn about the reasons and mechanics behind the migration. ::: :::custom-info[Requirements] diff --git a/docs/docs/guides/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx b/docs/docs/guides/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx index 77e49c2..040264e 100644 --- a/docs/docs/guides/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx +++ b/docs/docs/guides/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx @@ -9,12 +9,12 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ``` -#### Migrating your stake in the legacy StakeWise Pool to StakeWise V3 +

Migrating your stake in the legacy StakeWise Pool to StakeWise V3

This guide will walk you through the process of migrating your stake in the StakeWise Pool (known as StakeWise V2) to StakeWise V3 on Gnosis Chain. Follow the simple steps below to proceed. :::custom-info[Migration Information] -Please consult our [blog post](https://medium.com/@stakewise/stakewise-v3-on-gnosis-chain-what-to-expect-how-to-migrate-1149a5367c76) about the migration to StakeWise V3 to learn about the reasons and mechanics behind the migration. +Please consult our [blog post](https://blog.stakewise.io/announcement/stakewise-v3-on-gnosis-chain-what-to-expect-and-how-to-migrate) about the migration to StakeWise V3 to learn about the reasons and mechanics behind the migration. ::: :::custom-info[Requirements] diff --git a/docs/docs/guides/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx b/docs/docs/guides/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx index 36c57da..4afdbde 100644 --- a/docs/docs/guides/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx +++ b/docs/docs/guides/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx @@ -9,7 +9,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ``` -#### Learn how to change your withdrawal credentials to a 0x01 type +

Learn how to change your withdrawal credentials to a 0x01 type

:::custom-warning[Important Notice] Partial and full withdrawals from staking require validators to have an execution layer address, known as the `0x01` withdrawal address. By default, validators created using StakeWise Solo have `0x00` withdrawal credentials, which must be changed to `0x01` withdrawal address to exit from staking or benefit from partial withdrawals. This guide will teach you how to change `0x00` withdrawal credentials to a `0x01` address. @@ -22,15 +22,10 @@ To find the right guide for you, choose your operating system. ````mdx-code-block - - To change withdrawal credentials using Ledger Nano X click on "Credentials change" on [StakeWise Solo page](https://v2.stakewise.io/solo) and follow the guide for Ledger Nano X. - :::custom-warning[Important] Ensure that the Windows machine you are using for executing the change in withdrawal credentials is not infected with any malware and can be disconnected from the Internet at a certain stage of the credentials change process. @@ -55,32 +50,23 @@ To find the right guide for you, choose your operating system. The whole procedure will take at most 10 minutes. - ### Find out your BLS withdrawal credentials + ## Find Out Your BLS Withdrawal Credentials Before we can begin the credentials change procedure, you will need to get a list of public BLS credentials for all of your Solo validators. - 1. Go to [StakeWise Solo page](https://v2.stakewise.io/solo) and connect the wallet you used for registering the validators - 2. Ensure that all of your validator bills are paid - 3. Click on `Credentials change` button and download the file under the first step of "Change credentials using CLI". It will download a list of your validator indices and withdrawal credentials that is required for later. - - You should end up with a text file with two lists on two separate lines: - - - Validator indices, each separated by comma (`Validator index list`) - - Withdrawal credentials, each separated by comma, matching the order of respective validator indices (`Withdrawal credentials list`) - - :::custom-tips[Step Complete] - You have successfully completed step 1 of this tutorial. + :::custom-info[Contact StakeWise Team] + To obtain your validator indices and withdrawal credentials, please contact the StakeWise team via [Discord ↗](https://discord.gg/stakewise) or email at info@stakewise.io. ::: - ## Download and launch Ethereum Staking Deposit CLI + ## Download and Launch Ethereum Staking Deposit CLI 1. Go to the [StakeWise Github page](https://github.com/stakewise/staking-deposit-cli/releases/tag/v2.5.1) and download the Windows version of `staking_deposit-cli` zip archive :::custom-info[Note] - This version of the staking_deposit-cli is based on the original cli by the Ethereum Foundation which was modified by StakeWise. You can track all the changes vs the original cli here. + The version of the `staking_deposit-cli` is based on the original cli by the Ethereum Foundation which was modified by StakeWise. ::: - 2. In your `Downloads` folder, right-click on the downloaded package and select Extract All. Set `Desktop` as your destination folder + 2. In your `Downloads` folder, right-click on the downloaded package and select **Extract All**. Set `Desktop` as your destination folder 3. Rename the extracted folder to `staking_deposit-cli` - 4. Move the `deposit.exe` file one directory up i.e. place it into the `staking_deposit-cli` folder + 4. Move the `deposit.exe` file one directory up i.e., place it into the `staking_deposit-cli` folder 5. Disconnect your machine from the Internet / disable Internet at your location to prevent possible intereference with the next steps :::custom-warning[Important] Failing to disconnect from the Internet might expose your machine to online interference with the credentials change procedure and result in a loss of all funds. We strongly recommend disconnecting / disabling the Internet connection at your location before you proceed. @@ -97,11 +83,7 @@ To find the right guide for you, choose your operating system. At this stage, you should see the tool running, asking for your choice of language before you proceed. - :::custom-tips[Step Complete] - You have successfully completed step 2 of this tutorial. - ::: - - ## Generate a .json file for credentials rotation + ## Generate a `.json` File for Credentials Rotation 1. Choose your preferred language for the procedure by entering the relevant number in the **Command Line** (use `3` for English) 2. Type in `mainnet` into the **Command Line** when prompted to choose the network @@ -114,25 +96,20 @@ To find the right guide for you, choose your operating system. Please double-check the withdrawal address you insert to ensure that you entered the correct address. Entering the wrong address will result in a loss of all funds. ::: 8. Copy and paste the withdrawal address into the **Command Line** again when asked to repeat - At this stage, you will have generated a .json file that can be found in the `staking_deposit-cli` folder. + At this stage, you will have generated a .json file that can be found in the `staking_deposit-cli` folder - :::custom-tips[Step Complete] - You have successfully completed step 3 of this tutorial. - ::: - - ## Broadcast the .json file message to the network + ## Broadcast the `.json` File Message to the Network 1. Head to the [Beacon Chain Explorer](https://beaconcha.in/tools/broadcast) website - 2. Upload your .json file into the relevant form + 2. Upload your `.json` file into the relevant form At this stage, your BLS withdrawal credentials should be changed to `0x01` withdrawal address to enable partial and full withdrawals for your Solo validators. Congratulations! - :::custom-tips[Step Complete] - You have now successfully completed all 4 steps of this tutorial and learned how to execute the rotation of BLS withdrawal credentials to `0x01` withdrawal address. - ::: - :::custom-info[Note] - If you are unsure whether the procedure was successful, in about 1 hour after the procedure visit https://beaconcha.in/validator/index#withdrawals by replacing "index" with your actual validator index (e.g. https://beaconcha.in/validator/156849#withdrawals). If the procedure was successful, then you should see an expected date of the first partial withdrawal (i.e. rewards payout) from your validator. If you don't see it, please refer to the guide again. + If you are unsure whether the procedure was successful, in about 1 hour after the procedure visit https://beaconcha.in/validator/index#withdrawals by replacing "index" with your actual validator index (e.g., `https://beaconcha.in/validator/156849#withdrawals`). + + + If the procedure was successful, then you should see an expected date of the first partial withdrawal (i.e., rewards payout) from your validator. If you don't see it, please refer to the guide again. ::: @@ -154,24 +131,19 @@ To find the right guide for you, choose your operating system. 1. Find out the public BLS credentials of your Solo validators 2. Download and launch `staking_deposit-cli` using **Terminal** - 3. Generate a .json file for rotating withdrawal credentials to `0x01` address - 4. Broadcast the .json file's message to the Ethereum Network + 3. Generate a `.json` file for rotating withdrawal credentials to `0x01` address + 4. Broadcast the `.json` file's message to the Ethereum Network The whole procedure will take at most 10 minutes. - ## Find out your BLS withdrawal credentials + ## Find Out Your BLS Withdrawal Credentials Before we can begin the credentials change procedure, you will need to get a list of public BLS credentials for all of your Solo validators. - 1. Go to StakeWise Solo page and connect the wallet you used for registering the validators - 2. Ensure that all of your validator bills are paid - 3. Click on Credentials change button and download the file under the first step of "Change credentials using CLI". It will download a list of your validator indices and withdrawal credentials that is required for later. You should end up with a text file with two lists on two separate lines: - - Validator indices, each separated by comma (Validator index list) - - Withdrawal credentials, each separated by comma, matching the order of respective validator indices (Withdrawal credentials list) - :::custom-tips[Step Complete] - You have successfully completed step 1 of this tutorial. + :::custom-info[Contact StakeWise Team] + To obtain your validator indices and withdrawal credentials, please contact the StakeWise team via [Discord ↗](https://discord.gg/stakewise) or email at info@stakewise.io. ::: - ## Download and launch Ethereum Staking Deposit CLI + ## Download and Launch Ethereum Staking Deposit CLI 1. Go to [**StakeWise Solo**](https://v2.stakewise.io/solo) page and connect the wallet you used for registering the validators 1. Ensure that all of your validator bills are paid @@ -182,11 +154,7 @@ To find the right guide for you, choose your operating system. 1. Validator indices, each separated by comma (`Validator index list`) 1. Withdrawal credentials, each separated by comma, matching the order of respective validator indices (`Withdrawal credentials list`) - :::custom-tips[Step Complete] - You have successfully completed step 1 of this tutorial. - ::: - - ## Download and launch Ethereum Staking Deposit CLI + ## Download and Launch Ethereum Staking Deposit CLI 1. Launch **Terminal** on your Mac and enter the following command to download the latest release of the `staking_deposit-cli` by StakeWise: @@ -195,7 +163,8 @@ To find the right guide for you, choose your operating system. ``` :::custom-info[Note] - This version of the `staking_deposit-cli` is based on the original `cli` by the Ethereum Foundation which was modified by StakeWise. You can track all the changes vs the original `cli` [here](https://github.com/ethereum/staking-deposit-cli/compare/master...stakewise:staking-deposit-cli:master). + This version of the `staking_deposit-cli` is based on the original `cli` by the Ethereum Foundation which was modified by StakeWise. + You can track all the changes vs the original `cli` [here](https://github.com/ethereum/staking-deposit-cli/compare/master...stakewise:staking-deposit-cli:master). ::: 2. Disconnect your Mac from the Internet / disable Internet at your location to prevent possible intereference with the next steps @@ -228,11 +197,7 @@ To find the right guide for you, choose your operating system. At this stage, you should see the tool running, asking for your choice of language before you proceed. - :::custom-tips[Step Complete] - You have successfully completed step 2 of this tutorial. - ::: - - ## Generate a .json file for credentials rotation + ## Generate a `.json` File for Credentials Rotation 1. Choose your preferred language for the procedure by entering the relevant number in the **Terminal** (use `3` for English): 2. Type in `mainnet` into the **Terminal** when prompted to choose the network @@ -248,25 +213,17 @@ To find the right guide for you, choose your operating system. 8. Copy and paste the withdrawal address into the **Terminal** again when asked to repeat - At this stage, you will have generated a .json file that can be found in the `staking_deposit-cli` folder. - - :::custom-tips[Step Complete] - You have successfully completed step 3 of this tutorial. - ::: + At this stage, you will have generated a `.json` file that can be found in the `staking_deposit-cli` folder. - ## Broadcast the .json file message to the network + ## Broadcast the `.json` File Message to the Network 1. Head to the [**Beacon Chain Explorer**](https://beaconcha.in/tools/broadcast) website - 2. Upload your .json file into the relevant form. + 2. Upload your `.json` file into the relevant form At this stage, your BLS withdrawal credentials should be changed to `0x01` withdrawal address to enable partial and full withdrawals for your Solo validators. Congratulations! - :::custom-tips[Step Complete] - You have now successfully completed all 4 steps of this tutorial and learned how to execute the rotation of BLS withdrawal credentials to `0x01` withdrawal address. - ::: - :::custom-info[Note] - If you are unsure whether the procedure was successful, in about 1 hour after the procedure visit `https://beaconcha.in/validator/[index]#withdrawals` by replacing `index` with your actual validator index (e.g. [https://beaconcha.in/validator/156849#withdrawals](https://beaconcha.in/validator/156849#withdrawals)). If the procedure was successful, then you should see an expected date of the first partial withdrawal (i.e. rewards payout) from your validator. If you don't see it, please refer to the guide again. + If you are unsure whether the procedure was successful, in about 1 hour after the procedure visit `https://beaconcha.in/validator/[index]#withdrawals` by replacing `index` with your actual validator index (e.g., `https://beaconcha.in/validator/156849#withdrawals`). If the procedure was successful, then you should see an expected date of the first partial withdrawal (i.e. rewards payout) from your validator. If you don't see it, please refer to the guide again. ::: diff --git a/docs/docs/guides/stakewise-v2/04-exit-solo-validator.mdx b/docs/docs/guides/stakewise-v2/04-exit-solo-validator.mdx index 74fb336..026ac52 100644 --- a/docs/docs/guides/stakewise-v2/04-exit-solo-validator.mdx +++ b/docs/docs/guides/stakewise-v2/04-exit-solo-validator.mdx @@ -4,7 +4,7 @@ sidebar_position: 4 # Exit Solo Validator -#### Learn how to unstake from StakeWise Solo. +

Learn how to unstake from StakeWise Solo

:::custom-warning[Prerequisites] Note that you must [**rotate your Solo validator withdrawal credentials**](./03-change-solo-withdrawal-credentials-to-0x01-address.mdx) to 0x01 withdrawal address before you can request a validator exit. This is a technical requirement of the Ethereum network. diff --git a/docs/docs/oracles/oracle-duties.mdx b/docs/docs/oracles/oracle-duties.mdx index a77df04..5b46918 100644 --- a/docs/docs/oracles/oracle-duties.mdx +++ b/docs/docs/oracles/oracle-duties.mdx @@ -18,7 +18,7 @@ Oracles run the [v3-oracle ↗](https://github.com/stakewise/v3-oracle) nodes an Oracles approve validator registration requests before they are submitted to the Beacon Chain [Deposit Contract ↗](https://etherscan.io/address/0x00000000219ab540356cbb839cbe05303d7705fa#code). -The [Operator Service →](../../operator/start-operator) periodically checks whether its Vaults have accumulated enough ETH for registering new validator(s). +The [Operator Service →](../../operator/intro) periodically checks whether its Vaults have accumulated enough ETH for registering new validator(s). When the Vault has enough ETH, the operator sends a registration approval request to Oracles that includes encrypted exit signature(s) for the validator(s) it is attempting to create. This is done to maintain the protocol's ability to exit validators on demand, and to perform checks against the front-running withdrawal credentials attack described [here ↗](https://blog.lido.fi/vulnerability-response-update/). The operator must receive **8 out of 11 approvals** from Oracles to register a validator for the Vault. @@ -59,7 +59,7 @@ The reward update process has protocol-wide impact. ## Validator Exits The validator exit process is automated and trustless. -Validator exits require exit signatures that are generated during the [Validator Registration →](../../operator/start-operator) process. +Validator exits require exit signatures that are generated during the validator registration process. As part of registration, the Operator Service encrypts exit signatures using Shamir's secret sharing and distributes them to all Oracles. diff --git a/operator-v3/Prerequisites.mdx b/operator-v3/Prerequisites.mdx index a8d2625..4eebdea 100644 --- a/operator-v3/Prerequisites.mdx +++ b/operator-v3/Prerequisites.mdx @@ -14,7 +14,7 @@ Before installing the Operator Service, ensure your node infrastructure meets th ## Execution Client -Your execution node must be fully synced and running. Any client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/api-documentation/) can be used: +Your execution node must be fully synced and running. Any client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/) can be used: - **[Nethermind ↗](https://launchpad.ethereum.org/en/nethermind)** — (Ethereum, Gnosis) - **[Besu ↗](https://launchpad.ethereum.org/en/besu)** — (Ethereum) diff --git a/operator-v3/additional-actions/_category_.json b/operator-v3/additional-actions/_category_.json index 822b5db..76976cd 100644 --- a/operator-v3/additional-actions/_category_.json +++ b/operator-v3/additional-actions/_category_.json @@ -1,6 +1,6 @@ { "label": "Additional Actions", - "position": 7, + "position": 6, "link": { "type": "doc", "id": "additional-actions/index" diff --git a/operator-v3/alternative-key-management/_category_.json b/operator-v3/alternative-key-management/_category_.json index e8043ce..ed05e29 100644 --- a/operator-v3/alternative-key-management/_category_.json +++ b/operator-v3/alternative-key-management/_category_.json @@ -1,6 +1,6 @@ { "label": "Alternative Key Management", - "position": 6, + "position": 7, "link": { "type": "doc", "id": "alternative-key-management/index" diff --git a/operator-v3/alternative-key-management/dvt/obol-setup.mdx b/operator-v3/alternative-key-management/dvt/obol-setup.mdx index 8b196b9..277bd34 100644 --- a/operator-v3/alternative-key-management/dvt/obol-setup.mdx +++ b/operator-v3/alternative-key-management/dvt/obol-setup.mdx @@ -25,7 +25,7 @@ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` 3. [Create Vault →](/docs/guides/running-a-vault/how-to-create-a-vault) -4. [Setup Operator Service →](/operator/Installation) +4. [Setup Operator Service →](/operator/v3/Installation) :::custom-warning[Important - Keystore Password Configuration] When using the `create-keys` command, add the `--per-keystore-password` flag to generate a keystore with a separate password file for each keystore. This is necessary for the normal operation of the Charon CLI, especially when splitting keys. diff --git a/operator-v3/alternative-key-management/dvt/ssv-setup.mdx b/operator-v3/alternative-key-management/dvt/ssv-setup.mdx index 78c5667..09374e6 100644 --- a/operator-v3/alternative-key-management/dvt/ssv-setup.mdx +++ b/operator-v3/alternative-key-management/dvt/ssv-setup.mdx @@ -21,7 +21,7 @@ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` 3. [Create Vault →](/docs/guides/running-a-vault/how-to-create-a-vault) -4. [Setup Operator Service →](/operator/intro) +4. [Setup Operator Service →](/operator/v3/Installation) :::custom-notes[Hardware Requirements] SSV node requires (in addition to your beacon/execution nodes): ⚙️ 2 cores, ⚡️ 2GB RAM, 💾 20GB storage, 🚀 >8K IOPS. See [full requirements ↗](https://docs.ssv.network/operators/operator-node/node-setup/hardware-requirements). diff --git a/operator-v3/v4-upgrade-guide.mdx b/operator-v3/v4-upgrade-guide.mdx index 0829c9e..baa6a95 100644 --- a/operator-v3/v4-upgrade-guide.mdx +++ b/operator-v3/v4-upgrade-guide.mdx @@ -14,7 +14,7 @@ This guide covers the key changes and upgrade steps for StakeWise Operator V4, i :::custom-info[Prerequisites] Ensure your Vault is updated to **version 5** for Ethereum network or **version 3** for Gnosis network for full Pectra compatibility. See [Prerequisites →](./Prerequisites#deployed-vault) for details on checking and upgrading your Vault version. -Additionally, ensure your Operator Service wallet has the [Validators Manager →](validators-manager#step-2-assign-validators-manager-role) role assigned in your Vault settings for proper operation. +Additionally, ensure your Operator Service wallet has the [Validators Manager →](/operator/validators-manager#step-2-assign-validators-manager-role) role assigned in your Vault settings for proper operation. ::: ## Validator Changes @@ -25,7 +25,7 @@ After the Pectra upgrade ([EIP-7251 ↗](https://eips.ethereum.org/EIPS/eip-7251 - To register `0x01` validators, add the flag `--validators-type=0x01` :::custom-notes[Consolidations] -To migrate `0x01` validators to `0x02`, use the `consolidate` command. Read more about it [here →](./additional-actions/consolidate-validators). +To migrate `0x01` validators to `0x02`, use the `consolidate` command. Read more about it [here →](/operator/additional-actions/consolidate-validators). ::: When funding validators: @@ -114,7 +114,7 @@ V4 Operator **no longer requires pre-uploaded deposit data** for validator regis :::custom-info[Important] To support this new flow, you must **assign your operator wallet as the Validators Manager** in the Vault settings. -🔗 **Setup Guide**: [How to Set Up Validators Manager →](./validators-manager). +🔗 **Setup Guide**: [How to Set Up Validators Manager →](/operator/validators-manager). ::: ## Automated Rewards Withdrawals @@ -122,7 +122,7 @@ To support this new flow, you must **assign your operator wallet as the Validato It is now possible to **periodically withdraw rewards** for the Vault's fee shareholders. :::custom-notes[Deep Dive] -For detailed instructions on fee claiming, see [Fee Claiming →](./additional-actions/fee-claiming). +For detailed instructions on fee claiming, see [Fee Claiming →](/operator/additional-actions/fee-claiming). ::: ## Parameter Changes diff --git a/operator/Installation.mdx b/operator/Installation.mdx index e3576d5..9a5d072 100644 --- a/operator/Installation.mdx +++ b/operator/Installation.mdx @@ -1,6 +1,6 @@ --- title: 4. Installation -sidebar_position: 4 +sidebar_position: 3 --- import Tabs from '@theme/Tabs'; diff --git a/operator/Prerequisites.mdx b/operator/Prerequisites.mdx index 4380d61..97e7acb 100644 --- a/operator/Prerequisites.mdx +++ b/operator/Prerequisites.mdx @@ -38,7 +38,7 @@ You can find your Vault version in the **Details** section of your Vault page. If your Vault is below the required version, log in as a Vault Admin and click "Upgrade" at the top of the Vault page. **Using older Vault versions:** -If you have an older Vault and cannot upgrade, follow the documentation [here ↗](https://v3-docs.stakewise.io/for-operators/operator-service). +If you have an older Vault and cannot upgrade, follow the documentation [here ↗](/operator/v3/intro). ::: ### Finding Your Vault Address @@ -74,7 +74,7 @@ A new experimental feature allows the Operator Service to automatically install ### Execution Client -Your execution node must be fully synced and running. Any client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/api-documentation/) can be used: +Your execution node must be fully synced and running. Any client that supports the [ETH Execution API specification ↗](https://ethereum.github.io/execution-apis/) can be used: - **[Nethermind ↗](https://launchpad.ethereum.org/en/nethermind)** — (Ethereum, Gnosis) - **[Besu ↗](https://launchpad.ethereum.org/en/besu)** — (Ethereum) diff --git a/operator/additional-actions/index.mdx b/operator/additional-actions/index.mdx index 5db37d0..4416111 100644 --- a/operator/additional-actions/index.mdx +++ b/operator/additional-actions/index.mdx @@ -25,4 +25,6 @@ With these tools, you can: [Rated Network Integration →](./rated-network) — track validator performance and analytics. +[Process Meta Vaults →](./process-metavaults) — update states and process deposits and exits for meta vaults. + Dive into each action to see when it is useful and how to set it up in your environment. diff --git a/operator/alternative-key-management/dvt/ssv-setup.mdx b/operator/alternative-key-management/dvt/ssv-setup.mdx index 78c5667..8853a06 100644 --- a/operator/alternative-key-management/dvt/ssv-setup.mdx +++ b/operator/alternative-key-management/dvt/ssv-setup.mdx @@ -21,7 +21,7 @@ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ``` 3. [Create Vault →](/docs/guides/running-a-vault/how-to-create-a-vault) -4. [Setup Operator Service →](/operator/intro) +4. [Setup Operator Service →](/operator/Installation) :::custom-notes[Hardware Requirements] SSV node requires (in addition to your beacon/execution nodes): ⚙️ 2 cores, ⚡️ 2GB RAM, 💾 20GB storage, 🚀 >8K IOPS. See [full requirements ↗](https://docs.ssv.network/operators/operator-node/node-setup/hardware-requirements). diff --git a/operator/node-setup.mdx b/operator/node-setup.mdx index 3218243..095fe12 100644 --- a/operator/node-setup.mdx +++ b/operator/node-setup.mdx @@ -1,6 +1,6 @@ --- title: Automated Node Setup -sidebar_position: 11 +sidebar_position: 9 --- # Automated Node Setup diff --git a/operator/smoothing-pool-relays.mdx b/operator/smoothing-pool-relays.mdx index 3bc106a..569c7f0 100644 --- a/operator/smoothing-pool-relays.mdx +++ b/operator/smoothing-pool-relays.mdx @@ -1,6 +1,6 @@ --- title: Smoothing Pool Relays -sidebar_position: 10 +sidebar_position: 8 --- import Tabs from '@theme/Tabs'; diff --git a/operator/start-operator.mdx b/operator/start-operator.mdx index 6fc6e21..471685f 100644 --- a/operator/start-operator.mdx +++ b/operator/start-operator.mdx @@ -1,6 +1,6 @@ --- title: 7. Start Operator -sidebar_position: 7 +sidebar_position: 6 --- import Tabs from '@theme/Tabs'; diff --git a/operator/validator-keys.mdx b/operator/validator-keys.mdx index 4d4b01a..f00f702 100644 --- a/operator/validator-keys.mdx +++ b/operator/validator-keys.mdx @@ -1,6 +1,6 @@ --- title: 5. Validator Keys -sidebar_position: 5 +sidebar_position: 4 --- import Tabs from '@theme/Tabs'; diff --git a/operator/validators-manager.mdx b/operator/validators-manager.mdx index 4ed2d5a..3235a45 100644 --- a/operator/validators-manager.mdx +++ b/operator/validators-manager.mdx @@ -1,6 +1,6 @@ --- title: 6. Validators Manager -sidebar_position: 6 +sidebar_position: 5 --- import Tabs from '@theme/Tabs'; diff --git a/operator/vault-performance.mdx b/operator/vault-performance.mdx index 2595e53..4a0685b 100644 --- a/operator/vault-performance.mdx +++ b/operator/vault-performance.mdx @@ -1,6 +1,6 @@ --- title: Vault Performance -sidebar_position: 11 +sidebar_position: 10 --- import Tabs from '@theme/Tabs';