Unveiling Lido Lend: Security-First Lending

Lido Lend: mainnet deployment, audits and vote items

This post lists the Lido Lend mainnet deployment for the Lido DAO on-chain vote that starts on November 18: the vote items, contract addresses, parameters, audit reports and deployment verification reports. The design is described in the Final Proposal.

The deployed contracts, audits and committees are also maintained in the Lido Lend docs: Deployed contracts, Audits, Committees.

1. Vote items

Lido Lend items are 2–7 of the vote. Each item adds one factory to Easy Track. Aragon Voting adds the factories directly, so items 2–7 do not go through Dual Governance. The trusted caller of all six factories is the Lend Operational Committee Safe. These items do not change Lido Lend roles or admins and do not create markets.

# Factory Address Permitted calls
2 LidoLendActivateMarket 0x17bb2A2B5983D29392A5d31D627D4C8B13383fe6 AdaptiveCurveIrm.applyIrmConfig, IrmRouter.setMarketIrm, LidoLendOwner.createMarket, LidoLendOwner.setFee, RiskStewardDashboard.addMarketSteward, CircuitBreaker.registerPauser, LidoLendPreseeder.preseedMarket
3 LidoLendCircuitBreakerActions 0x4e89cc970F0DBAE2f8C38C083D5D345B4F9e76b8 CircuitBreaker.registerPauser, setPauseDuration, setHeartbeatInterval
4 LidoLendGuardianActions 0x9fE41afb2114bF9430D7f9B1Fb65f0a4B9DeF779 LidoLendOwner.addGuardian, setGuardiansQuorum, removeGuardian, replaceGuardian, setGuardiansSuspectWindow, unbanGuardianSignals
5 LidoLendMarketManagerActions 0x9D75EaE321976e85e472847AFD21246F1f87dC43 LidoLendOwner.setInstantActivation, setMarketCollateralActivationConfig, setMarketSettlementConfig, setMarketSupplyCap, unfreezeMarket, setFee
6 LidoLendRiskStewardActions 0x7276CE5f92911216d41C7b0A9C3575DE873763E9 RiskStewardDashboard.addMarketSteward, removeMarketSteward
7 LidoLendApplyIrmConfig 0x5795E73C0c2007ceD7D65cE4FC21c0C09F14C668 LidoLend.accrueInterest, AdaptiveCurveIrm.applyIrmConfig

2. Source code

Component Repository Audited commit Deploy commit
Lending core lidofinance/lend 4d55f1d 422d589
Policy layer lidofinance/lend-markets 23416c4 9c0ba34
Interest-rate models lidofinance/lend-irm 97af4c3 566d31f
Easy Track factories lidofinance/easy-track, PR #142 4caa911 4caa911
Circuit Breaker lidofinance/circuit-breaker b4b2fbc 6829a5a (tag 1.0.0)
Bundler3 morpho-org/bundler3 263f75d 9afc2f4

Differences between the audited and deploy commits:

  • lend and lend-irm: the deploy commits are earlier commits. Cyfrin matched all 53 audited files at the deploy commits by digest (section 5);
  • lend-markets: no change under src/ (diff). Both commits pin the same lend and lend-irm commits;
  • circuit-breaker: no change under src/;
  • bundler3: changes only in files that Lido Lend does not use and in NatSpec comments.

Deployment artifacts: deployed/mainnet, lend-markets PR #24.

3. Mainnet contracts

Protocol

Per-market contracts (controller, vault and Guardian registry) are proxies of these implementations. They will be listed in the post of each market.

Bundler3 and adapters

Lido Lend has its own Bundler3 instance.

Circuit Breaker and Easy Track

Each LidoLendActivateMarket motion calls LidoLendPreseeder.preseedMarket through the Easy Track EVMScriptExecutor to seed the new market and its vault with permanently locked shares. The Easy Track factory addresses are in section 1.

This CircuitBreaker is a separate Lido Lend instance. It is not the Lido core protocol CircuitBreaker 0x6019CB557978296BA3C08a7B73225C0975DFB2F7, which items 1.8.1 and 1.9.1 of the same vote change.

Exit Books (not used)

Contract Address
MorphoExitBook 0xAd28EFa8f2ef56a68b0Eb6836f4aE1d2D6459Ecd
Erc4626ExitBook 0x0d2580e4c9b20507eDFAeFC7777d760F12Ad55D4
LidoLendExitBookActions (Easy Track factory) 0xA30b212c3657fa745feaE4b48B7Eb0A8F429C604

