Admin
Learn what the Lotus admin controls including ownership, fees, IRM/LLTV/liquidation module enablelists, and market hook configuration with scoped authority.
The Lotus protocol has a single admin address, retrievable via owner(). The admin controls global protocol configuration, per-market settings, and the enablelists that gate market creation. Admin authority is intentionally scoped — the admin cannot move user funds, modify existing market parameters beyond fees, or bypass protocol safety checks such as health requirements and LLTVs.
What the Admin Controls
The admin manages protocol-level settings: transferring ownership, designating a fee recipient, and setting per-tranche protocol fees. Fee updates are bounded by a maximum of 25% and always accrue interest before taking effect so the change applies on up-to-date state. For the full function signatures and revert conditions, see Reference → Admin.
The admin also manages three one-way enablelists that control which components can be used in new markets. The admin can enable IRM implementations, LLTV values, and liquidation module contracts. Once a component is enabled, it cannot be disabled — this one-way design prevents the admin from pulling the rug on existing markets that depend on an approved component.
Market creation itself is permissionless. Any address can create a market as long as it uses IRM, LLTV, and liquidation module values that the admin has previously enabled. The admin's role is to curate the set of approved components, not to create every market directly.
Market Hooks
The admin can attach a hook contract to any existing market. Hooks execute custom logic after core operations — supply, borrow, withdraw, and collateral management — and can veto transactions by reverting. This mechanism enables use cases such as restricting market access to allowlisted addresses or enforcing stricter health requirements on borrowers. The admin specifies which operations trigger the hook via a permissions bitmask. Setting the hook address to zero removes it. For the full API, see Reference → Admin → Market Hooks.
See Also
Reference → Admin for complete function signatures, parameter tables, and revert conditions
Reference → Contract API for the full protocol API
Reference → Authorization for the delegation system
Last updated

