Staked ETH is locked—it cannot be used in DeFi while unbonding. Liquid staking solves this by issuing a derivative token (LST) — a liquid representation of the asset. Developing a liquid staking protocol (LST token) unlocks staking capital for use in Aave, Curve, Compound, and other protocols. Lido captured over $30B TVL precisely because stETH became native collateral in DeFi. Designing such a protocol requires deep understanding of PoS consensus and DeFi tokenomics. Our engineers have 10+ years of experience in blockchain development and security certifications.
How does the Oracle mechanism work?
The protocol needs to know the current total balance of all validators to calculate the exchange rate. This information comes from the Beacon Chain, the consensus layer of Ethereum. Ethereum Beacon Chain documentation
-
Oracle committee — a group of trusted nodes (dao-managed) periodically (typically once a day) reports
totalStakedBalanceto the contract. The contract accepts data upon reaching quorum (e.g., 5 out of 9). - Canary oracle — one of the oracles monitors data from others. If there is a strong deviation, an alert is triggered.
- Self-balancing: new deposits are converted to stETH at the current exchange rate, which includes accumulated rewards.
If data from the oracle committee is incorrect, manipulation of the exchange rate is possible. Therefore, multi-level checks and circuit breakers are applied. Our oracle approach reduces manipulation risks by 3x compared to the baseline scheme.
Why is the choice of token approach (rebasing vs value-accruing) important?
Two main patterns for implementing a liquid staking token:
| Feature | Rebasing (stETH model) | Value-accruing (rETH model) |
|---|---|---|
| User balance | Automatically grows with rewards | Fixed amount, exchange rate increases |
| DeFi compatibility | Requires wrapped version (wstETH) | Native, does not change balance |
| Intuitiveness | High — clear balance increases | Medium — harder to explain rate changes |
| Example | stETH + wstETH | rETH |
Rebasing tokens are simpler for users but less DeFi-compatible: protocols expecting an unchanging balance break on them. Value-accruing tokens solve this but require education. Lido uses rebasing for stETH and a separate wrapped wstETH (value-accruing) for DeFi compatibility. Value-accruing is twice as compatible as rebasing since it doesn't change the balance.
Protocol Architecture
Protocol Layers
User Layer ├── Deposit ETH → mint stETH └── Burn stETH → receive ETH (via withdrawal queue) Protocol Layer ├── Staking Router (distribution to operators) ├── Withdrawal Queue (ERC-721 withdrawal NFTs) └── Oracle (reports current validator balance) Node Operator Layer ├── Operator A (N validators) ├── Operator B (N validators) └── ... Node Operator Management
A liquid staking protocol delegates actual staking to node operators:
- Operator registry — list of approved operators with a limit on the number of keys.
- Key management — operators provide pre-generated BLS keys. The contract stores deposit data. Upon reaching 32 ETH, an automatic deposit is made to a new validator via the Ethereum deposit contract.
- Slashing insurance — if an operator gets slashed, the protocol compensates affected stakers through an insurance fund or slashing coverage.
- Incentives — operators receive a share of staking rewards (typically 5–10%) and compete for positions reputationally.
Distributed Validator Technology (DVT)
To reduce the risk of a single operator, DVT is used (Obol, SSV Network). One validator is managed by a group of operators via a threshold signature scheme. For example, 3-of-5: 3 out of 5 operators must sign for validation. If one goes offline, the validator continues operating.
Withdrawal Queue
ETH withdrawals are now possible, but the queue can take days during high demand. The protocol must have a liquidity buffer for instant small withdrawals.
- Withdrawal NFT (ERC-721) — the user receives an NFT representing their claim. The NFT is tradeable — can be sold at a discount instead of waiting.
- Buffer strategy — a portion of ETH (1–5% of TVL) is not staked as instant liquidity. When a withdrawal is requested, it is immediate if within the buffer, otherwise queued.
Tokenomics and DAO
Protocols like Lido are governed by a DAO via a governance token (LDO). Key decisions: adding/removing node operators, changing fee parameters, upgrading contracts (via timelock), treasury management.
Fee structure: Lido takes 10% of staking rewards. Of that, 5% goes to operators, 5% to the DAO treasury.
How to Develop a Liquid Staking Protocol: 5 Steps
- Analytics and requirements gathering: define tokenomics, choose network, estimate TVL.
- Architecture design: design smart contracts, oracles, withdrawal queues.
- Smart contract development in Solidity with gas optimization (Foundry, Hardhat).
- Security audit: multiple rounds (Slither, Mythril, formal verification).
- Deployment on testnet, then mainnet, configuration of node operators and monitoring.
Security and Risks
- Smart contract risk: the protocol is a target for attacks at TVL > $30B. Multiple audits (Sigma Prime, OpenZeppelin, MixBytes) and bug bounties from $2M are required.
- Centralization risk: if one protocol controls 30%+ of Ethereum validators, it threatens decentralization. Soft caps are discussed in the community.
- Oracle manipulation: incorrect data can manipulate the exchange rate. Multi-level checks and circuit breakers are used.
- Operator slashing: one operator with many validators could incur large slashing from double signing. Diversification of operators and an insurance fund mitigate this.
Timelines and Deliverables
| Phase | Duration | Result |
|---|---|---|
| Analytics | 1–2 weeks | Technical specification |
| Architecture design | 2–4 weeks | High-level design |
| Smart contract development | 4–8 weeks | Prototype on testnet |
| Audit | 2–4 weeks | Audit report |
| Testing and optimization | 2–4 weeks | Ready contract |
| Deployment and support | 1–2 weeks | Mainnet launch |
A full-scale protocol like Lido requires 12–18 months and a team of 10+ people. A simplified solution takes 4–8 months. Timelines depend on required functionality. Potential gas savings with our optimizations reach 50 ETH per month.
What's Included (Deliverables)
- Architecture documentation (High-Level Design, Data Flow)
- Smart contract source code in Solidity (tested, gas-optimized)
- Deployment on testnet and mainnet
- Audit report + recommendations for fixes
- Configuration of oracles and node operators (or instructions)
- Technical support during launch phase (2 weeks)
Our team consists of blockchain engineers with 10+ years of experience in Solidity and Rust (Anchor, Solana). Over 5 years, we have completed 20+ DeFi projects, including several liquid staking solutions. We hold OpenZeppelin certifications and have experience conducting audits. Contact us to evaluate your project — get a detailed development plan and preliminary cost estimate. Order a consultation, and we will select the optimal solution.