Skip to main content

Committees

This page describes who operates Lido Lend day to day and what each actor can and cannot do.

The design separates fast, risk-reducing actions from slower, risk-increasing ones. Committees with instant powers can only restrict: tighten a market's settings, freeze a market, or pause a market for a fixed time. Changes that add risk or restore service go through Easy Track motions, which LDO holders can object to, or through a Lido DAO vote. No committee can upgrade contracts or move user funds through the current contract interfaces. The Lido DAO remains the final trust assumption. It can upgrade a proxy until the proxy is ossified, and it continues to administer the roles after that.

ActorExecution pathMain purpose
Lend Operational CommitteePredefined Easy Track motionsActivate markets and perform routine configuration, membership and recovery actions
Lend Risk Steward CommitteeDirect calls to RiskStewardDashboardTighten selected risk limits or freeze a market
Lend Emergency Brakes CommitteeCircuitBreaker with a live registration and heartbeatApply one finite emergency pause to a market controller
Guardian Security CouncilGuardian or its current delegate calls GuardianSignalsReport account risk and attest to collateral-screening progress
Reseal Committee / Dual GovernanceDualGovernance through ResealManagerKeep an already paused controller paused during a governance emergency
Lido DAOLido DAO AgentUpgrades, role administration, ownership, and actions outside the Easy Track factories
note

Committee names follow the Lido Lend Final Proposal on the Research Forum. The Lend Emergency Brakes Committee is not the CircuitBreaker Committee of the Lido core protocol, and the Lido Lend CircuitBreaker is a separate instance.

For an overview of who controls Lido Lend, see Governance.

Lend Operational Committee​

Purpose: Activate markets and perform routine configuration through Easy Track motions. Each motion is delayed and LDO holders can object to it.

The committee is the trusted caller of the Lido Lend Easy Track factories. The factories fix the target contracts and functions of each motion. The committee chooses the parameters. Lido Lend authorizes the EVMScriptExecutor, so these limits depend on the factory set that the Lido DAO registers in Easy Track. See the Easy Track guide for how motions and objections work.

The factories check most addresses only for a non-zero value. For an ActivateMarket motion, LDO holders should check every address in it:

  • the oracle and its price source;
  • that the IRM config is the address that IrmConfigFactory.getAdaptiveCurveConfig returns for the published parameters;
  • that the controller and the vault are proxies of the listed implementations;
  • the guardians, quorum and roles of the controller's GuardianSignals registry;
  • the steward and pauser addresses.

The market fields, the controller and the settlement setting cannot change after the market is created.

Powers:

  • activate a deployed market (ActivateMarket): configure and route the initial IRM, create the core market with its controller and settlement setting, appoint the market steward, register the Circuit Breaker pauser, preseed the market and vault with permanently locked shares, and optionally set the market fee;
  • register, replace or remove the Circuit Breaker pauser of a controller, and change the instance-wide pause duration and heartbeat interval within immutable bounds (RegisterPauser, SetPauseDuration, SetHeartbeatInterval);
  • unfreeze markets (UnfreezeMarkets);
  • add, remove or replace guardians, and change the guardian quorum and suspect window (AddGuardian, RemoveGuardian, ReplaceGuardian, SetGuardiansQuorum, SetSuspectWindow);
  • unban account and market pairs (UnbanAccounts);
  • grant or revoke instant activation for an integration, and replace the collateral activation config, the settlement config and the supply cap (SetInstantActivation, SetCollateralActivationConfig, SetSettlementConfig, SetSupplyCap);
  • change a market's protocol fee (SetFee), up to the core cap of 25%;
  • add or remove a market steward (AddRiskSteward, RemoveRiskSteward);
  • apply a new configuration to the market's active Adaptive Curve IRM without changing the route (ApplyIrmConfig).

Cannot:

  • upgrade contracts or administer roles;
  • withdraw user positions, choose borrowers for settlement, or start settlement;
  • change the core fee recipient;
  • change the IRM route of a live market;
  • act without a motion: every action waits for the motion duration and fails if LDO holders reach the objection threshold.

Address: 0x4f29aA4c299e17176b48c41D67ee97aE673d29bC [proposed] (the trusted caller of the Lido Lend Easy Track factories)

Forum topics:
Lido Lend: Technical Specification and Committees
Lido Lend: Final Proposal

Quorum: 5/7

List of signers:

NameAddressVerificationPublic verification
Izzy0xd0e99d6A51201C24421cD6DAfFFeE4f0E08BCd91https://etherscan.io/verifySig/341850https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/69
psirex0xeF83852FaBd22bda23857abF171e05Bae9463F95https://etherscan.io/verifySig/341705https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/68
bulbozaur0x62c89F5768D0FeC0915fb614C5eDd9fdeaA2A3fdhttps://etherscan.io/verifySig/341952https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/73
Willem0x28939ef21690Fe8358E93d661d1ce6d7fA9154F3https://etherscan.io/verifySig/341239https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/70
TheDZhon0x59f8d74fe49d5ebeac069e3baf07eb4b614bd5a7https://etherscan.io/verifySig/341699https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/65
mikgur0xcD0cDa37f68a6758f86a4e2910E60174af1190B5https://etherscan.io/verifySig/341741https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/66
Mol_Eliza0x21b82AA7149c8Fd0562E78b740937442FfD43094https://etherscan.io/verifySig/341743https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/67

