Lido's materials
Northstake's Staking Vault Manager (SVM) is built directly on Lido V3 stVaults. The pages below are the official Lido documentation relevant to our product, grouped so you can jump to the right reference quickly.
[!note] How Lido's terms map to ours
Lido calls our category of product a DeFi Wrapper: a pooled, tokenized staking product layered on top of a single stVault. Wherever Lido's docs say "DeFi Wrapper", read it as thevaults-wrappercontracts (Pool, Withdrawal Queue, Distributor, Strategy) that the SVM is built on.
Entry point: stVaults Documentation Center: the hub for all Lido V3 stVault documentation.
Building guides
How to create and ship a staking product on stVaults.
| Page | What it covers |
|---|---|
| Basic stVault | Creating and operating a single-owner stVault with optional stETH minting: the foundational layer every pooled product sits on. Covers the two-role model (Node Operator Manager + Vault Owner), funding, minting, and validator deposits. |
| Pooled staking product | Overview of the DeFi Wrapper toolkit for launching multi-user, tokenized staking products. Closest analogue to the SVM: start here for the big picture. |
| Roles & permissions | The three-layer access-control model: TimelockController governance, per-contract RBAC (Pool, Withdrawal Queue, Distributor, Dashboard), and the Emergency Committee. |
| Withdrawals | Operating the withdrawal queue (request → finalize → claim) plus liquidity management and finalizer gas compensation. |
| Custom strategy | Adding a yield strategy to a pool via the IStrategy / IStrategyFactory interfaces. Covers fresh deployment vs. upgrading an existing StvStETHPool; GGVStrategy is the reference implementation. |
| Disconnect guide | Gracefully shutting down a pooled product and returning remaining assets to users via Merkle distribution. (Irreversible: affects all pool users.) |
Operational & management guides
Day-to-day running, monitoring, and exit of a stVault.
| Page | What it covers |
|---|---|
| Health monitoring | The four health metrics to track (Health Factor, Carry Spread, Net Staking APR, Utilization Ratio) and how to read them. |
| Health emergency | Restoring an unhealthy vault (Health Factor < 100%): burn stETH, add ETH, or rebalance: with the trade-offs of each. |
| stVaults economy examples | Worked APR models for DeFi-integrated, institutional, and leveraged staking strategies. |
| Voluntary rebalancing & vault closure | Eliminating stETH liability to close a vault: external repay vs. voluntary rebalancing to Lido Core. |
| Applying report guide | Applying oracle reports via the LazyOracle so operations (mint, withdraw, rebalance) see fresh vault state. |
| stVault disconnect guide | Disconnecting a single stVault from Lido Core to operate independently. (Distinct from the pooled-product disconnect guide above.) |
| Node operators identification | Becoming an Identified Node Operator to access better reserve ratios and stETH minting tiers. |
Deployed contracts
Authoritative Lido core contract addresses per network.
| Network | Addresses |
|---|---|
| Mainnet | https://docs.lido.fi/deployed-contracts/ |
| Hoodi (testnet) | https://docs.lido.fi/deployed-contracts/hoodi |
Source code
| Repository | Description |
|---|---|
| lidofinance/core | Lido core contracts, including the V3 stVaults stack (StakingVault, Dashboard, VaultHub, oracles). Interface-only from our side: we do not modify these. |
| lidofinance/vaults-wrapper | The DeFi Wrapper / pooled staking contracts the SVM is built on (StvPool, StvStETHPool, WithdrawalQueue, Distributor, Factory, strategies). |
Updated about 4 hours ago
