The Staking Vault Manager

What the SVM does

The Staking Vault Manager (SVM) is an enterprise-grade platform whose purpose is to make Lido V3 easy to use and access. It offers all features that are necessary to operate a stVault, and provides some UX improvements.

The SVM covers four areas.

On-chain operations. Everything needed to run a stVault across its full lifecycle: creating and connecting vaults, funding them, the validator lifecycle (predeposits, activations, top-ups, consolidations, exits, and withdrawals), minting and burning stETH (and wstETH), processing withdrawal requests, rebalancing, and settling node-operator and protocol fees. If Lido v3 supports an operation, the SVM builds the calldata for it.

Analytics. A comprehensive coverage of live data such as contract balances, validators, rewards, liabilities, fees, vault health, deposits, withdrawals: aggregated from on-chain transaction and events, as well as external data sources. You monitor performance and spot problems early without running your own indexer.

Automation. Webhooks push vault and validator events to your systems as they happen, replacing polling. Together with the API, this lets you drive operations (finalising withdrawals, settling fees, reacting to health changes) from your own infrastructure.

Multi-user access. The SVM supports organization accounts with read and write access, so teams can easily coordinate. Users can also integrate with the SVM via API.

Why use the SVM

Built-in node operator and data integrations. The SVM connects directly to a roster of supported node operators and to the data sources that report vault and validator state. Operator selection, vault creation, and monitoring work out of the box: there are no separate integrations to build or maintain.

Easier to operate, easier to build on. For day-to-day operators, the SVM turns multi-contract procedures into single actions in a clean UI. For developers, the same operations are available through one consistent API, with webhooks instead of polling and ready-to-sign calldata instead of hand-assembled transactions. Either way, you work in terms of vaults, validators, and withdrawals rather than raw contract calls.

Related

• Lido v3 primer: the protocol foundation the SVM operates on
• SVM vs SVM Pro: which product tier fits your use case
• Roles and permissions: how on-chain roles map to team access
• Subscribe to webhooks: the events the SVM emits for automation