DeFi Protocols

Lido stETH Liquid Staking

Stake ETH, receive liquid stETH. V3 stVaults add institutional compliance. Open question: is stETH a security?

Vendors

Lido · stVault Partners

Compliance center

stVaults add Identity. Validator risk at Authorization. Security classification unclear.

defistakingliquid-stakinglidostethinstitutional-vaultsecurity-question
Filter by shape:
|
D4L · DEFILido stETH liquid staking·5 stations(2 compliance, 3 infra)·lido
S1INTENTS2S3DISCOVERYS4NEGOTIATIONS5S6AUTHORIZATIONS7FACILITATIONS801Smart Wallet02State Update03Mint04Tx Monitoring05Smart Wallet
3+5 shape system
GatePre-condition — blocks if it failsMonitorConcurrent — observes without haltingObligationPost-settlement — reports after the factsolid = codedashed = policy
How to read this diagram
Each station on the rail represents a compliance or infrastructure event in the Lido stETH liquid staking path. Hover any station to inspect it. The shape tells you what kind of event it is. The ring tells you how it's enforced.
Gate Monitor Obligation| Ingress Crossing Transform Settlement Venue
This path at a glance
5 stations across 5 of 8 segments. 2 are compliance checkpoints, 3 are infrastructure.
4 code-enforced1 policy-enforced
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET

Step 1 · User Wallet (Ethereum)Policy-Enforced

"Self-custody wallet with ETH balance ready for staking. No identity required on base protocol; stVaults (institutional) require KYC/AML."

User's self-custody wallet on Ethereum holds ETH available for staking. On permissionless Lido V2, no identity verification is required—anyone can stake. On stVaults (Lido's institutional variant, launched 2024), the operator address must be whitelisted and subject to KYC/AML checks. Enforcement for stVaults is policy-enforced at the UI/operator level rather than code-enforced by the protocol itself. The staking intent is constructed but not yet submitted to the Lido contract.

Counterparty
Self (user holds keys)
Latency
Instant · no on-chain tx yet
Finality
N/A — staking not yet submitted
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONNode operator selection
L2 CONSENSUSNode operator selection
◆ Enforcement Line — code-enforced at this layer

Step 2 · Validator DelegationCode-EnforcedINGESTDETECTALERT

"Choosing a fund manager for your capital. The delegation is transparent, permissionless at the protocol level, and automated — users cannot select individual validators."

User's ETH is delegated to Lido's node operator set (approximately 30 professional staking operators). Lido's operator management committee selects operators based on performance, geographic diversification, and operational reliability. Each operator runs one or more Ethereum validators. The delegation algorithm distributes new ETH deposits across operators to maintain balance. Code-enforced via Lido's deposit logic; no discretion by the protocol. Operational risk (D13) is the compliance center of gravity here: validator performance, slashing risk, and operator reputation directly affect stETH value.

Counterparty
Lido node operator set
Latency
<1s · on-chain read (operator selection)
Finality
Pre-condition — if operator set is compromised, staking may revert
Vendors
Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L4 ACCOUNTMINT
L3 EXECUTIONMINT
◆ Enforcement Line — code-enforced at this layer

Step 3 · stETH MintCode-Enforced

"Exchange receipt. You deposit asset, receive proof of deposit (liquid staking token) that is fully composable and tradeable."

Lido's deposit contract receives user's ETH and mints 1:1 stETH to the user's wallet. stETH is a rebasing token: the balance increases daily as staking rewards accrue at L3 Execution (Ethereum beacon chain rewards) and L4 Account (stETH balance updates). stETH is fully composable—it can be transferred, used as collateral in Aave or other DeFi protocols, or traded on secondary markets (Curve, Uniswap). Unlike locked staking, stETH unlocks capital: you retain full liquidity while earning staking yield. Code-enforced; the mint is atomic with deposit.

Counterparty
Lido protocol (automated staking pool)
Latency
~12s · Ethereum block confirmation
Finality
Finalized on beacon chain (epoch 32 blocks later)
Vendors
Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSLASHING MONITOR
L2 CONSENSUSSLASHING MONITOR
◆ Enforcement Line — code-enforced at this layer

Step 4 · Validator Risk MonitoringCode-EnforcedINGESTDETECTALERT

"Fund performance oversight. Continuous monitoring of validator health. If validators misbehave, staked capital is penalized (slashed)."

Lido's validator monitoring system tracks Ethereum beacon chain validator performance: attestation participation, block proposals, and slashing risk. If a validator misbehaves (double-signs, surround votes), Ethereum protocol applies a slashing penalty: up to 32 ETH is burned from the validator's balance. Lido's insurance fund covers small slashing events to protect stETH holders from losses. Monitoring is continuous and code-enforced via beacon chain consensus. **Open question:** Is stETH a security under US law? The SEC has not ruled definitively. If stETH is deemed a security, continuous monitoring of validator performance (analogous to fiduciary oversight in traditional finance) becomes a regulatory obligation under the Howey test. This ambiguity affects Lido's US compliance posture.

