Pro feature inventory
Complete list of capabilities SVM Pro unlocks on top of standard SVM.
The exhaustive list of features gated to SVM Pro accounts. For the decision view ("which tier do I need?"), see SVM vs SVM Pro.
Pro access is governed by the is_pro_svm_user flag on your account, returned by GET /v1/account.
Vault types
| Feature | Notes |
|---|---|
Pool vaults (stv) | Generic LP-token pool |
Pool vaults (stvSteth) | Pool with native stETH integration |
| Permissioned pools | Pool vaults with allowList: true: allowlist-gated deposits |
Vault operations
| Operation | Endpoint | Notes |
|---|---|---|
| Allowlist add | POST /v1/lidov3/staking-vaults/{id}/allowlist/add | Grants DEPOSIT_ROLE |
| Allowlist remove | POST /v1/lidov3/staking-vaults/{id}/allowlist/remove | Revokes DEPOSIT_ROLE |
| Settle Lido fees | POST /v1/lidov3/staking-vaults/{id}/settle-lido-fees | Available everywhere; combined UI is Pro-only |
| Disburse operator fees | POST /v1/lidov3/staking-vaults/{id}/disburse-fee | Available everywhere; combined UI is Pro-only |
| Change fee rate | POST /v1/lidov3/staking-vaults/{id}/set-fee-rate | Pro |
| Activate validator | (See API Reference, lido/SVMPro tag) | PDG → beacon-chain activation |
| Prove unknown validator | (See API Reference, lido/SVMPro tag) | Requires NODE_OPERATOR_PROVE_UNKNOWN_VALIDATOR_ROLE |
| Change tier | (See API Reference, lido/SVMPro tag) | Tier ID + share-limit change |
| Sync tier | (See API Reference, lido/SVMPro tag) | No parameters; refresh from operator grid |
| Operator grid management | (See API Reference, lido/SVMPro tag) | Manage validator-provider mappings |
| Timelocked operations | (See API Reference, lido/SVMPro tag) | Schedule sensitive grants/changes through Timelock |
Integrations
| Feature | Notes |
|---|---|
| Webhooks | Six event types; see Webhook event catalog |
API endpoints flagged x-isProSvmFeature | 23 operations gated to Pro |
| Per-pool Timelock contract | Delay enforcement for sensitive operations |
Validator providers
| Feature | Notes |
|---|---|
| Myrmidon Staking support | Pro accounts typically have Myrmidon Staking enabled in their operator grid by default; standard accounts may need to request it |
UI surfaces
The following appear only when is_pro_svm_user is true (and the relevant vault feature is configured):
| Surface | Appears when |
|---|---|
| Allowlist tab on vault detail page | Pool has allowList: true |
| Operations → Activate | Vault has validators in pdgState ∈ {predeposited, proven} |
| Operations → Operator Grid | Pro account |
| Operations → Timelocked Operations | Pro account |
| Operations → Change Fee Rate | Pro account |
| Operations → Settle Fees (combined) | Pro account |
| Operations → Manage Allowlist | Pool has allowList: true |
| Operations → Tier Settings | Pro account |
| Settings → Webhooks | Pro account |
| Header tier toggle | Pro account |
What's identical between SVM and SVM Pro
For symmetry: these features behave the same in both tiers:
- Dedicated stVaults
- Validator creation, exit, withdrawal flows
- Permissions tab / on-chain role management
- Linked wallets
- API keys and the bulk of read endpoints (
lido/read,lido/stakingVaults,lido/rewards) - The Dashboard contract and its standard operations
A note on endpoint counts
Two different counts circulate in older docs:
- 23: operations carrying
x-isProSvmFeature: true(the strict gating flag) - 33+: operations tagged
lido/SVMProin the OpenAPI spec
The two diverge because the lido/SVMPro tag includes read-only operations (e.g. listing operator-grid state) that aren't strictly Pro-gated. The 23 count is the authoritative number for "operations that fail without is_pro_svm_user."
Updated about 1 month ago