Lido’s lending plan could block loan repayments without stopping interest

Under Lido Lend’s proposed emergency rules, borrowers could be blocked from paying down debt and lenders from withdrawing. When the pause ends, borrowers could owe more: the next successful interest update would count the time they spent locked out.

The distinction appears in Lido Lend’s November 9 consolidated proposal. The proposed lending protocol, built on a modified version of Morpho Blue, uses a controller contract to permit or reject market actions. It separates a limited market freeze from a broader controller pause. Only the second shuts down repayment, liquidation and lender settlement together. Lenders supply loan tokens that borrowers take out against pledged collateral.

The proposal reports that the core contracts are deployed on Ethereum mainnet, but the DAO would have to accept the protocol separately. Each market would then need its own motion or DAO vote. The forum discussion continued with a signer declaration on November 14; the thread did not announce a completed acceptance vote or creation of the first market.

Restrictions that preserve repayment

A Guardian ban stops an account’s new borrowing and collateral maturation but does not itself stop repayment, liquidation, settlement or collateral withdrawal under the remaining rules. The expected first WETH/wstETH market would launch with one contributor-run Guardian and a 1-of-1 quorum, with independent Guardians intended later.

Under the market controller rules, a freeze stops new borrowing, new collateral from completing its activation delay, and collateral withdrawals from positions carrying debt. Repayment, liquidation, lender withdrawals and settlement remain available, subject to their ordinary checks.

The Risk Steward Committee could impose that freeze and tighten defined controller settings through its dashboard, but could not loosen them. The proposed Operational Committee would use bounded Easy Track motions, open to LDO-holder objections, for actions such as unfreezing.

Borrowers can pay down debt, a key consideration when comparing crypto loan terms. Lenders can withdraw available loan tokens or use eligible settlement, which reduces a lender’s claim and a borrower’s debt by the same amount in exchange for collateral valued by the protocol’s price feed.

Settlement is the mechanism behind the Fallback Exits CryptoSlate examined in October. Lenders can exit without available loan tokens, but settlement is subject to market rules and policy limits. Bad debt at the front of the borrower queue can block it.

An Exit Book, a system for posting withdrawal requests, has a separate pause that stops new withdrawal requests and fills in that book. Owners can still cancel requests or use underlying positions directly, but those routes cannot bypass a paused market controller.

A pause blocks those routes. The architecture specification says it stops actions subject to the controller, including repayment, lender withdrawals, liquidation, settlement and direct interest updates. Even a direct call to the core cannot bypass the pause. Vault-share transfers and core functions outside the controller’s scope remain available.

Blocking an interest-update call does not make the borrowing period free. The core accounting specification uses elapsed time to calculate interest, and the controller rules explicitly say a later successful accrual covers time since the last update. A borrower could therefore regain repayment access with a larger debt balance under the applicable interest-rate model.

Compare the access rules

Repayment, liquidation and lender withdrawal or settlement are blocked, alongside other controller-checked actions. The interest clock is not stopped.

A finite emergency power does not guarantee a finite interruption: a separate Reseal path can make an active pause indefinite.

Proposed Lido Lend design, not a live pause. Available routes remain subject to normal rules and other active controls. Interest depends on the IRM. Live market settings and permissions are not independently verified.

Sources and evidence

Sources

1. Lido Lend proposal
2. Controller rules
3. Architecture
4. Core accounting
5. Privileged roles
6. Reseal implementation
7. Governance authorization

Supporting facts

• A Lido Lend market freeze stops new borrowing, completion of collateral activation and collateral withdrawals while debt remains, while leaving repayment, liquidation, lender settlement and loan-asset withdrawals available under their ordinary rules. [1] [2]
• A controller pause rejects every market action routed through that controller, including repayment, lender withdrawal, liquidation, settlement and explicit interest accrual; the core provides no bypass for those blocked actions. [3] [2] [4]
• A controller pause does not stop the interest clock: after resumption, a later successful accrual accounts for elapsed time since the market’s last update under the selected interest-rate model. [2] [4]
• A Guardian quorum ban blocks new borrowing and collateral maturation for the account, but does not itself block repayment, liquidation, settlement or collateral withdrawal under the market’s other rules; Guardians cannot lift a ban. [1] [2]
• The proposal gives the Lend Emergency Brakes Committee a 3-of-6 signing threshold and one fixed-duration controller pause per registration through CircuitBreaker, conditional on periodic heartbeats; the committee cannot choose, extend or end that pause. [1] [5]
• A CircuitBreaker pause normally expires automatically, but the proposal says the protocol-wide Reseal Manager can make it permanent when Dual Governance is outside its normal state; the role specification also gives the Reseal Manager power to extend or end controller pauses. [1] [5] [2]
• An Exit Book pause stops request placement and fills in that book, while cancellation and direct access to underlying vault or core positions remain available; those direct routes still have to pass any underlying controller pause. [3] [5]
• These turbulence controls apply per Lido Lend market and do not themselves confer custody or power to move user assets; the proposal separately acknowledges upgradeable proxies administered by the DAO Agent. [1] [3] [5]
• The published Reseal implementation can replace an active finite pause with an indefinite one through the governance contract when called by the authorized Reseal Committee outside Dual Governance’s Normal state; this code path does not require a fresh ordinary DAO vote at that step. [6] [7]

Method

Source-bound permission and authority diagrams from the November 9 proposal and current specifications. Arrows identify affected action routes, not quantities or guaranteed execution. No numerical outcome chart is warranted.

Scope

Proposed Lido Lend design, not a live pause. Available routes remain subject to normal rules and other active controls. Interest depends on the IRM. Live market settings and permissions are not independently verified.

Infographic by CryptoSlate

There is a protective reason to suspend more than new borrowing. The proposal warns that initial price feeds, or oracles, use issuer-published collateral rates, which may diverge from secondary-market prices. If collateral falls in the market without a corresponding rate change, liquidation may become uneconomic and settlement may deliver collateral worth less than the debt canceled. Pausing those transactions can contain that risk, while also interrupting borrowers trying to repay.

Who controls the pause duration

The proposed Lend Emergency Brakes Committee has a 3-of-6 signing threshold. Through CircuitBreaker, it could trigger one fixed-duration controller pause per registration while maintaining required liveness signals, called heartbeats. It could not select the duration, extend the pause or end it early.

The roles specification assigns duration configuration and pauser registration to a separate administrator within immutable bounds. The committee’s successful pause consumes its registration, so another use requires re-registration.

The repository’s mainnet profile selects a configuration with an initial pause of five minutes and a permitted range from one minute to 60 days. The first market’s actual setting has not been confirmed.

Automatic expiry also has an exception. The proposal says the protocol-wide Reseal Manager can make a pause indefinite when Dual Governance is outside its normal state. The published Reseal Manager and Dual Governance implementations require an active finite pause and an authorized Reseal Committee acting through the governance contract. That path can replace the finite pause with an indefinite one without a fresh ordinary DAO vote at that step.

These controls apply per Lido Lend market and do not themselves move user assets. Separate DAO-controlled proxy upgrades remain part of the protocol’s trust assumptions.

For the first WETH/wstETH market, watch for the configured pause duration and who can extend it indefinitely. Those decisions will determine how long borrowers could be stuck with an interest bill they cannot stop by repaying.