Introduction
Lido Lend is a lending protocol of isolated markets. Its core contract, LidoLend, is a fork of Morpho Blue and keeps Morpho's isolated-market accounting. A Lido policy layer adds per-market rules on top: a supply cap, delayed collateral activation, guardian signals, freeze and pause controls, and additional exit paths for lenders. The Lido DAO governs the protocol.
How it works
Each market lets lenders supply one loan token and lets borrowers borrow that token against one collateral token. A market also selects an oracle, an interest-rate model (IRM) and a liquidation loan-to-value (LLTV). The oracle values collateral in loan-token units. The IRM sets how debt and lender claims grow over time. LLTV is the borrowing limit that the core health check uses.
When debt exceeds the LLTV-adjusted collateral value, anyone can liquidate the position. The liquidator repays debt and may receive collateral. The payout includes a liquidation incentive that depends on the market's LLTV. If a liquidation uses all the collateral and debt remains, the core writes that debt off against the market's suppliers.
Five fields identify a market: loanToken, collateralToken, oracle, irm and lltv. Positions and totals are isolated by market, so assets in one market do not back positions in another. One core contract holds all markets and is the source of truth for balances, shares and token custody. Token custody is shared by token address.
In a market with a controller, the core calls the controller before most actions. The controller allows the action or reverts it. It cannot change the amounts that the core calculates, spend user tokens or act for user accounts.
For the full system model, see Architecture and the architecture specification.
What is different from Morpho Blue
The fork of the core makes four changes to Morpho Blue (see FORK_NOTES):
- only the core owner can create markets, and
enableIrmandenableLltvare removed; - a market can be bound to a controller when it is created, and the core calls that controller before most market actions;
- a new
settlefunction lets a lender exit against borrower collateral; - the core runs behind a proxy and is initialized once in proxy storage.
The Lido layer adds these contracts and mechanisms:
- Market controller.
LidoLendMarketControllerapplies the policy of one market: supply cap, collateral activation, guardian-based borrow gating, freeze and pause, and settlement policy; - Collateral activation. New collateral counts in the core health check at once, but it supports new borrowing only after an activation delay;
- Guardian signals. Guardians report on accounts and on their review progress through
GuardianSignals. Reports can delay collateral activation or ban new borrowing. They cannot seize collateral; - Settlement and lender exits. A lender can cancel a borrower's debt against its own supply and receive collateral of the same oracle value, with no liquidation incentive.
LidoLendERC4626vaults add a fallback exit that pays free liquidity first and settles the rest; - Governance-managed IRM. The
irmfield of a standard market points toIrmRouter, which forwards rate calls to a selected model such asAdaptiveCurveIrm. Governance roles can change the route and the model configuration after market creation.
For lenders
A lender supplies the loan token directly to the core and receives supply shares, or deposits into a LidoLendERC4626 vault and receives transferable ERC-4626 shares. Borrowers can use the supplied tokens, so a lender may not be able to withdraw the full claim at once.
Main constraints and options:
- a supply cap can limit new supply to a market;
- an ordinary withdrawal is limited by the free liquidity of the market;
- when liquidity is short, a lender can exit through settlement, directly or through the vault fallback exit, if the market enabled settlement at creation. Otherwise, the lender can withdraw only the free liquidity;
- lenders bear the debt that remains after a liquidation uses all of a borrower's collateral.
See Risks.
For borrowers
A borrower supplies collateral, borrows the loan token and repays the debt. The whole collateral balance protects the position from liquidation. Only active collateral counts toward new borrowing.
Main constraints:
- new collateral goes through an activation delay before it supports new borrowing. The delay grows with recent collateral inflow to the market, and guardian reports can extend it;
- a guardian ban blocks new borrowing and stops collateral activation, but it does not block repayment or collateral withdrawal;
- a market freeze stops new borrowing, collateral activation and collateral withdrawal while debt remains;
- a position with debt above its LLTV-adjusted collateral value can be liquidated;
- in a market with settlement enabled, a lender can cancel part of a borrower's debt and take collateral of the same oracle value. Without borrower action, this applies only to the borrower at the root of the risk queue, which is ordered by estimated LTV. A borrower can also opt in by setting a personal target LTV.
See Risks.
Governance and safety
- Lido DAO. The Lido DAO Agent is the initial proxy admin of the core, the IRM router and the market contracts, and it administers the privileged roles. Until a proxy is ossified, its admin can replace the contract code;
- Lend Operational Committee. In the intended setup, routine configuration goes through predefined Easy Track motions that execute through the
EVMScriptExecutor. This covers market activation, supply caps, activation and settlement configuration, fees, IRM configuration, guardian membership, unbans and unfreezing; - Lend Risk Steward Committee. In the intended setup, it is appointed as the steward of each market in
RiskStewardDashboard. As a steward, it can only tighten a market: freeze it, increase activation delays, the activation lock or the minimum deposit, or revoke instant activation; - Emergency pause.
CircuitBreakerlets a registered emergency actor apply one finite pause to a market controller. In a Dual Governance emergency, the Reseal Committee can keep a paused market paused indefinitely through the Reseal Manager, and, in a tie, the Tiebreaker Committee can end the pause. Otherwise, a pause ends when its fixed duration expires, unless a Lido DAO vote changes the controller's roles; - Guardians. Guardians report account risk and review progress through
GuardianSignals. Flags from a quorum of distinct guardians ban an account in a market.
No role other than proxy administration can directly rewrite or redirect a core or vault position. For the full role map, see Governance and Committees. For audits and vulnerability reporting, see Audits and Security.
Where to go next
- Integrators: Architecture, Deployed contracts;
- Lenders and borrowers: Risks;
- Governance participants: Governance, Committees, Audits, Security;
- Terms: Glossary.
The full specifications are in the lend-markets specs, the core specification and the IRM specification.