Lend Risk Steward Committee​

Purpose: Tighten risk controls of a market instantly, without a vote.

Powers:

  • freeze one market (RiskStewardDashboard.freezeMarket). A freeze stops new borrowing and the maturation of activating collateral, and borrowers with debt cannot withdraw collateral. Lender supply, collateral supply, repayment, lender withdrawals, liquidation and settlement stay available;
  • increase the market's base activation delays and the guardian-quorum fallback delay (increaseActivationDelays);
  • lengthen the lock on activating collateral (increaseActivatingLockDuration);
  • raise the minimum standard collateral deposit (increaseMinDepositAmount);
  • remove one integration's instant-activation privilege (revokeInstantActivation). Its future deposits then follow the standard deposit floor, dust, activation delay and inflow rules.

The committee can use the dashboard powers only in a market where it is an appointed steward. Steward membership is stored per market. The ActivateMarket motion appoints the selected steward when the market is created, and the Lend Operational Committee can add or remove stewards through Easy Track. The Lido DAO Agent administers the dashboard roles and can reassign them. See Freeze and pause for the user effects.

Cannot:

  • loosen any setting: each increase* function reverts if the new value is lower than the current one;
  • unfreeze a market;
  • change fees or the interest rate configuration;
  • ban an account other than as a guardian. See Guardian Security Council;
  • upgrade contracts.

Address: 0x1011E8a0668da8bbED925cB5A6DA5aa128C2BB5E [proposed]

Forum topics:
Lido Lend: Technical Specification and Committees
Lido Lend: Final Proposal

Quorum: 3/7

List of signers:

NameAddressVerificationPublic verification
Izzy0xd0e99d6A51201C24421cD6DAfFFeE4f0E08BCd91https://etherscan.io/verifySig/341850https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/69
psirex0xeF83852FaBd22bda23857abF171e05Bae9463F95https://etherscan.io/verifySig/341705https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/68
bulbozaur0x62c89F5768D0FeC0915fb614C5eDd9fdeaA2A3fdhttps://etherscan.io/verifySig/341952https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/73
Willem0x28939ef21690Fe8358E93d661d1ce6d7fA9154F3https://etherscan.io/verifySig/341239https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/70
TheDZhon0x59f8d74fe49d5ebeac069e3baf07eb4b614bd5a7https://etherscan.io/verifySig/341699https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/65
mikgur0xcD0cDa37f68a6758f86a4e2910E60174af1190B5https://etherscan.io/verifySig/341741https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/66
Mol_Eliza0x21b82AA7149c8Fd0562E78b740937442FfD43094https://etherscan.io/verifySig/341743https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/67

Lend Emergency Brakes Committee​

Purpose: Stop all controller-checked operations of a market for a fixed time in an emergency, without a vote.

Powers:

  • apply the configured finite pause to one market controller (CircuitBreaker.pause(controller)). The call consumes the committee's registration for that controller. The pause blocks every operation that passes through the controller: supply, collateral supply and withdrawal, borrowing, repayment, lender withdrawal, liquidation, settlement and explicit interest accrual;
  • keep its authority alive (CircuitBreaker.heartbeat()). Each call extends its pause authority for every controller still registered to it. If the deadline passes, the committee cannot send a heartbeat or pause a controller until the CircuitBreaker admin registers it again.

The ActivateMarket motion registers the selected pauser for the new market's controller. The CircuitBreaker admin is the EVMScriptExecutor, so the Lend Operational Committee configures CircuitBreaker through Easy Track. The general CircuitBreaker page describes the instance of the core Lido protocol, whose admin is the Lido DAO Agent. In the Lido Lend instance, the pause duration is 21 days within bounds of 5 to 60 days, and the heartbeat interval is 365 days within bounds of 30 days to 3 years. The pause does not forgive interest: after the market resumes, the next successful accrual covers the full elapsed period.

Cannot:

  • choose the pause duration. The CircuitBreaker admin sets it for the whole instance within immutable bounds;
  • extend an active pause or resume a controller;
  • pause the same controller a second time until it is registered again through an Easy Track motion.

Address: 0x604B13eD638663AA0C1eEF0c3482e51f228BA2E1 [proposed]

Forum topics:
Lido Lend: Technical Specification and Committees
Lido Lend: Final Proposal

Quorum: 3/6

List of signers:

