StakeWise V3 enables you to launch your own staking Pool, called Vault, and keep the stake in the Vault liquid with osETH, a liquid staking token of StakeWise.
Vaults architecture can be used by solo stakers to access liquid staking, and by individuals and organizations to stake on their terms and offer liquid staking to others.
Use case
Recommended settings
Liquid solo staking
100K ETH capacity, 0% fee, no Vault token, Private Vault, Smoothing Pool enabled
Community staking pool
Capacity and fee according to the business plan, no Vault token, Public Vault, Smoothing Pool enabled
Staking service with own LST
Capacity and fee according to the business plan, Vault token, Public Vault, Smoothing Pool enabled/disabled based on compliance
Liquid staking offered by a node operator
Capacity and fee according to the business plan, no Vault token, Private Vault for each customer, Smoothing Pool enabled/disabled based on compliance need
Below you can explore the guides for launching and running a Vault with StakeWise.
Creating your Vault
A Vault is a customizable smart contract that can be deployed by anyone to stake their own capital and/or offer staking to others, all in a non-custodial way.
Each Vault is isolated from others and relies on its own set of validators to produce rewards on the consensus layer. However, a Vault may participate in MEV smoothing to avoid volatility in the execution layer earnings.
Staked ETH in any Vault can be made liquid by minting osETH, a liquid staking token.
Head to the Operate page in the StakeWise dApp and connect your wallet.
Press on the Create Vault button.
Configure your Vault by setting its parameters according to your needs and press Continue. These parameters cannot be changed in the future.
Choose whether you would like to join a Smoothing Pool or collect only Personal MEV earnings and press Continue. This choice cannot be changed in the future.
Add branding to your Vault by specifying the name, logo, and description of the Vault and press Continue.
Review your choices in the Summary section and press Create Vault to deploy your Vault.
Configuring StakeWise Operator Service
Each Vault requires a node operator, or set of node operators, to stake the ETH deposited into the Vault, with each operator required to run StakeWise Operator Service. The service is designed to run seamlessly alongside any node set-up, giving operators the freedom to run their preferred execution/consensus clients, MEV relay, and distributed validator technology. The Operator Service is responsible for the creation of validators and the distribution of validator exit messages to the Oracle Network, enabling the automatic exiting of validators when required.
Before validators can be created within a Vault, a deposit data file must be uploaded to the Vault. This file contains the pre-generated public validator keys from the operator(s), with the order of the validator keys in the file determining the order in which validators are created. A new deposit data file can be uploaded at any point in time to override any unused validator keys via the Vault settings, allowing new node operators to be easily added to the operator set.
Check out the full guide to getting your node connected to your Vault with StakeWise Operator Service and the Vault deposit data file. For more information on the role of Operator Service within StakeWise V3, visit here.
Managing your Vault
Some parameters of your Vault, like branding and whitelist, are configurable even after the Vault was created.