> For the complete documentation index, see [llms.txt](https://docs.zerolend.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zerolend.xyz/airdrop-incentives/protocol-eligible-incentives.md).

# Protocol Eligible Incentives

This section explains how users can actively interact with ZeroLend ecosystem for potential incentives.

Protocol Incentives are airdrops provided by other protocols to encourage engagement and growth within their ecosystems. ZeroLend, operational across Ethereum, Linea, Blast, zkSync, Manta, and X Layer, benefits from these incentives. 

Engagement with ZeroLend and its integrated protocols enhances users' likelihood of receiving various incentives. 

As active participants in this thriving DeFi ecosystem, we are eligible for various airdrops and incentives from the protocols and networks we integrate. 

ZeroLend is committed to distributing **80%** of all airdrops directly to our stakers and liquidity providers, reinforcing our appreciation for their trust and investment in the platform. The other **20%** goes back into the development fund. 

## LRT Partners

Liquid Restaking Tokens (LRTs) allow users to unlock liquidity from their staked assets while still earning staking rewards.

ZeroLend provides dedicated markets for LRTs like Renzo. Users can supply their assets and earn rewards such as native supply yields, $earlyZERO tokens, LRT points, and Zero Gravity Points.

| LRT Partners   | Token | Integration Status |
| -------------- | ----- | ------------------ |
| Kelp DAO       | ✔     | Done               |
| Renzo          | ✔     | Done               |
| ether.fi       | ✔     | Done               |
| Puffer Finance | ✔     | Done               |
| Swell          | ✔     | TBA                |
| Bedrock        | ✔     | TBA                |

{% hint style="info" %}
Read further about different yield strategies with LRTs [here](broken://pages/C8ptiHMAY2Cj5cAtJ08A). 
{% endhint %}

## Data Feed Partners

Our lending and borrowing markets rely on high-fidelity price data from premium oracle networks like Pyth and Redstone. As a leading data customer driving significant value to their networks, Zerolend could qualify for such incentive programs as they roll out staking programs.

| Oracle Partners | Integration Status | Token |
| --------------- | ------------------ | ----- |
| Pyth            | Done               | ✔     |
| Redstone        | Done               | TBA   |

## Layer 2s 

As a lending market, we scale by deploying our money markets on other chains. ZeroLend is currently the leading lending market on a number of L2s. 

| Chain         | Deployment | Token |
| ------------- | ---------- | ----- |
| Linea         | Done       | TBA   |
| zkSync        | Done       | ✔     |
| Blast Network | Done       | ✔     |
| Manta Network | Done       | ✔     |


---

# 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.zerolend.xyz/airdrop-incentives/protocol-eligible-incentives.md?ask=<question>&goal=<user_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.