Counterparty
Ethereum beacon chain validators (Lido operator set)
Latency
Real-time · continuous beacon chain monitoring
Finality
Slashing finalized after 3 epochs (32 blocks each)
Vendors
Ethereum Proof-of-Stake (Beacon Chain — Casper FFG finality + LMD-GHOST fork choice) — permissionless 32-ETH stake threshold; effective validator economics concentrated via Lido / Coinbase / Binance / Kraken / Figment staking pools · MEV-Boost relays (Proposer-Builder Separation — out-of-protocol; OFAC-compliant relays Flashbots / BloXroute Regulated have periodically dominated relay share) · Uniswap v4 (extensible AMM — concentrated liquidity + custom-logic extension framework) · Curve · Balancer · Chainalysis OFAC Oracle (on-chain SDN-list enforcement primitive · code-enforced at the contract layer for opt-in callers) · Circle CCTP v2 (canonical USDC burn-and-mint cross-chain transport) · Wormhole · LayerZero · Across (intent-based settlement) · Securitize DS Protocol (on-chain transfer-restriction smart-contract framework enforcing eligible-investor whitelisting) · ERC-3643 / T-REX (industry-standard permissioned-token framework — Tokeny-developed, used by issuers outside the Securitize stack)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWALLET
L4 ACCOUNTWALLET
◆ Enforcement Line — code-enforced at this layer

Step 5 · stETH Position / UnstakingCode-Enforced

"Portfolio holding. stETH circulates freely as collateral elsewhere, or enters withdrawal queue for redemption to ETH."

User's stETH balance can remain in wallet indefinitely, earning compounding staking rewards via rebasing. Or: user can initiate unstaking by requesting withdrawal of stETH back to ETH. Unstaking enters the Lido withdrawal queue—a FIFO queue on Ethereum L1. Wait time is variable: it depends on the Ethereum validator exit queue (how many validators are exiting) and the size of Lido's accumulated withdrawal requests. Typical wait: hours to days (as of 2024, ~10 days average). Once exited, ETH is returned to the user's wallet. All logic is code-enforced; recordkeeping is the on-chain stETH holdings and withdrawal queue position.

Counterparty
Lido withdrawal queue + Ethereum beacon chain
Latency
Instant (stETH stays in wallet) or ~10 days (unstaking)
Finality
Finalized on Ethereum when ETH returned to wallet
Vendors
MetaMask · MetaMask Institutional (ConsenSys-operated; institutional custody/MPC integrations) · Fireblocks · Safe (Gnosis Safe — multisig + module framework) · EOA (secp256k1 externally-owned accounts) + ERC-4337 account abstraction (EntryPoint singleton + UserOperation mempool — paymaster and aggregator extensions) · Securitize LLC (SEC-registered transfer agent; runs Reg D 506(c)(2)(ii) accredited-investor verification workflow) — off-chain compliance function paired with on-chain DS Protocol enforcement · EigenLayer (restaking primitive — slashing-conditional re-pledge of staked ETH and LSTs to Actively Validated Services; compliance-relevant for AVSs that supply oracle / fast-finality / DA security to downstream protocols) · Securitize Markets ATS (SEC-registered ATS) · INX Securities ATS · BlackRock BUIDL · Franklin BENJI · Hashnote USYC · Ondo OUSG · Apollo ACRED (Ethereum mainnet deployments; issuer profiles carry SEC-registered / NYDFS limited-purpose trust / Reg D 506(c) postures detailed in the respective compliance frameworks)
Chain
Ethereum (Ethereum Foundation (protocol research + core-dev grants; protocol itself is permissionless and operated by the validator set))

Resolved 5 steps across 1 chain(s). 0 threshold(s) triggered. Frameworks: Common Reporting Standard / FATCA.

Coverage notes: 5 disclosed gap(s).

TOOL 01 · CLIENT-SIDE HEURISTIC ENGINE

Transaction Pattern Analyzer

Detect structuring, round-tripping, and smurfing patterns in on-chain transactions — mapped to GENIUS Act §104(d) requirements.

Cloudflare
TOOL 02 · VENDOR COVERAGE MATRIX

GENIUS Act Compliance Mapper

Map GENIUS Act §104(d)/(e) requirements to Chainalysis, Elliptic, TRM Labs, and on-chain monitoring capabilities.

Interactive GENIUS Act compliance matrix. Each cell shows vendor coverage for specific §104 requirements.
Requirementchainalysiselliptictrm-labson-chain
§104(d)(1)
Real-time transaction monitoring
§104(d)(2)
Risk-trigger customer info updates
§104(d)(3)
Behavioral pattern detection
§104(d)(4)
Cross-chain transfer tracking
§104(e)(1)
SAR identification (>$5K + suspicious indicators)
§104(e)(2)
SAR filing automation
§104(e)(3)
SAR record retention (5 years)
§104(e)(4)
Law enforcement notification
Legend
Fully covered
Partial coverage
Gap
Cloudflare

Other DeFi Protocols Paths

SETTLEMENT CHAINS