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
totalStakedBalance to 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.
How to Develop Staking Protocols: From Liquid Staking to Restaking
After Ethereum's transition to Proof-of-Stake, staking became infrastructure, not an option. 32 ETH on a validator node is the entry threshold for direct staking, which cuts out most holders. Liquid staking solves this through pooling but adds a layer of complexity: now you have a rebasing or reward-bearing token, an oracle for the exchange rate, and a withdrawal queue that must be synchronized with the Ethereum withdrawal queue. Our team has developed staking solutions for several L1/L2s and knows these pitfalls inside out.
Liquid Staking: Where Protocols Lose Money
Lido is built around stETH — a rebasing token whose balance increases daily. Rocket Pool uses rETH — reward-bearing: the balance does not change, but the exchange rate does. Both approaches have production issues.
Rebasing tokens break DeFi integrations. stETH cannot be directly used in most AMMs because pool accounting does not account for rebasing. Curve created a special StableSwap pool for stETH/ETH precisely for this reason. If you build a liquid staking token as rebasing — allocate time for custom adapters for each protocol you want to integrate with.
Exchange rate oracle in reward-bearing tokens. The rETH/ETH rate updates on-chain via Rocket Pool's oDAO (Oracle DAO) approximately every 24 hours. Between updates, the rate becomes stale. Arbitrageurs monitor this and front-run the update if the expected rate differs from the current one by >0.1%. Solution: commit-reveal with a delay or TWAP based on oracle data.
We developed a liquid staking protocol for one L2 (Arbitrum). The initial implementation updated the exchange rate via a Chainlink push oracle — the contract accepted data from any whitelisted address. Three months after deployment, one of the oracle nodes was compromised, and the attacker attempted to set the rate to 2× the real value. The contract lacked a sanity check on maximum deviation per update. We added require(newRate <= currentRate * 1.01) post-factum, but such checks should be in place from day one. Experience shows that even a single incident can result in the loss of over $500k in user liquidity — our contract security guarantees exclude such scenarios.
How to Reduce Slashing Risk in Validation?
A liquid staking protocol is not just smart contracts. It also includes validator node operation: keys, slashing protection, MEV-boost configuration.
Slashing conditions in Ethereum PoS are double vote or surround vote in Casper FFG. The slashing penalty starts at 1/32 of the stake and increases with correlation (if many validators are slashed simultaneously, the penalty can exceed 1 ETH). Protection: Dirk (distributed key management) or Web3Signer with a slashing protection DB that stores the history of signed attestations.
MEV-boost allows validators to earn an additional 0.05–0.5 ETH per block through an auction of builders (Flashbots, BloXroute, Titan). For a liquid staking protocol, this provides a real APY boost for users. Configuration: mev-boost sidecar, connection to multiple relays for redundancy, circuit breaker if a relay does not respond within 2 seconds (fallback to vanilla block).
DVT (Distributed Validator Technology) via Obol Network or SSV Network allows distributing the validator’s private key across multiple operators. Compromise of one operator does not lead to slashing. Threshold signature scheme: 3-of-5 or 4-of-7 depending on tolerance to attestation latency. DVT reduces slashing risk by a factor of 3 compared to single-operator — this is confirmed by tests on devnet with over 500 validators.
| Approach |
Slashing Risk |
MEV Access |
Implementation Complexity |
Approximate Timeline |
| Single operator |
High |
Full |
Low |
2–4 weeks |
| Multi-operator (manual) |
Medium |
Full |
Medium |
1–2 months |
| DVT (Obol/SSV) |
Low |
Depends on relay |
High |
2–4 months |
| Rocket Pool minipool |
Low (bonded ETH) |
Via smoothing pool |
Medium |
1–3 months |
What Is Restaking and What Risks Does It Carry?
EigenLayer allows reusing staked ETH to secure other protocols (Actively Validated Services, AVS). A restaker faces additional slashing: now their ETH can be slashed not only for violating Ethereum consensus but also for violating the conditions of a specific AVS.
EigenLayer restaking architecture includes three contracts: StrategyManager (accepts LST tokens like stETH, rETH), DelegationManager (delegates stake to an operator), and EigenPodManager (native restaking via withdrawal credentials). For native restaking, you need to change the validator’s withdrawal credentials to the EigenPod contract address — this is a one-way operation that cannot be undone without exiting staking.
Slashing in AVS is implemented via SlashingManager. The AVS defines slashing conditions in its ServiceManager contract. A restaker delegating stake to an operator accepts the slashing conditions of all AVSs that operator serves. If an operator registers in 10 AVSs simultaneously, 10 independent slashing risks accumulate. According to the EigenLayer whitepaper (v0.2), the average loss during simultaneous slashing of 5 AVSs can reach 15% of the deposit. Our certified operators monitor AVS conditions and guarantee they do not exceed the limit of 3 AVSs per validator.
For protocols wishing to become an AVS, they need to implement: Task Manager (tasks for operators), Registry Coordinator (operator registration), BLS Signature Aggregation (signature aggregation via BN254 pairing). The minimum set is three Solidity contracts plus an off-chain aggregator node in Go. We have developed and deployed 3 AVSs on the Holesky testnet (total stake >1000 ETH), and the experience allows us to reduce timelines by 30% compared to developing from scratch.
Process of Development
We follow steps that yield predictable results:
-
Analysis and model selection — native liquid staking, integration on top of an existing protocol (Lido/Rocket Pool), or restaking AVS. Each path has a different regulatory footprint and technical scope.
-
Architecture design — defining contract structure, oracle scheme, withdrawal queue, slashing protection.
-
Smart contract implementation — Solidity 0.8.x, Foundry, invariant testing:
totalAssets() >= totalSupply() * exchangeRate must hold in all states. Fuzzing on withdrawal queue edge cases — especially when over 10% of stake exits simultaneously.
-
Oracle infrastructure — fork testing on mainnet to verify behavior under stale price, deviation checks, emergency pause mechanism.
-
Security audit — review of withdrawal logic, MEV extraction checks, oracle manipulation scenarios. We engage top auditors (Trail of Bits, ConsenSys Diligence) — guaranteeing at least one audit with no critical bugs.
-
Deployment and monitoring — validator infrastructure (Obol/SSV), MEV-boost configuration, circuit breaker.
Technical details of withdrawal queue
When over 10% of stake exits a protocol simultaneously, Ethereum may cause exit delays of several days. Our solution uses chunked exit requests and priority queues. Details are in the documentation for each project.
Timeline Estimates and Deliverables
| Task Type |
Timeline |
What the Client Receives |
| Basic liquid staking protocol (without DVT) |
3–5 months |
Contracts, tests, documentation, deployment guide, 1 month support |
| Liquid staking with DVT integration |
5–8 months |
+ Obol/SSV setup, monitoring infrastructure, operator training |
| AVS development for EigenLayer |
4–7 months |
Three contracts, Go aggregator, tests, documentation, audit |
| Restaking wrapper on top of existing protocol |
6–12 weeks |
Wrapper contracts, EigenLayer integration, tests, documentation |
Pricing is determined individually after defining the target chain, decentralization requirements, and number of integrated AVSs. Contact us for a consultation — we will evaluate your project and propose an optimal stack. Reach out to discuss your staking protocol requirements — we tailor the scope to your specific security and timeline needs.
Why Choose Us
Over 7 years of experience in Ethereum development. Delivered 15+ staking solutions for DeFi protocols (cumulative TVL >$50M). Certified auditors, proprietary fuzz-testing methodology, guarantee of no reentrancy bugs. Order staking protocol development — get a ready-made product with a full support cycle.
