> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/for-developer/lista-lending.md). # Lista Lending ## Overview Moolah is Lista DAO's decentralized lending protocol, branded as Lista Lending. It is deployed on BNB Smart Chain and on Ethereum — see [Ethereum](/for-developer/lista-lending/smart-contract/smart-contract-ethereum.md) for that address set, and note the [SDK](/for-developer/lista-lending/sdk.md)'s Ethereum coverage lags the protocol. It is powered by Morpho and built on Morpho Blue smart contracts. Moolah extends standard Morpho market architecture with Lista-specific controls and integrations, including minimum loan floor, resilient oracle routing, protocol-level reentrancy protection, upgradeability, and role-based access control. In addition, it supports two integration patterns for external systems: * Provider contracts for collateral handling and asset transformation * Broker contracts for curated market access and fixed-term/fixed-rate lending flows --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bsc.lista.org/for-developer/lista-lending.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.