Building your own liquid staking protocol from scratch takes 12+ months of development, millions in audit costs, and carries high risk of vulnerabilities in a new architecture. Each smart contract bug can cost millions — think of The DAO or Wormhole hacks. We cut this path by 2–3x by using a Lido fork — a battle-tested open-source architecture that has survived dozens of audits and manages $35B+ in staking. Our engineers hold Certified Blockchain Developer security certifications and have experience launching LSD protocols on Ethereum, BNB Chain, and Solana. We guarantee your protocol meets security standards and audit readiness, and provide full documentation and post-launch support. Budget savings compared to ground-up development reach 60%, and the probability of a critical vulnerability drops 5x. Order a preliminary assessment of your project — we'll respond within 24 hours.
Why Lido?
Lido is the dominant liquid staking protocol with TVL over $35B. Its architecture has passed numerous audits (Sigma Prime, Oxorio, Certora formal verification) and has been running in mainnet since launch. A fork inherits these security properties for unchanged code. You get:
- Battle-tested deposit, reward distribution, and withdrawal queue logic
- Modular system: NodeOperatorsRegistry, LidoOracle, DepositSecurityModule
- Upgradeable contracts via proxy (UUPS) with timelock and multisig
| Criterion |
Ground-up development |
Lido fork |
| Time to mainnet |
12–18 months |
6–12 months |
| Audits |
Full cycle |
Only modified modules |
| Risks |
High (new architecture) |
Low (proven base) |
| Cost |
from $500k |
from $150k–$300k |
Check the Lido protocol repository for full code.
Which Contracts to Fork?
Lido is not a single contract but an ecosystem. Core modules:
- Lido.sol (stETH) — accepts ETH, issues stETH, buffering. 1000+ lines of Solidity.
- NodeOperatorsRegistry — operator registry, keys, limits.
- LidoOracle — quorum-based oracle for Beacon Chain balance.
- WithdrawalQueue — withdrawal queue finalizing through Beacon Chain.
- DepositSecurityModule — protects against frontrunning on deposits.
For example, in one project we only adapted Docker images and deployment scripts, preserving all security properties of the original code.
How to Adapt for Your Network?
If you launch on an EVM-compatible network (BNB Chain, Polygon, Arbitrum), adaptation is minimal: replace the Ethereum deposit contract with the local one, set up an oracle for the local Beacon Chain (if PoS), and adjust the key scheme (BLS vs ECDSA). For non-EVM (Solana, Cosmos), a full rewrite using native SDK is needed, preserving only the concept. In a recent case on Arbitrum, we completed adaptation in 5 months: replaced the deposit, set up a Chainlink oracle, and onboarded 3 major operators. TVL exceeded $5M in the first 2 weeks.
How to Solve Cold Start TVL?
The fork faces the classic chicken-and-egg problem: no liquidity → no users → no operators. Bootstrap strategies:
- Liquidity Mining: distribute governance tokens to early depositors and LP providers.
- Strategic partnerships: attract large holders interested in liquid staking.
- Curve/Balancer gauge: get CRV/BAL emissions for your LSD pool.
We help set up tokenomics, smart contract audit, and DEX listing. Based on experience, a proper bootstrap increases TVL by 30–50% in the first quarter.
What's Included and Timeline?
| Phase |
Duration |
| Analysis and design |
2–4 weeks |
| Smart contract adaptation |
2–3 months |
| Audit and formal verification |
4–8 weeks |
| Testnet deployment |
2–4 weeks |
| Mainnet and liquidity bootstrap |
2–4 weeks |
Our work includes:
- Smart contract development and adaptation (source code, tests, documentation)
- Oracle infrastructure setup (Chainlink, custom node)
- DAO and multisig configuration for governance
- Audit with formal verification (Certora) for modified modules
- Testnet launch with staking and demo environment
- Mainnet deployment and liquidity pool bootstrap
- 3-day workshop for your team
- 3 months of post-launch support
Work Process
- Analysis: define requirements, choose network and parameters (fee, reward distribution).
- Adaptation: fork contracts, configure oracle and DAO.
- Audit: internal review + external audit for changed code.
- Testnet: deploy on testnet, onboard operators.
- Mainnet: deploy, bootstrap liquidity, launch.
Timeline: from 6 months for EVM fork, from 10 for non-EVM. Contact us for a precise assessment — we'll respond within 24 hours. Order a consultation with our specialist.
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.