The Exit Books are not part of the Final Proposal. This vote does not register LidoLendExitBookActions, and ALLOWLIST_MANAGER_ROLE of both Exit Books is held only by the Easy Track EVMScriptExecutor, so no market can be added to them. Their use requires a separate proposal and Lido DAO vote. The two Exit Books are in the scope of the Cyfrin audit, and Cyfrin Stage 1 verified their deployment. LidoLendExitBookActions is in the scope of the MixBytes report, which also verified its deployment.

Committees

Committee Safe Threshold
Lend Operational Committee 0x4f29aA4c299e17176b48c41D67ee97aE673d29bC 5 of 7
Lend Risk Steward Committee 0x1011E8a0668da8bbED925cB5A6DA5aa128C2BB5E 3 of 7
Lend Emergency Brakes Committee 0x604B13eD638663AA0C1eEF0c3482e51f228BA2E1 3 of 6

The Safe owners match the addresses signed by the members in posts #64, #65, #66, #67, #68, #69, #70, #71, #72, #73.

Admins and owners

The Lido DAO Agent (Aragon Agent) 0x3e40D73EB977Dc6a537aF587D48316feE66E9C8c is subject to Dual Governance.

Role Contracts Holder
Proxy admin LidoLend, IrmRouter, per-market controller, vault, Guardian registry and oracle Lido DAO Agent
Owner IrmRouter, AdaptiveCurveIrm Lido DAO Agent
Owner LidoLend core LidoLendOwner
DEFAULT_ADMIN_ROLE LidoLendPreseeder Lido DAO Agent
Role admin LidoLendOwner, RiskStewardDashboard, per-market controller and Guardian registry Lido DAO Agent
Admin CircuitBreaker Easy Track EVMScriptExecutor

4. Parameters

CircuitBreaker parameter Initial value Allowed range
Pause duration 21 days 5–60 days
Heartbeat interval 365 days 30 days – 3 years

Market parameters will be published in this thread before the Easy Track motion of each market.

5. Audits and deployment verification

Lido Lend audits

Report Auditor Date Scope Findings Status
Lido Lend Cyfrin 2026-10-26 lend, lend-markets, lend-irm: 53 files 62: 0 critical, 0 high, 8 medium, 27 low, 21 informational, 6 gas 30 resolved, 1 partially resolved, 31 acknowledged
Lido Lend Easy Track Factories MixBytes 2026-11-16 Easy Track factories, LidoLendPreseeder 11: 11 low 1 fixed, 10 acknowledged
Lido Lend Guardian Daemon SDK MixBytes 2026-11-09 lend-guardian-daemon 16: 1 high, 8 medium, 7 low 12 fixed, 4 acknowledged

Dependency audits

Report Auditor Date
CircuitBreaker Audit Report Cyfrin 2026-05-01
CircuitBreaker Formal Verification Report Cyfrin 2026-04-06
CircuitBreaker Audit Report MixBytes 2026-05-01
Bundler3 Spearbit 2025-01-02
Bundler3 update Cantina 2025-02-17
Bundler3 with update OpenZeppelin 2025-02-18

The upstream audits of Morpho Blue and Morpho Blue IRM cover only the upstream code. The Lido changes are in the scope of the Cyfrin audit and are listed in FORK_NOTES.md in lend and in FORK_NOTES.md in lend-irm.

Deployment verification

Report Auditor Date Scope
Lido Lend Deployment Verification, Stage 1 – Core Cyfrin 2026-11-11 Runtime bytecode, constructor arguments and immutables of the protocol contracts, the Bundler3 adapters and the two Exit Books. Supplementary: code and implementation pointers of the LidoLend and IrmRouter proxies, bytecode of Bundler3 and CircuitBreaker
Lido Lend Easy Track Factories MixBytes 2026-11-16 Mainnet deployments of the Easy Track factories and LidoLendPreseeder

The audited files are matched to the Cyfrin report by keccak256 digests. The digest tooling is in script/config/mainnet/scripts/. The source code of the mainnet contracts is verified on Etherscan.

Stage 2 of the Cyfrin verification will cover the market deployments, starting with WETH / wstETH. Cyfrin will add it to the same report.

6 Likes