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.

D4L — Lido stETH liquid staking · Rails: defi · Protocols: Lido V2, stVaults · Origin: United States — Federal
CTR (USD 10,000+)TRAVEL-RULE (USD 3,000+)ENHANCED-DUE-DILIGENCE (USD 50,000+)
D4L — LIDO STETH LIQUID STAKINGYOU ARE HERE● User WalletPOLICY⬣ Validator Deleg…CODE stETH MintCODE Validator Risk …CODE● stETH Position …CODEIntentIdentityDiscoveryNegotiationTransportAuthorizationFacilitationFinalitySTEP 1STEP 2STEP 3STEP 4STEP 5ETHEREUMVisual system: StablecoinAtlas.com · Steps mapped to 8 STP Stages
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 1 · User Wallet (Ethereum)Policy-EnforcedBlockchain-Native

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.

⚠ ENHANCED-DUE-DILIGENCE triggered at USD 50,000 — 31 CFR § 1010.312 — Enhanced Due Diligence (United States — Federal)
Counterparty
Self (user holds keys)
Latency
Instant · no on-chain tx yet
Finality
N/A — staking not yet submitted
Vendors
MetaMask / Fireblocks · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 2 · Validator DelegationCode-EnforcedBlockchain-Native

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 PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKMINTETHEREUM
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 3 · stETH MintCode-EnforcedBlockchain-Native

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 · Chainalysis OFAC Oracle · Circle CCTP v2 · EOA / ERC-4337
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L3 EXECUTIONSmart contracts, swap / bridge logicClearing & matching engine
L2 CONSENSUSValidator ordering, block productionRTGS settlement engine
◆ Enforcement Line — code-enforced below, policy-enforced above

Step 4 · Validator Risk MonitoringCode-EnforcedBlockchain-Native

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.

⚠ TRAVEL-RULE triggered at USD 3,000 — 31 CFR § 1010.410(f) — Funds Transfer Recordkeeping (United States — Federal)
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 PoS Validators · Uniswap v4 · Chainalysis OFAC Oracle · Circle CCTP v2
L5 APPLICATIONL4 ACCOUNTL3 EXECUTIONL2 CONSENSUSL1 NETWORKETHEREUM
L5 APPLICATIONWallet UX, consent, policy engineBank customer channel / issuer app
L4 ACCOUNTBalances, addresses, signing keysCore banking ledger / DDA

Step 5 · stETH Position / UnstakingCode-EnforcedBlockchain-Native

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.

⚠ CTR triggered at USD 10,000 — 31 CFR § 1010.311 — Currency Transaction Report (United States — Federal)
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 / Fireblocks · EOA / ERC-4337

Resolved 5 steps across 1 chain(s). 3 threshold(s) triggered. Frameworks: Bank Secrecy Act, GENIUS Act, OFAC Sanctions Program, FATF Recommendation 16 (Travel Rule), Common Reporting Standard / FATCA.

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