Skip to main content

🏛️ Qualified Custodians Supporting stVaults

This page outlines which Qualified Custodians support interaction with stVaults, and how institutional stakers can access stVaults depending on their custody setup.

This resource is useful for:

  • Node Operators offering stVaults to institutional clients
  • Institutional clients evaluating custody options

stVaults Technical Requirements

To interact with stVaults, a custodian must support:

  • Ethereum mainnet custody
  • Arbitrary smart contract interactions
  • ERC-20 token custody
  • stETH and/or wstETH Ethereum tokens integrated

To interact with the native stVaults Web UI, the custodian must support DeFi connectivity, such as WalletConnect or an equivalent dApp connection method.


Custodian Compatibility Matrix

info

Support may vary by jurisdiction, entity, and onboarding scope. Clients should confirm details directly with their custodian.

CustodianstETH SupportwstETH SupportstVaults Web UI integrationOfficial website
FireblocksWalletConnecthttps://www.fireblocks.com/
CopperCopperConnect Browser Extensionhttps://copper.co/
Cactus CustodyCactus Linkhttps://www.mycactus.com/
BitGoWalletConnecthttps://www.bitgo.com/
AnchorageWalletConnecthttps://www.anchorage.com/
KomainuWalletConnecthttps://komainu.com/
Hex TrustWalletConnecthttps://www.hextrust.com/

Whitelisting smart contract addresses

To use the stVaults infrastructure, the relevant stVaults smart contracts must be whitelisted for interaction. Please ask your administrator or custodian support team to add the required stVaults contract addresses to the whitelist.

Some addresses must be whitelisted before creating your first vault, while vault-specific addresses can only be added after a vault has been created. We recommend whitelisting the core stVaults infrastructure addresses upfront, and adding individual vault contract addresses as new stVaults are deployed.

stVaults infrastructure addresses to be whitelisted

Smart ContractAddressDescription
VaultFactory0x02Ca7772FF14a9F6c1a08aF385aA96bb1b34175AFactory for deploying StakingVault + Dashboard pairs using a beacon proxy. Learn more
VaultHub0x1d201BE093d847f6446530Efb0E8Fb426d176709Central registry and lifecycle manager for StakingVaults connected to the Lido protocol. Handles vault connection, minting/burning stETH against vault collateral, rebalancing, fee settlement, and bad debt management. Learn more
PredepositGuarantee0xF4bF42c6D6A0E38825785048124DBAD6c9eaaac3PredepositGuarantee (PDG) mitigates deposit frontrunning by requiring a node operator guarantee and validator withdrawal credentials proofs (EIP-4788) before activating staged deposits. Learn more
LazyOracle0x5DB427080200c235F2Ae8Cd17A7be87921f7AD6cOracle adapter for stVaults. Stores per-vault reports, applies sanity checks, and forwards vault updates to VaultHub. Learn more
OperatorGrid0xC69685E89Cefc327b43B7234AC646451B27c544dRegistry for node operators, groups, and tier parameters that define share limits, reserve ratios, and fee schedules for stVaults. Learn more

Deployed stVault addresses to be whitelisted

When an stVault is created (deployed), it includes two smart contracts by default: StakingVault (the core primitive) and Dashboard (an interface layer for the StakingVault that simplifies interaction). You can find the addresses of these smart contracts at the bottom of the stVault main page (Dashboard):

stVaults Web UI: Smart Contract addresses