> ## Content Index > Fetch the complete content index at: https://blog.lido.fi/llms.txt > Use this file to discover other available public pages before exploring further. # Lido V3 & Copper: Accessing stVaults via CopperConnect - URL: https://blog.lido.fi/lido-v3-copper-accessing-stvaults-via-copperconnect/ - Published: 2026-04-29T13:06:33.000Z - Updated: 2026-04-29T13:06:33.000Z - Description: Learn how Copper uses Lido V3 to access stVaults using CopperConnect. - Author: Lido - Tags: Lido V3 [Copper](https://copper.co/en?ref=blog.lido.fi) is an institutional digital asset custodian, known for its MPC-based custody infrastructure. Copper [is one of the Qualified Custodians](https://docs.lido.fi/run-on-lido/stvaults/qualified-custodians/?ref=blog.lido.fi) supporting stVaults, Lido protocol's modular staking infrastructure. stVaults introduce a single-operator architecture that enables large staking entities — including institutions, ETFs, ETPs, and asset managers — to deploy dedicated, customizable vaults with control over validator choice, fee terms, and infrastructure, while retaining on-demand liquidity through optional stETH minting. Compared to pooled staking approaches, stVaults are designed to address the control-versus-liquidity tradeoff — enabling stakers to run validators with their chosen counterparty, define geographic or jurisdictional parameters, and configure MEV routing and insurance mandates to meet specific internal risk and policy requirements. Copper supports stETH and wstETH in custody. Copper users can create and manage an stVault from their existing Copper Organisation and Account via CopperConnect — the same setup they already use for other on-chain interactions. ## **How It Works** The connection runs through **CopperConnect**, Copper's browser extension. Setup: 1. In the CopperConnect extension: log in, then select the Organisation and Account to connect. 2. [In the stVaults Web UI](https://stvaults.lido.fi/?ref=blog.lido.fi): click Connect wallet, then Browser in the dialog window. Your CopperConnect wallet address will appear as connected, and you can create and manage stVaults. For day-two operations — health monitoring, emergency procedures, voluntary rebalancing and vault closure — see the linked guides below. Full setup steps are in the [CopperConnect user guide](https://docs.lido.fi/run-on-lido/stvaults/qualified-custodians/copper?ref=blog.lido.fi). This flow is for vault owners — institutions that want to create and operate their own vault. Support varies by jurisdiction, entity, and onboarding scope. Before creating a vault, teams should confirm availability and policy settings with their Copper account manager. ## **Security & Risk** Standard Ethereum staking risks apply — for the full breakdown, see Lido's [Risk Assessment Framework for stVaults](https://research.lido.fi/t/risk-assessment-framework-for-stvaults/9978?ref=blog.lido.fi). The following measures have been implemented to support the security of Lido V3\*: - **Smart contracts.** Lido V3 stVaults smart contracts have undergone audits by [Certora](https://github.com/lidofinance/audits/blob/main/Certora%20Lido%20V3%20Audit%20Report%20-%2012-2025.pdf?ref=blog.lido.fi) (including [formal verification](https://github.com/lidofinance/audits/blob/main/Certora%20Lido%20V3%20Formal%20Verification%20Report%20-%2012-2025.pdf?ref=blog.lido.fi)), [MixBytes](https://github.com/lidofinance/audits/blob/main/MixBytes%20Lido%20V3%20Security%20Audit%20Report%20-%2012-2025.pdf?ref=blog.lido.fi), [Consensys Diligence](https://github.com/lidofinance/audits/blob/main/Consensys%20Diligence%20Lido%20V3%20Security%20Audit%20-%2011-2025.pdf?ref=blog.lido.fi), [Composable Security](https://github.com/lidofinance/audits/blob/main/Composable%20Security%20Lido%20V3%20Oracle%20V7%20Audit%20Report%20-%2012-2025.pdf?ref=blog.lido.fi), [Ackee Blockchain](https://github.com/lidofinance/audits/blob/main/Ackee%20Blockchain%20Vault%20Wrapper%20Report%2001-2026.pdf?ref=blog.lido.fi), and [Sigma Prime](https://github.com/lidofinance/audits/blob/main/Sigma%20Prime%20-%20Lido%20BLS%20Library%20Security%20Assessment%20Report%20v2.0%20-%2001-2026.pdf?ref=blog.lido.fi). An ongoing [Immunefi bug bounty](https://docs.lido.fi/security/bugbounty?ref=blog.lido.fi) offers white hats up to $2M in rewards. - **Custody-side controls.** Interactions with stVaults contracts are performed via CopperConnect. - **Built-in operational controls.** stVaults’ design allows Vault Owners to supply/withdraw ETH, mint/repay stETH, trigger [voluntary rebalancing and vault closure](https://docs.lido.fi/run-on-lido/stvaults/operational-and-management-guides/voluntary-rebalancing-and-vault-closure?ref=blog.lido.fi) (available in May 2026 on the Web UI), trigger ETH withdrawals from validators (available in April 2026 on the Web UI), and follow the [Health Emergency Guide](https://docs.lido.fi/run-on-lido/stvaults/operational-and-management-guides/health-emergency-guide?ref=blog.lido.fi) when vault health parameters fall below thresholds. *\* Audits, bug bounties, and operational controls are intended to reduce but do not eliminate underlying protocol or market risks. Additional risks may remain or be unidentified.* For institutions, the key point is that stVaults can be operated with a familiar security model: on-chain actions may be gated by your existing Copper policies, while Lido V3 contracts have undergone audits and include clearly defined emergency procedures. Teams should still run their own diligence on smart-contract, operational, and regulatory risks, and ensure internal approvals and monitoring are in place before going live. [Book a call](https://share-eu1.hsforms.com/1J9K3wmpfTiSn6lO7UgqXWw2dywmt?ref=blog.lido.fi) with the Lido Institutional team for further details. ## **Further reading** - [Qualified Custodians overview](https://docs.lido.fi/run-on-lido/stvaults/qualified-custodians/?ref=blog.lido.fi) - [Copper integration guide](https://docs.lido.fi/run-on-lido/stvaults/qualified-custodians/copper?ref=blog.lido.fi) - [stVaults documentation](https://docs.lido.fi/run-on-lido/stvaults/?ref=blog.lido.fi) - [stVaults Web UI](https://stvaults.lido.fi/?ref=blog.lido.fi)