Liquid Staking Protocol Development

Liquid Staking Protocol Development

Liquid staking solves the fundamental problem of regular staking: staked ETH is locked and cannot be used in DeFi while unbonding happens. A liquid staking protocol gives the user a derivative token (stETH, rETH) — a liquid representation of the staked asset that can be used in Aave, Curve, Compound.

Lido captured $30B+ TVL precisely because stETH became the "native" collateral in DeFi. Designing such a protocol requires understanding both PoS consensus and DeFi tokenomics.

Protocol Architecture

Protocol Layers

User Layer
  ├── Deposit ETH → mint stETH
  └── Burn stETH → receive ETH (via withdrawal queue)

Protocol Layer  
  ├── Staking Router (distribution across operators)
  ├── Withdrawal Queue (ERC-721 withdrawal NFTs)
  └── Oracle (reports current validator balance)

Node Operator Layer
  ├── Operator A (N validators)
  ├── Operator B (N validators)
  └── ...

Rebasing vs Value-accruing Tokens

Two patterns for implementing a liquid staking token:

Rebasing (stETH model): the stETH balance of a user automatically increases when staking rewards are received. 1000 stETH today → 1005 stETH tomorrow. Convenient for users, but breaks some DeFi protocols that don't expect a changing balance.

Value-accruing (rETH model): the balance doesn't change, but the exchange rate grows. User received 1 rETH, it exchanges for 1.05 ETH over a year. Compatible with all DeFi protocols, but less intuitive.

Lido uses rebasing for stETH and a separate wrapped wstETH (value-accruing) for DeFi compatibility.

Oracle Mechanism

The protocol must know the current total balance of all validators to correctly calculate the exchange rate. This information comes from the Beacon Chain — a separate consensus layer of Ethereum.

Oracle committee: a group of trusted nodes (DAO-managed) periodically (usually daily) reports totalStakedBalance to the contract. The contract accepts data upon reaching quorum (for example, 5 out of 9).

Canary oracle: one of the oracles monitors the data of others. If values diverge significantly — alert.

Self-balancing: new user deposits must be correctly converted to stETH at the current exchange rate, which includes accumulated rewards.

Node Operator Management

A liquid staking protocol delegates actual staking to node operators:

Operator registry: a list of approved operators. Each operator has a limit on the number of keys (validators) they manage.

Key management: operators provide pre-generated BLS keys for validators. The contract stores deposit data (public keys + signatures). When 32 ETH is collected — automatic deposit to a new validator via Ethereum deposit contract.

Slashing insurance: if an operator receives slashing — the protocol must compensate affected stakers. Need an insurance fund or slashing coverage mechanism.

Incentives: operators receive a share of staking rewards (usually 5-10%). Plus reputation — larger operators compete for a place in the protocol.

Distributed Validator Technology (DVT)

To reduce single operator risk — DVT (Obol, SSV Network). One validator is managed by a group of operators via threshold signature scheme. 3-of-5 scheme: 3 out of 5 operators must sign to validate. One operator offline — the validator continues working.

Withdrawal Queue

Before Shanghai upgrade (April 2023) ETH was locked forever. Now withdrawal is possible, but:

• The withdrawal queue can take days during high demand
• The protocol must have a liquidity buffer for instant small withdrawals

Withdrawal NFT (ERC-721): the user requests withdrawal, receives an NFT representing their claim. NFT tradeable — can be sold at a discount instead of waiting.

Buffer strategy: part of ETH (1-5% of TVL) is not staked, held as instant liquidity. Upon withdrawal request — immediate if within buffer, or queue if larger.

Tokenomics and DAO

Protocols like Lido are managed by DAO through governance tokens (LDO). Key governance decisions:

• Adding/removing node operators
• Changing fee parameters
• Upgrading contracts (via timelock)
• Treasury management

Fee structure: Lido takes 10% of staking rewards. Of these, 5% — to operators, 5% — to DAO treasury.

Security and Risks

Smart contract risk: the protocol became a target for $30B+ TVL — highest priority for attackers. Multiple audits (Sigma Prime, OpenZeppelin, MixBytes), bug bounty $2M+.

Centralization risk: if one protocol controls 30%+ of all Ethereum validators — threat to network decentralization. The Ethereum community actively discusses soft caps.

Oracle manipulation: incorrect data from oracle committee can manipulate exchange rate. Multi-level checks, circuit breakers on anomalous values.

Operator slashing: one operator with a large number of validators, if operating incorrectly (double signing), can receive major slashing penalty. Operator diversification and insurance fund.

Developing a full-scale liquid staking protocol like Lido — 12-18 months of work by a team of 10+ people. A simplified protocol for one network with lower TVL — 4-8 months.