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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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)
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
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
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
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
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
+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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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/):
-
+
## 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.
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. - +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. - +