> 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/overview.md).
# Overview
## Lista DAO for developers
Lista DAO is a DeFi protocol spanning lending, liquid staking, a decentralized stablecoin, and a concentrated-liquidity DEX. Most of it is deployed on BNB Smart Chain; Lista Lending, the LISTA and slisBNB OFTs and the slisXAUE RWA product also run on Ethereum (see [Networks](#networks)). Integration work centres on **Lista Lending (Moolah)** — a Morpho-based isolated-market lending protocol — alongside **slisBNB** liquid staking, **Smart Lending**, the **V3 DEX**, **RWA** markets, **Credit Loans**, the **LISTA** governance token, **lisAster**, the **slisBNBx** Launchpool certificate, and the legacy **lisUSD** Collateral Debt Position. Whether you are integrating against Lista, auditing the contracts, or working out how the pieces fit together, start here. Each product below links to its developer README and its on-chain contract reference.
## Product map
| Product | What it is | Developer docs | Contracts |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Lista Lending (Moolah)** | Morpho-based isolated lending markets and curated vaults, extended with Lista controls (oracle routing, min-loan floor, role-based access). | [README](/for-developer/lista-lending.md) · [Integration Patterns](/for-developer/lista-lending/integration-patterns.md) | [Smart Contract](/for-developer/lista-lending/smart-contract.md) |
| **Liquid Staking (slisBNB)** | Stake BNB to mint the yield-bearing `slisBNB` liquid staking token, usable as collateral across Lista. | [README](/for-developer/liquid-staking-slisbnb.md) | [Smart Contract](/for-developer/liquid-staking-slisbnb/smart-contract.md) |
| **Collateral Debt Position (lisUSD)** | The legacy Helio-era CDP. **Being wound down** — new borrowing is disabled protocol-wide, deposits are whitelisted, and liquidation auctions are whitelist-only. Existing holders can repay or withdraw; new third-party liquidation integrations should use Lista Lending. | [README](/for-developer/collateral-debt-position.md) · [Mechanics](/for-developer/collateral-debt-position/mechanics.md) | [Smart Contract](/for-developer/collateral-debt-position/smart-contract.md) |
| **Smart Lending** | Accepts a Lista **StableSwap** LP position as Moolah collateral through `SmartProvider`, so the LP keeps earning trading fees while backing a loan. Distinct from the V3 DEX below. | [Smart Lending & StableSwap](/for-developer/lista-lending/stableswap-integration.md) · [concept](/introduction/smart-lending.md) | [Smart Lending contracts](/for-developer/lista-lending/smart-contract/smart-contract-bsc-smart-lending.md) |
| **V3 DEX** | Uniswap V3-style concentrated-liquidity AMM — positions as NFTs, swaps via `SwapRouter`. Derive pool addresses with Lista's own init-code hash, not Uniswap's. | [README](/for-developer/dex.md) · [Mechanics](/for-developer/dex/mechanics.md) | [Smart Contract](/for-developer/dex/smart-contract.md) |
| **RWA** | Tokenized real-world assets. The two `USDT` pools (Treasury, AAA CLO) issue NAV-bearing shares via `RWAEarnPool`; slisXAUE (Tether Gold, Ethereum) is a separate product. | [README](/for-developer/rwa.md) | [Smart Contract](/for-developer/rwa/smart-contract.md) |
| **Credit Loans** | Fixed-term, fixed-rate `CreditBroker` lending gated by off-chain credit scoring represented on-chain via Merkle roots and a transfer-restricted `CreditToken` (only whitelisted `TRANSFERER`s may transfer it). | [README](/for-developer/credit-loans.md) · [Loan Lifecycle](/for-developer/credit-loans/loan-lifecycle.md) | [Smart Contract](/for-developer/credit-loans/smart-contract.md) |
| **Governance (LISTA)** | The `LISTA` token and governance contracts. The veLISTA voting-escrow mechanism is being retired under LIP-024; existing locks can still be exited. See the Smart Contract page for the exit paths and their gates. | [README](/for-developer/lista-governance.md) | [Smart Contract](/for-developer/lista-governance/smart-contract.md) |
| **lisAster** | ASTER staking aggregator: deposit ASTER to mint the transferable `lisAster` ERC-20, then stake it for epoch-based rewards. | [README](/for-developer/lisaster.md) | [Smart Contract](/for-developer/lisaster/smart-contract.md) |
| **Lista Rights** | Reward distribution for the **holder** emission programme (LISTA Holder Boost). `LendingRewardsDistributorV2` and `RewardsRouter` are each deployed multiple times, one set per emission programme except Credit (no `RewardsRouter`) — see the README for how to tell instances apart. | [README](/for-developer/lista-rights.md) | [Smart Contract](/for-developer/lista-rights/smart-contract.md) |
| **slisBNBx** | A non-transferable collateral certificate that lets a Moolah collateral position also join Binance Launchpool. Formerly `clisBNB`. Minting and burning are driven by `SlisBNBxMinter`, whose address is on the [Lista Lending BSC Core](/for-developer/lista-lending/smart-contract/smart-contract-bsc-core.md) page. | [README](/for-developer/clisbnb.md) · [Delegation](/for-developer/clisbnb/delegation.md) | [Smart Contract](/for-developer/clisbnb/smart-contract.md) |
Cross-cutting references: the resilient price layer behind lending and the CDP — start at [Standard Collaterals](/for-developer/multi-oracle/multi-oracle-standard.md) for the per-asset sources, or [Consuming Oracle Prices](/for-developer/multi-oracle/consuming-prices.md) to read prices in code — and [Lista Platform Services](/for-developer/services.md) for the off-chain APIs.
## Where to start
* **Integrating** — [Integration Patterns](/for-developer/lista-lending/integration-patterns.md) for the provider and broker flows, then the [Contract Reference](/for-developer/lista-lending/contract-reference.md) or the [SDK](/for-developer/lista-lending/sdk.md).
* **Reading data** — the [Moolah Lending API](/for-developer/services/lending-api.md).
* **Auditing** — each product's **Smart Contract** page above, the [Multi-Oracle](/for-developer/multi-oracle.md) price layer, and [Audit Reports](/security/audit-reports.md).
## Networks
Lista contracts are deployed on:
| Network | chainId |
| --------------- | ------- |
| BNB Smart Chain | 56 |
| Ethereum | 1 |
Each product's Smart Contract page carries its address set, for BSC and — where applicable — Ethereum. These address tables can lag a deployment: as of this writing, [Governance](/for-developer/lista-governance/smart-contract.md)'s table (synced from an internal source) is missing the Ethereum LISTA OFT address even though LISTA bridges to Ethereum (above) — if a page looks incomplete for a chain the product runs on, treat it as a doc gap to report, not proof the contract doesn't exist.
---
# 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/overview.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.
