Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 0 additions & 12 deletions docs/docs/stakewise-protocol/governance-swise-token.mdx

This file was deleted.

13 changes: 6 additions & 7 deletions docs/docs/stakewise-protocol/intro.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -5,14 +5,13 @@ description: Learn how StakeWise Protocol enables decentralized liquid staking o

# The StakeWise Protocol

## Introduction
StakeWise is a liquid staking protocol for Ethereum and Gnosis Chain, designed to make staking more flexible, secure, and accessible. Anyone can start staking. There is no minimum ETH/GNO deposit, no validator node to run, and no technical setup required.

StakeWise is a liquid staking protocol for Ethereum, designed to make staking more flexible, secure, and accessible.
Instead of one large staking pool, StakeWise is built around [Vaults](/docs/vaults/intro): permissionless, customizable, and non-custodial staking pools deployed by various operators. Vaults already secure hundreds of millions of US dollars' worth of staked assets, powering solutions from [MetaMask ↗](https://blog.stakewise.io/caseStudy/how-metamask-launched-pooled-staking-with-stakewise), [Chorus One ↗](https://blog.stakewise.io/caseStudy/how-chorus-one-launched-retail-staking-with-stakewise), [Blockchain.com ↗](https://www.blockchain.com/), [Ledger Live ↗](https://www.ledger.com/ledger-live), and others.

Rather than consisting of one large staking pool, StakeWise has a network of permissionless, customizable, and non-custodial staking pools deployed by various service providers, allowing individuals and organizations to pick which nodes will stake their ETH, helping them find the most suitable staking arrangement. All pools offer on-demand liquidity and DeFi integrations for users' stake via osToken, providing the flexibility to get the token only when needed.
Stakers choose the exact terms on which they stake, and can mint [osToken](/docs/ostoken/intro), StakeWise's liquid staking token, to put their stake to work across the [DeFi ecosystem ↗](https://app.stakewise.io/ecosystem) and earn more on top of their staking rewards. StakeWise also develops strategies to increase rewards, such as [Boost](/docs/vaults/boost) on Ethereum, with more coming soon.

The protocol is implemented as a mix of both upgradable (via dual governance) smart contracts that must keep up with the changes in Ethereum's Proof-of-Stake specification, and persistent, non-upgradable smart contracts designed to prioritize security and self-custody, and to function without centralized intermediaries who may selectively restrict access to the service.
The protocol is implemented with two types of smart contracts:

StakeWise was formally introduced with the release of its [Litepaper in 2022 ↗](https://www.stakewise.io/stakewise-v3.pdf), which set out the vision for a modular staking protocol designed to counter centralization risks and expand user choice. Since then, the protocol has continued to evolve to embody the core ethos of Ethereum and DeFi, specifically the non-custodial, trustless nature that allows self-sovereignty to truly thrive.

Most users lack either the technical expertise to run validator nodes or the 32 ETH required to stake. StakeWise addresses this by providing an essential base layer that lowers both technical and capital barriers to ETH staking.
- **Upgradable contracts** — the Vaults themselves — keep the protocol current with Ethereum's proof-of-stake specification. Upgrades are never automatic: a new Vault version must first be approved through StakeWise DAO governance, and it applies to a Vault only after its [Admin](/docs/vaults/configuration#admin) explicitly [opts in](/docs/vaults/technical-architecture#upgrade-flexibility).
- **Non-upgradable contracts** — the shared infrastructure every Vault plugs into, such as the Vault registry, the Keeper, and osToken accounting — have no upgrade path: once deployed on-chain, their code can never be changed. The same rules therefore apply to every Vault, and no intermediary can rewrite them or selectively restrict access to the service.
Loading