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.