> For the complete documentation index, see [llms.txt](https://docs.radiant.capital/radiant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.radiant.capital/radiant/project-info/rdnt-tokenomics/liquidity-provisioning/liquidity-options.md).

# dLP Liquidity Options

Liquidity pools are essential to many DeFi protocols. They allow users to provide liquidity (in the form of two assets--such as RDNT & ETH) in exchange for a share of the pool's potential yield.

dLP tokens can be locked through the protocol to receive protocol revenue, activate RDNT emissions in the money markets if eligible, and provide governance voting power.

Radiant currently offers the following liquidity pools (to receive platform fees and activate RDNT emissions if eligible):

1. Arbitrum: Balancer 80/20 composition (80% RDNT & 20% ETH)

{% embed url="<https://app.balancer.fi/#/arbitrum/pool/0x32df62dc3aed2cd6224193052ce665dc181658410002000000000000000003bd>" %}

2. BNB Chain: Pancakeswap 50/50 (50% RDNT & 50% BNB)

{% embed url="<https://pancakeswap.finance/info/pairs/0x346575fc7f07e6994d76199e41d13dc1575322e1?chain=bsc>" %}

3. Ethereu&#x6D;**:** Balancer 80/20 composition (80% RDNT & 20% ETH)

{% embed url="<https://app.balancer.fi/#/ethereum/pool/0xcf7b51ce5755513d4be016b0e28d6edeffa1d52a000200000000000000000617>" %}

4. Base: Aerodrome 80/20 composition (80% RDNT & 20% ETH)

Base deployment features a new dLP architecture based on Uniswap V3 designed to mimic an 80/20 ratio as used on other RDNT pools.

{% hint style="danger" %}
Due to this new architecture, the ONLY way to obtain eligible dLP tokens on Base is via zapping through Radiant's front end. **DO NOT** create liquidity directly on Aerodrome, as their returned NFT is not compatible with the RDNT protocol and it **WILL NOT** allow you to earn protocol revenue or RDNT rewards.
{% endhint %}

{% embed url="<https://app.radiant.capital/#/manage-radiant>" %}
Use the ZAP function for Base
{% endembed %}

You can find more details about dLP architecture in its respective section.

{% content-ref url="/pages/nZwMSx2sHkpUGpYsu5It" %}
[dLP Architecture](/radiant/project-info/rdnt-tokenomics/liquidity-provisioning/dlp-architecture.md)
{% endcontent-ref %}

One may bridge RDNT using the [Layer Zero OFT bridge](/radiant/project-info/rdnt-tokenomics/oft-bridge.md), providing ecosystem users with maximum flexibility to decide which chain yields will be more lucrative or to split their positions among chains.

To learn more about each chain, visit the project pages:

{% embed url="<https://ethereum.org/en/>" %}

{% embed url="<https://www.binance.com/en/bnb>" %}

{% embed url="<https://arbitrum.foundation/story>" %}

{% embed url="<https://www.base.org/>" %}

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.radiant.capital/radiant/project-info/rdnt-tokenomics/liquidity-provisioning/liquidity-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
