StakeWise

• Name: StakeWise
• URL: https://stakewise.io/
• Category: liquid staking infrastructure / vault-based staking control plane / operator tooling platform
• Tags: ethereum-ecosystem
• Summary: StakeWise is liquid staking infrastructure built around configurable vaults. The point is not the LST ticker. It is stake routing, operator mix, and liquid-claim policy exposed as product choices instead of one monolithic validator set.
• What it does:
  • Lets users stake through non-custodial vaults with configurable parameters rather than one global pooled product
  • Issues liquid claims such as osETH and osGNO against staked positions, using overcollateralization to buffer validator underperformance and penalties
  • Provides operator software and tooling for validator lifecycle work around deposits, rewards, and exits
  • Supports downstream integrators that want to package staking exposure, vault routing, or staking products on top of StakeWise infrastructure
  • Exposes staking as reusable infrastructure where vault design and default routing matter as much as the token wrapper
• Key claims:
  • The official site and docs position StakeWise V3 as vault-based staking infrastructure rather than only a branded liquid staking pool, which is the main reason to keep the note
  • The docs say vaults are non-custodial and configurable, with operator setup and product design varying by vault rather than being fixed protocol-wide
  • StakeWise documents osToken liquid claims such as osETH and osGNO as overcollateralized staking derivatives meant to absorb validator underperformance and slashing risk before losses reach the liquid token holder
  • The operator docs and public repositories show that StakeWise is selling operator workflow and validator-management software alongside the vault model, not just an LST frontend
  • The institutional page reinforces that the product is meant to be embedded or packaged by other entities, which makes governance over vault defaults and operator selection more important than the usual just another staking token framing
• Whitepaper: No canonical standalone StakeWise whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, documentation, and public operator/core repositories; see ../whitepapers/stakewise-primary-sources-2026-04-30.md.
• Sources:
  • https://stakewise.io/
  • https://stakewise.io/institution
  • https://docs.stakewise.io/
  • https://docs.stakewise.io/docs/overview
  • https://docs.stakewise.io/staker/introduction
  • https://docs.stakewise.io/operator/introduction
  • https://docs.stakewise.io/docs/ostoken/intro
  • https://docs.stakewise.io/contracts/networks/
  • https://docs.stakewise.io/contracts/audits
  • https://docs.stakewise.io/sdk/
  • https://raw.githubusercontent.com/stakewise/v3-core/master/README.md
  • https://raw.githubusercontent.com/stakewise/v3-operator/master/README.md

Internal linkages

• Company / operator boundary for the core development team, interface packaging, and institutional deployment shell: stakewise-labs.
• Best institutional liquid-staking contrast: liquid-collective. That note is more curated and partner-gated; StakeWise is the cleaner open vault-policy variant.
• Best operator-platform contrast: figment. Figment is the broader staking API and validator-operations stack; StakeWise is the more protocol-native vault layer.

Protocol / company boundary

• Keep this project note on the product and mechanism layer: vault types, osToken, operator choice inside vaults, validator lifecycle logic, MEV handling, and how stake-routing becomes a live control surface.
• Use stakewise-labs when the sharper question is who ships the main interface, sells the institution-facing deployment path, packages white-label staking, and maintains the ecosystem tooling partners are likely to inherit.
• That split matters because how do StakeWise vaults work? and which named team shapes the easiest way to deploy and distribute them? are related but not identical questions.

Control surface

• The contracts matter, but the real leverage sits in who creates the important vaults, which operators those vaults favor, which liquid claims downstream apps treat as default collateral, and how governance can change the surrounding vault and operator framework.

• The decentralization question is not whether the contracts are non-custodial. It is whether stake routing and product defaults quietly centralize around a small number of vault operators and integrators.

• One layer up, stakewise-labs matters because interface defaults, operator-service workflow, and white-label distribution can quietly shape which vaults and validator sets become the de facto institutional path.

• Last reviewed: 2026-08-10 UTC