AnyLend docsBrowse documentation
AnyLend documentation
A practical guide to isolated lending pools: how the markets work, what each risk boundary means, and how to review a position before you use it.
Read this first
Ethereum mainnet is the production target. The app supports Ethereum, Sepolia, Base, OP Mainnet, Arbitrum, Robinhood Chain, Polygon, Avalanche, BNB Smart Chain, ZKsync Era, Linea, and Scroll. Sepolia remains available for testing and rehearsals. Review the selected network and current parameters before using a pool; these pages are not a promise of safety, yield, liquidity, or availability.
- Production target
- Ethereum mainnet
- Pool model
- Isolated per pool
- Testing network
- Sepolia supported
Choose a starting point
How AnyLend works
Follow a pool from configuration through lending, borrowing, repayment, liquidation, and recovery.
Risk and governance
Understand isolation, token custody, oracle and rate-model trust, curation, and owner controls.
Protocol reference
Map the contracts, public read paths, state-changing functions, and the invariants each pool protects.
What the system guarantees—and what it does not
| Boundary | What is enforced | What remains outside it |
|---|---|---|
| Pool isolation | Each pool keeps its own assets, shares, debt, oracle, rate model, limits, and pause state. | Shared token contracts, shared modules, governance, and market conditions can still create correlated risk. |
| Accounting | Exact ERC-20 deltas, aggregate custody ledgers, share math, and fail-closed solvency checks protect normal write paths. | Unsupported rebasing or fee-on-transfer behavior, malicious tokens, and external integrations are not made safe. |
| Curation | The factory records a reviewed configuration hash and current module/oracle health for a verified pool. | Curation is not an economic-risk rating or proof that an owner, creator, feed, or token can never change. |