Cowrie Research

stakewise-labs-primary-sources-2026-08-10

3 min read

StakeWise Labs primary-source snapshot

Fetched: 2026-08-10 UTC

1) StakeWise docs overview

Source: https://docs.stakewise.io/docs/overview

Selected excerpts from official materials:

StakeWise has several distinct areas that serve different purposes — here’s how to tell them apart.

StakeWise Protocol: A modular collection of smart contracts powering decentralized liquid staking on Ethereum and Gnosis Chain.

StakeWise Interface: A web interface that allows for easy interaction with the StakeWise protocol.

StakeWise DAO: A governance system for governing the StakeWise Protocol, enabled by the SWISE token.

StakeWise Labs: The core development team behind StakeWise Protocol and its ecosystem tools.

Why it matters:

  • This is the cleanest first-party evidence that StakeWise itself distinguishes the protocol from the interface, DAO, and Labs entity boundary.
  • The company split is therefore not just a naming preference; it is part of the project’s own explanatory taxonomy.

2) StakeWise institutional page

Source: https://stakewise.io/institution

Selected excerpts from official materials:

Enterprise-grade staking infrastructure

Launch your custom staking infrastructure with minimal engineering effort.

Deploy pool — Customize permissions, fees, and validator settings.

Choose infrastructure — Choose from our marketplace of operators or run your own.

Select UI — Deploy with our API or ready-to-use interface.

Why it matters:

  • The institutional page makes the company/operator shell visible: deployment packaging, operator-marketplace choice, and UI/API distribution sit above the protocol contracts themselves.
  • This is exactly the kind of named organization boundary the companies/ layer is supposed to preserve.

3) StakeWise operator introduction

Source: https://docs.stakewise.io/operator/introduction

Selected excerpts from official materials:

Anyone — from solo stakers to professional node operators and institutions managing thousands of ETH — can create a Vault via app.stakewise.io.

StakeWise infrastructure already powers staking solutions deployed by MetaMask and Chorus One.

Offer staking to others — Accept deposits and earn fees, or launch a white-label staking product powered by StakeWise smart contracts.

Both Regular and MetaVaults rely on the Operator Service to automate day-to-day Vault operations.

Why it matters:

  • These docs show the protocol being packaged as institution-facing infrastructure rather than only as neutral vault contracts.
  • The white-label and Operator Service language makes the operational and partner-distribution boundary analytically useful.

4) StakeWise homepage

Source: https://stakewise.io/

Selected excerpts from official materials:

Discover vaults curated by our partners and powered by StakeWise

Decentralized protection — Your stake is secured by a diverse validator network using DVT (Distributed Validator Technology) and proprietary ETH clients.

Built by proven experts … pioneered secure staking innovations like the Vault model.

Why it matters:

  • The homepage emphasizes partner-curated vault discovery and the broader branded staking shell rather than only bare protocol mechanics.
  • It reinforces that adoption flows through a named operator and interface layer.

5) StakeWise Protocol V3 repository README

Source: https://raw.githubusercontent.com/stakewise/v3-core/master/README.md

Selected excerpts from official materials:

The protocol includes customizable Vaults … an over-collateralized token system (osToken), validator lifecycle management, MEV capture and distribution, and governance controls.

The protocol follows a modular design with several key components … Vaults … Tokens … Keepers … MEV Escrows.

Why it matters:

  • The repository confirms the scope of the maintained software stack and shows how much implementation gravity still sits in StakeWise-maintained code.
  • Together with the institutional and operator docs, it supports a company note centered on interface, deployment, and operations rather than contract mechanics alone.

Notes

  • This pass was meant to support a company/entity split for the StakeWise Labs boundary above the StakeWise protocol note.
  • The useful distinction is between StakeWise as vault-and-token staking infrastructure and StakeWise Labs as the named team packaging the interface, institutional deployment path, and operator-service workflow.

Graph View