TL;DR
- Fireblocks users can now access Lido V3 stVaults through WalletConnect, using the stVaults Web UI and the Fireblocks mobile app within existing custody workflows.
- The setup targets vault owners seeking dedicated staking infrastructure with direct control over validators, fees, jurisdictional settings, MEV routing, and optional stETH liquidity.
- Lido pairs the integration with audited smart contracts, institutional approval flows, emergency procedures, and operational controls designed to fit stricter internal risk frameworks.
Fireblocks is opening a new route into Lido V3 stVaults, giving institutions a way to access modular staking infrastructure through a custody setup they already know. The significance of the move lies in how it narrows the distance between institutional controls and onchain staking customization. Instead of requiring firms to step outside their policy framework, the integration lets them connect to the stVaults Web UI through WalletConnect using the Fireblocks mobile app, creating a workflow that feels closer to treasury management than to the improvisational wallet culture that has long defined much of crypto staking.
That matters because stVaults are built for entities that want more than pooled exposure. The product uses a single-operator architecture that gives large staking participants dedicated and customizable vaults with direct control over validator choice, fee arrangements, infrastructure, and internal risk settings. Lido frames this as a way to reduce the usual tradeoff between control and liquidity, since vault owners can still retain on-demand liquidity through optional stETH minting while also setting jurisdictional preferences, MEV routing, and insurance mandates to match strict internal policy requirements that many institutions simply cannot ignore or easily work around.
A Familiar Custody Layer Meets a More Modular Staking Model
The operational flow is fairly simple, but the implications run wider. A Fireblocks user can open the stVaults interface, choose WalletConnect, scan the QR code through the Web3 Wallet section of the Fireblocks mobile app, and then create or manage vaults inside that institutional approval environment. Once connected, the account can manage stVaults, monitor vault health, and execute emergency procedures. This setup is explicitly meant for vault owners, meaning institutions that want to create and operate their own vaults rather than gain indirect exposure through pooled staking structures built for a very different client base.
Security is the part intended to make the model usable for serious capital. Onchain actions initiated through the stVaults Web UI route through Fireblocks’ approval workflows, while Lido V3 smart contracts sit behind audits, formal verification work, bug bounty coverage, and emergency procedures. The design also includes controls for supplying and withdrawing ETH, minting and repaying stETH, triggering validator withdrawals, and using emergency processes when vault parameters deteriorate. Support still depends on jurisdiction, entity type, and onboarding scope, but the signal is clear: institutional staking is being rebuilt around configurable vaults that fit custody rails.