NameAddressVerificationPublic verification
Izzy0xd0e99d6A51201C24421cD6DAfFFeE4f0E08BCd91https://etherscan.io/verifySig/341850https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/69
psirex0xeF83852FaBd22bda23857abF171e05Bae9463F95https://etherscan.io/verifySig/341705https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/68
bulbozaur0x62c89F5768D0FeC0915fb614C5eDd9fdeaA2A3fdhttps://etherscan.io/verifySig/341952https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/73
skhomuti0xed20740c4ce9a61ce41bb3954186afa0f5f80d9bhttps://etherscan.io/verifySig/341888https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/72
George0x912e21CdA3D7012146da4Df33309d860a9eb0bEbhttps://etherscan.io/verifySig/341681https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/64
folkyatina0x9d557bda79f6f4785c88997ac180ffe1c3d0a62bhttps://etherscan.io/verifySig/342091https://research.lido.fi/t/unveiling-lido-lend-security-first-lending/11987/71

Guardian Security Council​

Purpose: Screen new collateral before it can back borrowing, and report risky accounts.

The council is the guardian set of a GuardianSignals registry. Each guardian is a separate address in the registry and can appoint a delegate that flags accounts and sends heartbeats for it. As stated in the Final Proposal, the first market starts with one guardian and a quorum of 1, and independent guardians are added later. That guardian is the Lend Risk Steward Committee Safe, and its delegate is an externally owned account, so one key can ban an account and advance the scan frontier alone. A registry can serve one market or several markets. Membership, quorum, the suspect window and the heartbeat frontier apply to the whole registry. Flags, suspects and bans apply to one account in one market. GuardianSignals records the reports but cannot verify the underlying screening.

Powers:

  • appoint, replace or remove a delegate for routine daemon transactions (setDelegate). A delegate cannot be a guardian or another guardian's delegate;
  • flag accounts in one market (flag). The per-flag delay can extend collateral activation. When flags reach the quorum, the contract records a ban, which blocks borrowing and collateral maturation for that account in that market;
  • retract a flag (unflag). This can reduce the activation delay, but it cannot lift a recorded ban;
  • add or refresh a time-bounded suspicion report (suspect), or retract it (unsuspect). A suspect report can extend activation, but it cannot ban an account;
  • attest to its latest scan progress (heartbeat). The heartbeats of a quorum of guardians set the shared frontier, which lets ready collateral mature when a later controller operation synchronizes the position.

A ban does not close the position, block repayment, or move assets.

Cannot:

  • move assets or change market parameters;
  • lift a ban. Removing flags or changing the quorum does not clear a recorded ban. Only an authorized unban does;
  • change its own membership, quorum or suspect window. In the initial setup, these change through Lend Operational Committee motions, and the Lido DAO keeps role administration over the registry.

When a guardian is removed, its delegate and heartbeat are cleared, but its existing signals can stay effective until someone calls the permissionless prune function. Pruning never removes a recorded ban.

Members: defined per market. They are published in the Lido Lend Research Forum thread before the market's motion or vote (Final Proposal), and will be listed on the page of each market.

Dual Governance pause extension​

Every standard controller gives PAUSER_ROLE to both CircuitBreaker and the protocol-wide ResealManager. The ResealManager is also the controller's only RESUMER_ROLE holder.

After Dual Governance leaves its Normal state, the Dual Governance Reseal Committee can use the Dual Governance path to reseal a controller that is already under a finite pause. The ResealManager replaces the finite pause with an indefinite one, which lasts until an explicit authorized resume. This path cannot reseal a controller that is not paused. When the Dual Governance tiebreak conditions are met, the Tiebreaker Committee can resume a controller paused through either path. See the Dual Governance guide.

This mechanism is separate from the Lend Emergency Brakes Committee, which can only start its configured finite pause.

Lido DAO​

The Lido DAO holds every power that is not delegated to a committee or exposed through the Easy Track factories. DAO votes are subject to Dual Governance where applicable.

DAO actionScope
Change revenue settingsSet the core fee recipient (setFeeRecipient)
Change a live market's IRM routeSwitch the model selected by IrmRouter.setMarketIrm
Recover assets of auxiliary contractsRecover assets held directly by LidoLendPreseeder
Administer authorityGrant or revoke roles, transfer core ownership, rotate the IRM owners and managers
Change contract codeUpgrade a proxy, transfer its admin, or irreversibly ossify it

When the Lido DAO Agent does not hold the required role, the vote must use an authorized caller or grant the role before calling the setter. Recovery functions can move only assets held directly by the auxiliary contract, not assets in user positions.

Direct account bans​

GuardianSignals.ACCESS_LIMITER_ROLE has no holder in the initial setup. Bans arise only when guardian flags reach the quorum, which is 1 in the first market (see Guardian Security Council).

Changing this requires a separate Lido DAO action to grant the role. A holder of the role could ban one account in one market without guardian quorum (ban). The ban blocks borrowing by, for or to that account and stops its activating collateral from maturing. It does not close the position, block repayment, or move assets.

The registry admin, the Lido DAO Agent, can grant or revoke the role, and a holder can renounce it. In the initial setup, a ban is lifted through the Lend Operational Committee's UnbanAccounts motion, which calls unban through LidoLendOwner (ACCESS_RESTORER_ROLE).