diff --git a/docs/docs/glossary.mdx b/docs/docs/glossary.mdx index 921231cf..534a5d9b 100644 --- a/docs/docs/glossary.mdx +++ b/docs/docs/glossary.mdx @@ -5,136 +5,136 @@ description: Key terms and concepts in the StakeWise protocol # Glossary -### Blocklist Vault +### Blocklist Vault Blocklist Vault A Vault type that accepts deposits from any wallet except those on a specified blocklist. The blocklist is managed by the Whitelist/Blocklist Manager role. -### Boost +### Boost Boost A StakeWise feature that amplifies staking rewards by using osTokens as collateral on Aave to borrow additional assets, which are then staked again. This creates a leverage loop that can provide up to 3x boost in staking rewards compared to normal staking. -### Burning +### Burning Burning The process of returning minted osTokens to a Vault in exchange for unlocking the staked collateral that backs them. Users must burn all minted osTokens plus accrued protocol fees to fully unstake. Partial burns are possible to reduce debt or improve position health. -### Compound Validator (0x02) +### Compound Validator (0x02) Compound Validator A validator type that supports variable effective balances from 32 ETH up to 2048 ETH (or 1 GNO to 64 GNO on Gnosis Chain). These validators support automatic funding, compounding rewards, and partial withdrawals. Converting from 0x01 to 0x02 is irreversible. -### Consolidation +### Consolidation Consolidation The process of merging multiple legacy validators (0x01) into compound validators (0x02), or combining the balance of existing compound validators to improve capital efficiency and reduce infrastructure overhead. -### DAO-Approved Vault +### DAO-Approved Vault DAO-Approved Vault Vaults that meet stringent DAO criteria (defined in [SWIP-24 ↗](https://forum.stakewise.io/t/swip-24-establish-a-policy-for-enabling-100-oseth-minting-in-select-vaults/1724)) and qualify for 100% minting threshold (LTV) for osETH/osGNO—enabling automatic liquid staking token issuance without overcollateralization. This maximizes capital efficiency and unlocks advanced use cases like consumer liquid staking, exchange integrations, and leveraged DeFi strategies. Requirements include substantial stake (≥10k ETH / ≥5k GNO), fee caps (≤5% / ≤15%), above-median performance, Vault v3, significant SWISE bond (5M / 1M), and DAO governance approval. -### ERC-20 Vault +### ERC-20 Vault ERC-20 Vault A Vault type that issues transferable ERC-20 tokens representing stake in the Vault. Operators set the token's name and symbol, enabling custom DeFi ecosystems around the Vault's token. Users can transfer their stake as long as they don't have osToken minted against it. -### Automatic Unboost +### Automatic Unboost Automatic Unboost A safety mechanism in Boost that automatically unboosts positions approaching the liquidation threshold. When any position reaches 94.5% LTV, anyone can trigger an automatic unboosting transaction to protect the user, with all funds remaining under the original owner's control. -### Exit Queue +### Exit Queue Exit Queue A queue system that manages withdrawal requests from a Vault. When users request to withdraw, they receive a position ticket tracking their place in line. As ETH becomes available through unbonded assets or validator exits, users can claim their funds according to their queue position. -### OsToken Exchange Rate +### osToken Exchange Rate OsToken Exchange Rate The amount of underlying assets (ETH or GNO) that can be received when redeeming osToken within the protocol. This rate increases over time as staking rewards accrue, reflected through the `convertToAssets` and `convertToShares` functions in the osTokenVaultController contract. -### Fee Recipient +### Fee Recipient Fee Recipient The address designated to receive Vault fees. Set by the Vault Admin and can be updated over time. Typically the Vault operator or a multisig controlled by the operator team. -### Harvest +### Harvest Harvest The process of updating a Vault's state on-chain, which synchronizes the Vault's balance with the consensus layer, applies fee accruals, and processes the exit queue. Can be triggered automatically by the Operator Service (every 12 hours by default) or manually by users during interactions. -### Keeper +### Keeper Keeper The StakeWise smart contract that coordinates communication between the Operator Service and the Oracle network. The Keeper manages validator registration approvals by ensuring proper Oracle consensus, and processes reward updates including consensus rewards and Smoothing Pool distributions from the Oracle network. -### Legacy Validator (0x01) +### Legacy Validator (0x01) Legacy Validator The original validator type with a fixed stake of 32 ETH (or 1 GNO on Gnosis Chain). These validators automatically sweep excess balance above 32 ETH back to the withdrawal address. No top-up funding is available for 0x01 validators. -### Liquidation +### Liquidation Liquidation In 90% LTV Vaults, the process of closing an unhealthy osToken position that exceeds 92% LTV. Anyone can liquidate by burning all minted osTokens against the collateral. The liquidator receives the underlying collateral value plus a 1% premium, with the penalty deducted from the staker's collateral. Positions in 99.99% LTV Vaults are exempt from liquidation. -### LTV (Loan-to-Value) +### LTV (Loan-to-Value) LTV (Loan-to-Value) The ratio of minted osToken value to staked collateral value, expressed as a percentage. Standard Vaults have 90% LTV, while DAO-approved Vaults can have up to 99.99% LTV (osETH) or 99.95% LTV (osGNO). This determines the maximum amount of osToken that can be minted against staked assets. -### MetaVault +### MetaVault MetaVault A Vault type that does not register validators directly, instead delegating accumulated assets to sub-Vaults managed by the Vault Admin. Deposits are distributed across underlying sub-Vaults (up to 50 maximum) according to curator-defined allocation logic. -### Minting +### Minting Minting The process of issuing osTokens against staked assets held in a Vault. Minting limits are determined by the Vault's LTV ratio to ensure overcollateralization. Users can mint osTokens to access liquidity while their stake continues earning rewards. -### Operator Service +### Operator Service Operator Service Specialized software that node operators run alongside their Ethereum consensus and execution clients to manage Vault operations. Automates validator registration, consolidations, withdrawals, state updates, and fee claims. -### Oracle Network +### Oracle Network Oracle Network StakeWise's decentralized network of Oracle nodes that connects smart contracts to the Beacon Chain. Manages validator registration approvals, calculates rewards and penalties, maintains osToken exchange rates, and enforces validator exits when needed. -### osETH +### osToken osToken +Short for Overcollateralized Staked Token. StakeWise's liquid staking tokens (osETH on Ethereum, osGNO on Gnosis Chain) that represent staked assets plus accrued rewards. The value of staked assets backing osToken exceeds the token's value, providing a safety buffer against slashing and validator underperformance. + +### osETH osETH The overcollateralized liquid staking token on Ethereum. A repricing ERC-20 token that represents staked ETH plus accumulated rewards, with its value increasing over time as staking rewards accrue. -### osGNO +### osGNO osGNO The overcollateralized liquid staking token on Gnosis Chain. A repricing ERC-20 token that represents staked GNO plus accumulated rewards, with its value increasing over time as staking rewards accrue. -### osToken -Short for Overcollateralized Staked Token. StakeWise's liquid staking tokens (osETH on Ethereum, osGNO on Gnosis Chain) that represent staked assets plus accrued rewards. The value of staked assets backing osToken exceeds the token's value, providing a safety buffer against slashing and validator underperformance. - -### osToken Fee +### osToken Fee osToken Fee A 5% fee charged by StakeWise DAO on rewards accumulated by osToken. The fee is applied continuously to users' osToken debt (the amount they must burn to exit), with collected fees going to the DAO Treasury. -### Partial Withdrawal +### Partial Withdrawal Partial Withdrawal A withdrawal of rewards from a compound validator (0x02) without fully exiting the validator. Enabled by EIP-7002, partial withdrawals allow Vaults to access accumulated rewards above the minimum stake requirement while keeping validators active. -### OsToken Position +### OsToken Position OsToken Position An osToken minting position representing the relationship between a user's staked collateral in a Vault and their minted osToken debt. Position health is tracked through LTV ratios. -### Exit Queue Ticket +### Exit Queue Ticket Exit Queue Ticket A record issued when a user enters the exit queue, tracking their place in line and the amount they've requested to withdraw. Users can claim available funds according to their ticket number as ETH becomes available in the Vault. -### Private Vault +### Private Vault Private Vault A Vault type that only accepts deposits from wallets that have been whitelisted by the Vault Admin. Access control is managed by the Whitelist/Blocklist Manager role. -### Repricing Token +### Repricing Token Repricing Token A token whose redemption value increases over time rather than its quantity. osToken is a repricing token—each osETH or osGNO becomes worth more of the underlying asset as staking rewards accrue, reflected through an increasing exchange rate. -### Smoothing Pool +### Smoothing Pool Smoothing Pool A mechanism for distributing block proposal rewards (MEV and priority fees) evenly across all participating Vaults. Instead of keeping volatile block rewards, Vaults contribute them to a pool that provides stable, predictable returns. Vaults using the smoothing pool must operate [DAO-approved MEV relays →](/operator/smoothing-pool-relays). -### Standard Vault +### Standard Vault Standard Vault The most common Vault type that accepts deposits from any wallet and issues non-transferable shares that earn rewards. Users receive Vault shares representing their proportional stake in the Vault. -### SWISE +### SWISE SWISE The governance token of StakeWise DAO. SWISE holders vote on protocol parameters, oracle selection, upgrades, fees, and other governance decisions through StakeWise Improvement Proposals (SWIPs). -### Unbonded ETH +### Unbonded ETH Unbonded ETH ETH in a Vault that is not locked in validators. This includes excess deposits, staking rewards, and MEV that have not been allocated to new validators yet. Unbonded ETH provides liquidity for processing withdrawals from the exit queue. -### Unboost Queue +### Unboost Queue Unboost Queue A queue system that manages withdrawal requests from Boost positions. When users request to unboost, they enter the queue and can claim their assets as they will exit from the validators. -### Vault +### Vault Vault An isolated, customizable smart contract that functions as an individual staking pool. Vault operators accept deposits from stakers, register and manage validators, and offer tailored staking services. Each Vault operates independently with its own fee structure, MEV strategy, and risk profile. -### Vault Admin +### Vault Admin Vault Admin The primary controller of a Vault, responsible for overall configuration. The Admin can manage all roles and permissions, modify fees and fee recipients, update branding, and configure Vault settings. Can be a single wallet, multisig, or DAO. -### Vault Capacity +### Vault Capacity Vault Capacity An immutable deposit limit set during Vault creation that controls the maximum amount of ETH the Vault can accept. When left unset, Vaults have unlimited capacity by default. Helps operators control validator set size based on infrastructure capabilities. -### Own Escrow +### Own Escrow Own Escrow MEV strategy where block proposal rewards are collected solely by individual Vaults. Own Escrow allows a Vault to choose an independent approach to earning block production rewards, like using any relay of choice, because it does not rely on sharing such rewards with other Vaults. Own Escrow targets maximum value capture but with increased variability. -### Vault Fee +### Vault Fee Vault Fee A percentage fee charged by Vault operators on staking rewards, ranging from 0% to 100%. The fee is automatically deducted when Vault state is updated and the vault shares are minted to the fee recipient. Fees can only be increased by 20% at a time with a 3-day delay between updates. -### Vault Fee Claimer +### Vault Fee Claimer Vault Fee Claimer A Vault role that can claim accumulated Vault fees on behalf of the Vault's fee recipients. Set by the Vault Admin. -### Vault Operator +### Vault Operator Vault Operator Entities or individuals who run validators for a Vault. They operate the infrastructure and run the Operator Service software that automates essential Vault management tasks such as validator registration, consolidations, and withdrawals. -### Vault Shares +### Vault Shares Vault Shares The accounting mechanism used by all Vaults to represent a user's proportional stake in the Vault. Shares accrue rewards over time and can be used as collateral for minting osTokens. In Standard, Private, and Blocklist Vaults, shares are non-transferable. In ERC-20 Vaults, shares are represented as transferable ERC-20 tokens. -### Validators Manager +### Validators Manager Validators Manager A critical Vault role that grants permission to execute validator operations including registration, funding, consolidation, and withdrawals. The Operator Service requires this role to automatically manage the Vault's validators. -### Whitelist/Blocklist Manager +### Whitelist/Blocklist Manager Whitelist/Blocklist Manager A Vault role that controls deposit access permissions. Can add or remove accounts authorized to deposit (whitelist) or prohibited from depositing (blocklist). Only appears in Private Vaults or Vaults with blocklist functionality enabled. diff --git a/docs/docs/overview.mdx b/docs/docs/overview.mdx index 403da0a3..210adc14 100644 --- a/docs/docs/overview.mdx +++ b/docs/docs/overview.mdx @@ -9,7 +9,7 @@ description: "Overview of StakeWise ecosystem: Protocol, Interface, DAO, and Lab StakeWise has several distinct areas that serve different purposes — here's how to tell them apart. -- **[StakeWise Protocol](https://github.com/stakewise/v3-core)**: A modular collection of smart contracts powering decentralized liquid staking on Ethereum and Gnosis Chain. The protocol includes customizable Vaults (including blocklist, private, and ERC20 variants), an over-collateralized token system (osToken), validator lifecycle management, MEV capture and distribution, and governance controls. -- **[StakeWise Interface](https://app.stakewise.io/)**: A web interface that allows for easy interaction with the StakeWise protocol. The interface allows users to stake ETH, browse the Vault marketplace, create their own Vaults, and discover different DeFi strategies to maximize earnings. -- **[StakeWise DAO](https://vote.stakewise.io/#/)**: A governance system for governing the StakeWise Protocol, enabled by the SWISE token. -- **[StakeWise Labs](https://x.com/stakewise_io)**: The core development team behind StakeWise Protocol and its ecosystem tools. +- **[StakeWise Protocol ↗](https://github.com/stakewise/v3-core)**: A modular collection of smart contracts powering decentralized liquid staking on Ethereum and Gnosis Chain. The protocol includes customizable Vaults (including blocklist, private, and ERC20 variants), an over-collateralized token system (osToken), validator lifecycle management, MEV capture and distribution, and governance controls. +- **[StakeWise Interface ↗](https://app.stakewise.io/)**: A web interface that allows for easy interaction with the StakeWise protocol. The interface allows users to stake ETH, browse the Vault marketplace, create their own Vaults, and discover different DeFi strategies to maximize earnings. +- **[StakeWise DAO ↗](https://vote.stakewise.io/#/)**: A governance system for governing the StakeWise Protocol, enabled by the SWISE token. +- **[StakeWise Labs ↗](https://x.com/stakewise_io)**: The core development team behind StakeWise Protocol and its ecosystem tools. diff --git a/docs/docs/vaults/how-vaults-work.mdx b/docs/docs/vaults/how-vaults-work.mdx index 778e71c7..e5bf0ec9 100644 --- a/docs/docs/vaults/how-vaults-work.mdx +++ b/docs/docs/vaults/how-vaults-work.mdx @@ -84,7 +84,7 @@ Users can mint osTokens for instant liquidity or withdraw. When users choose to As ETH becomes available to the Vault, users can claim what is available. If only part of the requested amount is available, they can claim that portion immediately and receive an updated ticket for the remainder. -Partial withdrawals for `0x02` compound validators are now supported and can now be triggered from the execution layer via [EIP-7002](https://eips.ethereum.org/EIPS/eip-7002)4. +Partial withdrawals for `0x02` compound validators are now supported and can now be triggered from the execution layer via [EIP-7002 ↗](https://eips.ethereum.org/EIPS/eip-7002)4. The withdrawal fulfillment process is automated by the Operator Service, which manages validator exits and partial withdrawals among other responsibilities to ensure timely processing of the exit queue. :::custom-info[Processing Time] diff --git a/operator/manage-vault/add-extra-rewards.mdx b/operator/manage-vault/add-extra-rewards.mdx index 210ecc49..d7e70166 100644 --- a/operator/manage-vault/add-extra-rewards.mdx +++ b/operator/manage-vault/add-extra-rewards.mdx @@ -20,7 +20,7 @@ Please note that Vault incentives are currently supported only on Ethereum. Users can claim their incentives at any time through the [StakeWise App ↗](https://app.stakewise.io/): -![Claiming](./img/vault-incentives.gif) +![Claiming](./img/claim.gif) ## Periodic Distribution to the Vault diff --git a/operator/manage-vault/img/claim.gif b/operator/manage-vault/img/claim.gif new file mode 100644 index 00000000..387a8885 Binary files /dev/null and b/operator/manage-vault/img/claim.gif differ diff --git a/operator/manage-vault/img/vault-incentives.gif b/operator/manage-vault/img/vault-incentives.gif deleted file mode 100644 index 6d5d5066..00000000 Binary files a/operator/manage-vault/img/vault-incentives.gif and /dev/null differ diff --git a/operator/operator-service-v3/alternative-key-management/api-mode.mdx b/operator/operator-service-v3/alternative-key-management/api-mode.mdx index 813bad4e..c4d63b90 100644 --- a/operator/operator-service-v3/alternative-key-management/api-mode.mdx +++ b/operator/operator-service-v3/alternative-key-management/api-mode.mdx @@ -144,7 +144,7 @@ Response: ## DVT Relayer -When using a DVT setup, a specialized DVT relayer is required. Unlike a regular relayer, you do not need to set up a dedicated relayer instance. Instead, you can use the public DVT relayer available at: [https://mainnet-dvt-relayer.stakewise.io/](https://mainnet-dvt-relayer.stakewise.io/). +When using a DVT setup, a specialized DVT relayer is required. Unlike a regular relayer, you do not need to set up a dedicated relayer instance. Instead, you can use the public DVT relayer available at: [https://mainnet-dvt-relayer.stakewise.io/ ↗](https://mainnet-dvt-relayer.stakewise.io/). The Operator environment configuration is similar to that of a regular relayer. However, you must specify the relayer type as follows: diff --git a/staker/boost.mdx b/staker/boost.mdx index 10c93c16..64ccac19 100644 --- a/staker/boost.mdx +++ b/staker/boost.mdx @@ -21,7 +21,7 @@ To use Boost, you need osETH in your wallet.
-1. Open [app.stakewise.io](https://app.stakewise.io) and connect your wallet. +1. Open [app.stakewise.io ↗](https://app.stakewise.io) and connect your wallet. 2. Select the **Boost** tab. 3. Check the **Boost APY** displayed to decide if it's a good time to enter. 4. Enter the amount of osETH you want to boost. @@ -51,7 +51,7 @@ Periodically check on your position to ensure the Boost APY is positive. If you
-1. Open [app.stakewise.io](https://app.stakewise.io) and connect your wallet. +1. Open [app.stakewise.io ↗](https://app.stakewise.io) and connect your wallet. 2. Select the **Unboost** tab. 3. Enter the percentage of the position you want to exit. 4. Confirm the transaction. Your request enters the unboost queue, where processing time depends on the network exit queue. Only one unboost request can be active at a time. diff --git a/staker/risks.mdx b/staker/risks.mdx index 89b06bbe..10922824 100644 --- a/staker/risks.mdx +++ b/staker/risks.mdx @@ -7,20 +7,20 @@ description: Risks of liquid staking with StakeWise — Vault performance, smart Liquid staking carries inherent risks. This page covers them and how StakeWise addresses each. -## Vault Performance +## Vault Performance Vault Performance Your staking rewards depend on how well your Vault performs. Ethereum rewards validators for performing their duties correctly and [penalizes them ↗](https://ethereum.org/developers/docs/consensus-mechanisms/pos/rewards-and-penalties#penalties) for going offline, missing attestations, or acting maliciously. These penalties reduce the staked ETH in your Vault. Each Vault is fully isolated — poor performance in one Vault has no effect on stakers in other Vaults. You can review every Vault's performance in the app before staking. If a Vault's performance starts declining, consider unstaking and moving to a better-performing Vault. -## Smart Contract +## Smart Contract Smart Contract All DeFi protocols carry smart contract risk. StakeWise runs on battle-tested, [regularly audited](/contracts/audits) contracts that secure over $1B in staked assets. The protocol has been live since 2021 with no security incidents. -## osETH Depeg +## osETH Depeg osETH Depeg osETH could temporarily trade below its fair value on secondary markets. The protocol's [redemption and liquidation mechanisms](/docs/ostoken/how-ostoken-works#peg-maintenance) create arbitrage incentives that keep the market price aligned with the underlying value. -## Boost +## Boost Boost As with any leveraged strategy, [Boost](/docs/vaults/boost) carries liquidation and penalty risks. If Aave's borrow rate exceeds the staking rate for too long, your Boost APY turns negative and your position loses value every day it stays open, while your LTV drifts toward Aave's liquidation threshold. A [2% safety buffer](/docs/vaults/boost#safety-mechanisms) between max borrow LTV and the liquidation threshold gives your position room to absorb this drift, and StakeWise automatically unboosts as you approach the threshold. Stay updated via [StakeWise Discord ↗](https://discord.com/invite/2BSdr2g). diff --git a/staker/simple-staking.mdx b/staker/simple-staking.mdx index f39b3c2b..edbbbdd0 100644 --- a/staker/simple-staking.mdx +++ b/staker/simple-staking.mdx @@ -8,9 +8,9 @@ import Tooltip from '@site/src/components/Tooltip/Tooltip'; # Simple Staking -The simplest way to stake with StakeWise is through the [StakeWise App ↗](https://app.stakewise.io) — deposit any amount of ETH and stake it in a single click. Your assets are routed through a [MetaVault](/docs/vaults/meta-vaults) that distributes them across the best-performing Sub-vaults — currently just the [Genesis Vault](https://app.stakewise.io/vault/mainnet/0xac0f906e433d58fa868f936e8a43230473652885), with more to come. +The simplest way to stake with StakeWise is through the [StakeWise App ↗](https://app.stakewise.io) — deposit any amount of ETH and stake it in a single click. Your assets are routed through a [MetaVault](/docs/vaults/meta-vaults) that distributes them across the best-performing Sub-vaults — currently just the [Genesis Vault ↗](https://app.stakewise.io/vault/mainnet/0xac0f906e433d58fa868f936e8a43230473652885), with more to come. -When staking, you'll automatically receive [osETH](/docs/ostoken/intro), which represents your staked assets plus accumulated rewards. osETH can be used [across DeFi to boost your yield](https://app.stakewise.io/ecosystem). +When staking, you'll automatically receive [osETH](/docs/ostoken/intro), which represents your staked assets plus accumulated rewards. osETH can be used [across DeFi to boost your yield ↗](https://app.stakewise.io/ecosystem). StakeWise simple staking explanation diagram @@ -20,7 +20,7 @@ Stake your ETH and start earning rewards immediately. Staking flow explanation diagram -1. Open [app.stakewise.io](https://app.stakewise.io) and connect your wallet. +1. Open [app.stakewise.io ↗](https://app.stakewise.io) and connect your wallet. 2. Select the **Stake** tab and enter the amount of ETH you want to stake. 3. Review the details. 4. Click **Stake** and confirm the transaction in your wallet. @@ -38,13 +38,13 @@ Once you have osETH in your wallet, you can optionally [Boost](/staker/boost) yo Unstaking is just as simple — convert your osETH back to ETH directly in the StakeWise App whenever you want. -osETH can only be **minted** or **burned** — staking mints new osETH, and unstaking burns it to release the underlying ETH. osETH bought on a DEX isn't tied to any staking position, so it won't appear in the **Unstake** tab. To convert market-bought osETH back to ETH, swap it on the [Swap page](https://app.stakewise.io/swap) of the StakeWise App or sell it on a DEX. +osETH can only be **minted** or **burned** — staking mints new osETH, and unstaking burns it to release the underlying ETH. osETH bought on a DEX isn't tied to any staking position, so it won't appear in the **Unstake** tab. To convert market-bought osETH back to ETH, swap it on the [Swap page ↗](https://app.stakewise.io/swap) of the StakeWise App or sell it on a DEX. Before unstaking, make sure the amount of osETH you want to unstake is in your wallet. If you have an active Boost position, switch to the **Unboost** tab and exit it first. Unstaking flow explanation diagram -1. Open [app.stakewise.io](https://app.stakewise.io) and connect your wallet. +1. Open [app.stakewise.io ↗](https://app.stakewise.io) and connect your wallet. 2. Click the **flip** button flip button icon to switch from staking to unstaking mode. 3. Select the **Unstake** tab and enter the amount of osETH you want to convert back to ETH. 4. Review the details. diff --git a/staker/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx b/staker/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx index 2f3681be..1b6a2ed4 100644 --- a/staker/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx +++ b/staker/stakewise-v2/01-migrate-to-stakewise-v3-on-ethereum.mdx @@ -4,14 +4,14 @@ sidebar_position: 1 description: "Step-by-step guide to migrate your stake from StakeWise V2 Pool to StakeWise V3 on Ethereum." --- -# Migrate to StakeWise V3 on Ethereum +import Image from '@theme/IdealImage'; -

Migrating your stake in the legacy StakeWise Pool to StakeWise V3

+# Migrate to StakeWise V3 on Ethereum 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://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. +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] @@ -20,46 +20,38 @@ You must have sETH2 and/or rETH2 tokens in your wallet to be able to migrate to ## Make sure you are on the right website -Scammers have attempted to lull users into connecting their wallets to malicious interfaces by replicating the StakeWise V3 interface and creating domain names similar to [stakewise.io](https://stakewise.io/). +Scammers have attempted to lull users into connecting their wallets to malicious interfaces by replicating the StakeWise V3 interface and creating domain names similar to [stakewise.io ↗](https://stakewise.io/). -Before you proceed, make sure you are connecting your wallet to an interface located at [app.stakewise.io](https://app.stakewise.io/), which is the only official StakeWise V3 interface. +Before you proceed, make sure you are connecting your wallet to an interface located at [app.stakewise.io ↗](https://app.stakewise.io/), which is the only official StakeWise V3 interface. ## Connect your wallet -Once you land on the StakeWise V3 interface, press the `Connect Wallet` button at the top-right-hand side of your screen and select the type of wallet you want to connect with. +Once you land on the StakeWise V3 interface, press the `Connect Wallet` button at the top right-hand side of your screen and select the type of wallet you want to connect with. -![Step 1](./img/migrate-v3-1.avif) +Connect your wallet -Remember that in order to migrate, you will need to connect with the wallet that holds the sETH2 and rETH2 tokens i.e. your stake in StakeWise V2. +Remember that in order to migrate, you will need to connect with the wallet that holds the sETH2 and rETH2 tokens, i.e. your stake in StakeWise V2. ## Navigate to the Migrate interface Once your wallet is connected to the StakeWise V3 interface, you will find the Migrate section at the top of your screen. -![Step 2](./img/migrate-v3-2.avif) - -Press on the `Migrate` button to open the Migrate interface. You should see a floating module with blank fields for the amount of sETH2 and rETH2 tokens you would like to migrate to StakeWise V3. - -![Step 3](./img/migrate-v3-3.avif) - -## Enter the amount you will migrate - -For every StakeWise token that you own, you will be prompted to enter the amount you would like to migrate to StakeWise V3. +Navigate to the Migrate interface -sETH2 and rETH2 tokens represent ETH staked in StakeWise V2 at a 1:1 ratio. For every unit of a token you choose to migrate, a corresponding amount of your staked ETH will migrate to StakeWise V3. +Press the `Migrate` button to open the Migrate interface. You should see a floating module with blank fields for the amount of sETH2 and rETH2 tokens you would like to migrate to StakeWise V3. -![Step 4](./img/migrate-v3-4.avif) +Open the Migrate interface -You can use `Max` buttons to insert the total amount of tokens you hold in your wallet for migration. +## Enter the amount and confirm the transaction -## Confirm the transaction +For every StakeWise token that you own, you will be prompted to enter the amount you would like to migrate to StakeWise V3. sETH2 and rETH2 tokens represent ETH staked in StakeWise V2 at a 1:1 ratio. For every unit of a token you choose to migrate, a corresponding amount of your staked ETH will migrate to StakeWise V3. You can use `Max` buttons to insert the total amount of tokens you hold in your wallet. -Once you've selected the amounts of sETH2 and rETH2 tokens you would like to migrate to StakeWise V3, press on the Migrate button. Confirm the transaction in your wallet to initiate the migration. +Once you've entered the amounts, press the `Migrate` button and confirm the transaction in your wallet to initiate the migration. -![Step 5](./img/migrate-v3-5.avif) +Confirm the transaction -Once the transaction is finalized, you should see the total amount of tokens you chose to migrate as ETH staked in the ["Genesis"](https://app.stakewise.io/vault/0xAC0F906E433d58FA868F936E8A43230473652885) Vault on StakeWise V3. +Once the transaction is finalized, you should see the total amount of tokens you chose to migrate as ETH staked in the [Genesis Vault ↗](https://app.stakewise.io/vault/0xAC0F906E433d58FA868F936E8A43230473652885) on StakeWise V3. -![Step 6](./img/migrate-v3-6.avif) +Migration complete This step marks the successful completion of the migration. Congratulations! 🎉 diff --git a/staker/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx b/staker/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx index 2f9c70db..deb7db46 100644 --- a/staker/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx +++ b/staker/stakewise-v2/02-migrate-to-stakewise-v3-on-gnosis-chain.mdx @@ -4,14 +4,14 @@ sidebar_position: 2 description: "Step-by-step guide to migrate your stake from StakeWise V2 Pool to StakeWise V3 on Gnosis Chain." --- -# Migrate to StakeWise V3 on Gnosis Chain +import Image from '@theme/IdealImage'; -

Migrating your stake in the legacy StakeWise Pool to StakeWise V3

+# Migrate to StakeWise V3 on Gnosis Chain 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://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. +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] @@ -20,52 +20,44 @@ You must have sGNO and/or rGNO tokens in your wallet to be able to migrate to St ## Make sure you are on the right website -Scammers have attempted to lull users into connecting their wallets to malicious interfaces by replicating the StakeWise V3 interface and creating domain names similar to [stakewise.io](https://stakewise.io/). +Scammers have attempted to lull users into connecting their wallets to malicious interfaces by replicating the StakeWise V3 interface and creating domain names similar to [stakewise.io ↗](https://stakewise.io/). -Before you proceed, make sure you are connecting your wallet to an interface located at [app.stakewise.io](https://app.stakewise.io/), which is the only official StakeWise V3 interface. +Before you proceed, make sure you are connecting your wallet to an interface located at [app.stakewise.io ↗](https://app.stakewise.io/), which is the only official StakeWise V3 interface. ## Connect your wallet -Once you land on the StakeWise V3 interface, press the `Connect Wallet` button at the top-right-hand side of your screen and select the type of wallet you want to connect with. +Once you land on the StakeWise V3 interface, press the `Connect Wallet` button at the top right-hand side of your screen and select the type of wallet you want to connect with. -![Step 1](./img/migrate-v3-1.avif) +Connect your wallet -Remember that in order to migrate, you will need to connect with the wallet that holds the sGNO and rGNO tokens i.e. your stake in StakeWise V2. +Remember that in order to migrate, you will need to connect with the wallet that holds the sGNO and rGNO tokens, i.e. your stake in StakeWise V2. ## Switch network to Gnosis Chain -After connecting your wallet, select `Gnosis Chain` network at the top-right-hand side of the interface. +After connecting your wallet, select `Gnosis Chain` network at the top right-hand side of the interface. -![Step 7](./img/migrate-v3-7.webp) +Switch network to Gnosis Chain ## Navigate to the Migrate interface Once your wallet is connected to the StakeWise V3 interface, you will find the Migrate section at the top of your screen. -![Step 8](./img/migrate-v3-8.webp) - -Press on the `Migrate` button to open the Migrate interface. You should see a floating module with blank fields for the amount of sGNO and rGNO tokens you would like to migrate to StakeWise V3. - -![Step 9](./img/migrate-v3-9.webp) - -## Enter the amount you will migrate - -For every StakeWise token that you own, you will be prompted to enter the amount you would like to migrate to StakeWise V3 on Gnosis Chain. +Navigate to the Migrate interface -sGNO and rGNO tokens represent GNO staked in StakeWise V2 at a 1:1 ratio. For every unit of a token you choose to migrate, a corresponding amount of your staked GNO will migrate to StakeWise V3. +Press the `Migrate` button to open the Migrate interface. You should see a floating module with blank fields for the amount of sGNO and rGNO tokens you would like to migrate to StakeWise V3. -![Step 10](./img/migrate-v3-10.webp) +Open the Migrate interface -You can use `Max` buttons to insert the total amount of tokens you hold in your wallet for migration. +## Enter the amount and confirm the transaction -## Confirm the transaction +For every StakeWise token that you own, you will be prompted to enter the amount you would like to migrate to StakeWise V3 on Gnosis Chain. sGNO and rGNO tokens represent GNO staked in StakeWise V2 at a 1:1 ratio. For every unit of a token you choose to migrate, a corresponding amount of your staked GNO will migrate to StakeWise V3. You can use `Max` buttons to insert the total amount of tokens you hold in your wallet. -Once you've selected the amounts of sGNO and rGNO tokens you would like to migrate to StakeWise V3, press on the `Migrate` button. Confirm the transaction in your wallet to initiate the migration. +Once you've entered the amounts, press the `Migrate` button and confirm the transaction in your wallet to initiate the migration. -![Step 11](./img/migrate-v3-11.webp) +Confirm the transaction -Once the transaction is finalized, you should see the total amount of tokens you chose to migrate as ETH staked in the [Genesis Vault](https://app.stakewise.io/vault/gnosis/0x4b4406ed8659d03423490d8b62a1639206da0a7a) on StakeWise V3 on Gnosis Chain. +Once the transaction is finalized, you should see the total amount of tokens you chose to migrate as GNO staked in the [Genesis Vault ↗](https://app.stakewise.io/vault/gnosis/0x4b4406ed8659d03423490d8b62a1639206da0a7a) on StakeWise V3 on Gnosis Chain. -![Step 12](./img/migrate-v3-12.webp) +Migration complete This step marks the successful completion of the migration. Congratulations! cup diff --git a/staker/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx b/staker/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx index 947cd2f5..68ab2ee2 100644 --- a/staker/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx +++ b/staker/stakewise-v2/03-change-solo-withdrawal-credentials-to-0x01-address.mdx @@ -59,7 +59,7 @@ To find the right guide for you, choose your operating system. ## 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 + 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] The version of the `staking_deposit-cli` is based on the original cli by the Ethereum Foundation which was modified by StakeWise. ::: @@ -99,7 +99,7 @@ To find the right guide for you, choose your operating system. ## Broadcast the `.json` File Message to the Network - 1. Head to the [Beacon Chain Explorer](https://beaconcha.in/tools/broadcast) website + 1. Head to the [Beacon Chain Explorer ↗](https://beaconcha.in/tools/broadcast) website 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! @@ -144,7 +144,7 @@ To find the right guide for you, choose your operating system. ## 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. 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 1. 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. @@ -163,7 +163,7 @@ 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). + 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 @@ -216,7 +216,7 @@ To find the right guide for you, choose your operating system. ## Broadcast the `.json` File Message to the Network - 1. Head to the [**Beacon Chain Explorer**](https://beaconcha.in/tools/broadcast) website + 1. Head to the [**Beacon Chain Explorer** ↗](https://beaconcha.in/tools/broadcast) website 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! diff --git a/staker/stakewise-v2/04-exit-solo-validator.mdx b/staker/stakewise-v2/04-exit-solo-validator.mdx index 5890f7f7..88009a7f 100644 --- a/staker/stakewise-v2/04-exit-solo-validator.mdx +++ b/staker/stakewise-v2/04-exit-solo-validator.mdx @@ -14,7 +14,7 @@ Note that you must [**rotate your Solo validator withdrawal credentials**](./03- Validator exits from StakeWise Solo are handled manually on an on-request basis. In order to exit your Solo validator and unstake from StakeWise Solo, please perform the following steps: -1. Go to [**MyEtherWallet Sign**](https://www.myetherwallet.com/wallet/access) page and choose the best way to **connect the wallet you use to pay fees for your Solo validators**. Completing the next steps will be useless unless performed with this wallet. +1. Go to [**MyEtherWallet Sign** ↗](https://www.myetherwallet.com/wallet/access) page and choose the best way to **connect the wallet you use to pay fees for your Solo validators**. Completing the next steps will be useless unless performed with this wallet. 2. Enter the following message into the Sign field, inserting the indeces of validators you want to exit: > I request an exit for the validators with the following index / indeces: @@ -28,7 +28,7 @@ Validator exits from StakeWise Solo are handled manually on an on-request basis. You will receive confirmation of the StakeWise team processing your request within 24 hours of sending the email. Your exit request will be processed within 48 hours of the email receipt, also acknowledged via email. -After that, the timing of the validator exit will depend on the length of the [Ethereum validator exit queue](https://www.rated.network/overview?timeWindow=all&network=mainnet&rewardsMetric=average). +After that, the timing of the validator exit will depend on the length of the [Ethereum validator exit queue ↗](https://www.rated.network/overview?timeWindow=all&network=mainnet&rewardsMetric=average). :::custom-tips[Complete] You are now aware of how to unstake from StakeWise Solo. diff --git a/staker/stakewise-v2/img/ethereum/confirm_the_transaction.png b/staker/stakewise-v2/img/ethereum/confirm_the_transaction.png new file mode 100644 index 00000000..37942da4 Binary files /dev/null and b/staker/stakewise-v2/img/ethereum/confirm_the_transaction.png differ diff --git a/staker/stakewise-v2/img/ethereum/connect_your_wallet.png b/staker/stakewise-v2/img/ethereum/connect_your_wallet.png new file mode 100644 index 00000000..fd62af2e Binary files /dev/null and b/staker/stakewise-v2/img/ethereum/connect_your_wallet.png differ diff --git a/staker/stakewise-v2/img/ethereum/migration_complete.png b/staker/stakewise-v2/img/ethereum/migration_complete.png new file mode 100644 index 00000000..800dcc56 Binary files /dev/null and b/staker/stakewise-v2/img/ethereum/migration_complete.png differ diff --git a/staker/stakewise-v2/img/ethereum/navigate_to_the_migrate_interface.png b/staker/stakewise-v2/img/ethereum/navigate_to_the_migrate_interface.png new file mode 100644 index 00000000..8c200245 Binary files /dev/null and b/staker/stakewise-v2/img/ethereum/navigate_to_the_migrate_interface.png differ diff --git a/staker/stakewise-v2/img/ethereum/open_migrate_interface.png b/staker/stakewise-v2/img/ethereum/open_migrate_interface.png new file mode 100644 index 00000000..68b9692c Binary files /dev/null and b/staker/stakewise-v2/img/ethereum/open_migrate_interface.png differ diff --git a/staker/stakewise-v2/img/gnosis/confirm_the_transaction.png b/staker/stakewise-v2/img/gnosis/confirm_the_transaction.png new file mode 100644 index 00000000..505d77ac Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/confirm_the_transaction.png differ diff --git a/staker/stakewise-v2/img/gnosis/connect_your_wallet.png b/staker/stakewise-v2/img/gnosis/connect_your_wallet.png new file mode 100644 index 00000000..fd62af2e Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/connect_your_wallet.png differ diff --git a/staker/stakewise-v2/img/gnosis/migration_complete.png b/staker/stakewise-v2/img/gnosis/migration_complete.png new file mode 100644 index 00000000..11de35a5 Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/migration_complete.png differ diff --git a/staker/stakewise-v2/img/gnosis/navigate_to_the_migrate_interface.png b/staker/stakewise-v2/img/gnosis/navigate_to_the_migrate_interface.png new file mode 100644 index 00000000..66a9c18b Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/navigate_to_the_migrate_interface.png differ diff --git a/staker/stakewise-v2/img/gnosis/open_migrate_interface.png b/staker/stakewise-v2/img/gnosis/open_migrate_interface.png new file mode 100644 index 00000000..617b0336 Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/open_migrate_interface.png differ diff --git a/staker/stakewise-v2/img/gnosis/switch_network_to_gnosis_chain.png b/staker/stakewise-v2/img/gnosis/switch_network_to_gnosis_chain.png new file mode 100644 index 00000000..a9485ad6 Binary files /dev/null and b/staker/stakewise-v2/img/gnosis/switch_network_to_gnosis_chain.png differ diff --git a/staker/stakewise-v2/img/migrate-v3-1.avif b/staker/stakewise-v2/img/migrate-v3-1.avif deleted file mode 100644 index 1a19c489..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-1.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-10.webp b/staker/stakewise-v2/img/migrate-v3-10.webp deleted file mode 100644 index a14b68ad..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-10.webp and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-11.webp b/staker/stakewise-v2/img/migrate-v3-11.webp deleted file mode 100644 index 55eba0a1..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-11.webp and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-12.webp b/staker/stakewise-v2/img/migrate-v3-12.webp deleted file mode 100644 index 551f32a1..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-12.webp and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-2.avif b/staker/stakewise-v2/img/migrate-v3-2.avif deleted file mode 100644 index 939a55da..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-2.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-3.avif b/staker/stakewise-v2/img/migrate-v3-3.avif deleted file mode 100644 index 6948a54a..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-3.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-4.avif b/staker/stakewise-v2/img/migrate-v3-4.avif deleted file mode 100644 index 882559ce..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-4.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-5.avif b/staker/stakewise-v2/img/migrate-v3-5.avif deleted file mode 100644 index 0244e465..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-5.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-6.avif b/staker/stakewise-v2/img/migrate-v3-6.avif deleted file mode 100644 index 5418fc30..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-6.avif and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-7.webp b/staker/stakewise-v2/img/migrate-v3-7.webp deleted file mode 100644 index 03e3ac9f..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-7.webp and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-8.webp b/staker/stakewise-v2/img/migrate-v3-8.webp deleted file mode 100644 index 0a7affc8..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-8.webp and /dev/null differ diff --git a/staker/stakewise-v2/img/migrate-v3-9.webp b/staker/stakewise-v2/img/migrate-v3-9.webp deleted file mode 100644 index 918e53c2..00000000 Binary files a/staker/stakewise-v2/img/migrate-v3-9.webp and /dev/null differ diff --git a/staker/vault-staking.mdx b/staker/vault-staking.mdx index ed5ff225..45e5a03d 100644 --- a/staker/vault-staking.mdx +++ b/staker/vault-staking.mdx @@ -20,7 +20,7 @@ Pick a Vault that matches your preferences and start staking in just a few steps Staking flow with a Vault explanation diagram -1. Open [app.stakewise.io](https://app.stakewise.io) and connect your wallet. +1. Open [app.stakewise.io ↗](https://app.stakewise.io) and connect your wallet. 2. Navigate to **Vaults** and browse the available options. 3. Select a Vault and review its details, including MEV strategy, TVL, APY, performance, and staking fee. 4. Click the **(+)** button next to **Staked ETH**, enter the amount of ETH you want to stake, and confirm the transaction in your wallet. diff --git a/static/icons/glossary/automatic-unboost.png b/static/icons/glossary/automatic-unboost.png new file mode 100644 index 00000000..b1197c4c Binary files /dev/null and b/static/icons/glossary/automatic-unboost.png differ diff --git a/static/icons/glossary/blocklist-vault.png b/static/icons/glossary/blocklist-vault.png new file mode 100644 index 00000000..94b6e472 Binary files /dev/null and b/static/icons/glossary/blocklist-vault.png differ diff --git a/static/icons/glossary/boost.png b/static/icons/glossary/boost.png new file mode 100644 index 00000000..9ab702b8 Binary files /dev/null and b/static/icons/glossary/boost.png differ diff --git a/static/icons/glossary/burning.png b/static/icons/glossary/burning.png new file mode 100644 index 00000000..b58a9a55 Binary files /dev/null and b/static/icons/glossary/burning.png differ diff --git a/static/icons/glossary/compound-validator.png b/static/icons/glossary/compound-validator.png new file mode 100644 index 00000000..60efbd99 Binary files /dev/null and b/static/icons/glossary/compound-validator.png differ diff --git a/static/icons/glossary/consolidation.png b/static/icons/glossary/consolidation.png new file mode 100644 index 00000000..ee5d7b39 Binary files /dev/null and b/static/icons/glossary/consolidation.png differ diff --git a/static/icons/glossary/dao-approved-vault.png b/static/icons/glossary/dao-approved-vault.png new file mode 100644 index 00000000..d7cda65e Binary files /dev/null and b/static/icons/glossary/dao-approved-vault.png differ diff --git a/static/icons/glossary/erc20-vault.png b/static/icons/glossary/erc20-vault.png new file mode 100644 index 00000000..506b8b50 Binary files /dev/null and b/static/icons/glossary/erc20-vault.png differ diff --git a/static/icons/glossary/exit-queue-ticket.png b/static/icons/glossary/exit-queue-ticket.png new file mode 100644 index 00000000..9890381e Binary files /dev/null and b/static/icons/glossary/exit-queue-ticket.png differ diff --git a/static/icons/glossary/exit-queue.png b/static/icons/glossary/exit-queue.png new file mode 100644 index 00000000..e160125a Binary files /dev/null and b/static/icons/glossary/exit-queue.png differ diff --git a/static/icons/glossary/fee-recipient.png b/static/icons/glossary/fee-recipient.png new file mode 100644 index 00000000..74a5a21a Binary files /dev/null and b/static/icons/glossary/fee-recipient.png differ diff --git a/static/icons/glossary/harvest.png b/static/icons/glossary/harvest.png new file mode 100644 index 00000000..9e5f1fde Binary files /dev/null and b/static/icons/glossary/harvest.png differ diff --git a/static/icons/glossary/keeper.png b/static/icons/glossary/keeper.png new file mode 100644 index 00000000..732be19d Binary files /dev/null and b/static/icons/glossary/keeper.png differ diff --git a/static/icons/glossary/legacy-validator.png b/static/icons/glossary/legacy-validator.png new file mode 100644 index 00000000..97ec80a1 Binary files /dev/null and b/static/icons/glossary/legacy-validator.png differ diff --git a/static/icons/glossary/liquidation.png b/static/icons/glossary/liquidation.png new file mode 100644 index 00000000..1df22afb Binary files /dev/null and b/static/icons/glossary/liquidation.png differ diff --git a/static/icons/glossary/ltv.png b/static/icons/glossary/ltv.png new file mode 100644 index 00000000..ac195029 Binary files /dev/null and b/static/icons/glossary/ltv.png differ diff --git a/static/icons/glossary/metavault.png b/static/icons/glossary/metavault.png new file mode 100644 index 00000000..79c09f91 Binary files /dev/null and b/static/icons/glossary/metavault.png differ diff --git a/static/icons/glossary/minting.png b/static/icons/glossary/minting.png new file mode 100644 index 00000000..813e688a Binary files /dev/null and b/static/icons/glossary/minting.png differ diff --git a/static/icons/glossary/operator-service.png b/static/icons/glossary/operator-service.png new file mode 100644 index 00000000..cd65d702 Binary files /dev/null and b/static/icons/glossary/operator-service.png differ diff --git a/static/icons/glossary/oracle-network.png b/static/icons/glossary/oracle-network.png new file mode 100644 index 00000000..2d469262 Binary files /dev/null and b/static/icons/glossary/oracle-network.png differ diff --git a/static/icons/glossary/oseth.png b/static/icons/glossary/oseth.png new file mode 100644 index 00000000..f31f07ea Binary files /dev/null and b/static/icons/glossary/oseth.png differ diff --git a/static/icons/glossary/osgno.png b/static/icons/glossary/osgno.png new file mode 100644 index 00000000..c33659e1 Binary files /dev/null and b/static/icons/glossary/osgno.png differ diff --git a/static/icons/glossary/ostoken-exchange-rate.png b/static/icons/glossary/ostoken-exchange-rate.png new file mode 100644 index 00000000..6d9020de Binary files /dev/null and b/static/icons/glossary/ostoken-exchange-rate.png differ diff --git a/static/icons/glossary/ostoken-fee.png b/static/icons/glossary/ostoken-fee.png new file mode 100644 index 00000000..fd24ce44 Binary files /dev/null and b/static/icons/glossary/ostoken-fee.png differ diff --git a/static/icons/glossary/ostoken-position.png b/static/icons/glossary/ostoken-position.png new file mode 100644 index 00000000..f7940560 Binary files /dev/null and b/static/icons/glossary/ostoken-position.png differ diff --git a/static/icons/glossary/ostoken.png b/static/icons/glossary/ostoken.png new file mode 100644 index 00000000..b95bf001 Binary files /dev/null and b/static/icons/glossary/ostoken.png differ diff --git a/static/icons/glossary/own-escrow.png b/static/icons/glossary/own-escrow.png new file mode 100644 index 00000000..1c19949c Binary files /dev/null and b/static/icons/glossary/own-escrow.png differ diff --git a/static/icons/glossary/partial-withdrawal.png b/static/icons/glossary/partial-withdrawal.png new file mode 100644 index 00000000..7f2b7909 Binary files /dev/null and b/static/icons/glossary/partial-withdrawal.png differ diff --git a/static/icons/glossary/private-vault.png b/static/icons/glossary/private-vault.png new file mode 100644 index 00000000..4ce62f5e Binary files /dev/null and b/static/icons/glossary/private-vault.png differ diff --git a/static/icons/glossary/repricing-token.png b/static/icons/glossary/repricing-token.png new file mode 100644 index 00000000..3ca91a91 Binary files /dev/null and b/static/icons/glossary/repricing-token.png differ diff --git a/static/icons/glossary/smoothing-pool.png b/static/icons/glossary/smoothing-pool.png new file mode 100644 index 00000000..5bff23d0 Binary files /dev/null and b/static/icons/glossary/smoothing-pool.png differ diff --git a/static/icons/glossary/standard-vault.png b/static/icons/glossary/standard-vault.png new file mode 100644 index 00000000..5875528c Binary files /dev/null and b/static/icons/glossary/standard-vault.png differ diff --git a/static/icons/glossary/swise.png b/static/icons/glossary/swise.png new file mode 100644 index 00000000..ada4082d Binary files /dev/null and b/static/icons/glossary/swise.png differ diff --git a/static/icons/glossary/unbonded-eth.png b/static/icons/glossary/unbonded-eth.png new file mode 100644 index 00000000..e5c74e37 Binary files /dev/null and b/static/icons/glossary/unbonded-eth.png differ diff --git a/static/icons/glossary/unboost-queue.png b/static/icons/glossary/unboost-queue.png new file mode 100644 index 00000000..9a0ee616 Binary files /dev/null and b/static/icons/glossary/unboost-queue.png differ diff --git a/static/icons/glossary/validators-manager.png b/static/icons/glossary/validators-manager.png new file mode 100644 index 00000000..706006af Binary files /dev/null and b/static/icons/glossary/validators-manager.png differ diff --git a/static/icons/glossary/vault-admin.png b/static/icons/glossary/vault-admin.png new file mode 100644 index 00000000..a9855c60 Binary files /dev/null and b/static/icons/glossary/vault-admin.png differ diff --git a/static/icons/glossary/vault-capacity.png b/static/icons/glossary/vault-capacity.png new file mode 100644 index 00000000..3da914fd Binary files /dev/null and b/static/icons/glossary/vault-capacity.png differ diff --git a/static/icons/glossary/vault-fee-claimer.png b/static/icons/glossary/vault-fee-claimer.png new file mode 100644 index 00000000..7b2d4a0e Binary files /dev/null and b/static/icons/glossary/vault-fee-claimer.png differ diff --git a/static/icons/glossary/vault-fee.png b/static/icons/glossary/vault-fee.png new file mode 100644 index 00000000..8c46ab2f Binary files /dev/null and b/static/icons/glossary/vault-fee.png differ diff --git a/static/icons/glossary/vault-operator.png b/static/icons/glossary/vault-operator.png new file mode 100644 index 00000000..53452002 Binary files /dev/null and b/static/icons/glossary/vault-operator.png differ diff --git a/static/icons/glossary/vault-shares.png b/static/icons/glossary/vault-shares.png new file mode 100644 index 00000000..24755f15 Binary files /dev/null and b/static/icons/glossary/vault-shares.png differ diff --git a/static/icons/glossary/vault.png b/static/icons/glossary/vault.png new file mode 100644 index 00000000..f7aed5f6 Binary files /dev/null and b/static/icons/glossary/vault.png differ diff --git a/static/icons/glossary/whitelist-blocklist-manager.png b/static/icons/glossary/whitelist-blocklist-manager.png new file mode 100644 index 00000000..ba3cff35 Binary files /dev/null and b/static/icons/glossary/whitelist-blocklist-manager.png differ diff --git a/static/icons/risks/boost.png b/static/icons/risks/boost.png new file mode 100644 index 00000000..e8bee1a7 Binary files /dev/null and b/static/icons/risks/boost.png differ diff --git a/static/icons/risks/oseth-depeg.png b/static/icons/risks/oseth-depeg.png new file mode 100644 index 00000000..7ba781ee Binary files /dev/null and b/static/icons/risks/oseth-depeg.png differ diff --git a/static/icons/risks/smart-contract.png b/static/icons/risks/smart-contract.png new file mode 100644 index 00000000..45ddb856 Binary files /dev/null and b/static/icons/risks/smart-contract.png differ diff --git a/static/icons/risks/vault-performance.png b/static/icons/risks/vault-performance.png new file mode 100644 index 00000000..f6c58cee Binary files /dev/null and b/static/icons/risks/vault-performance.png differ