> For the complete documentation index, see [llms.txt](https://docs.airpuff.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airpuff.io/airpuff/points-and-referrals/buff-boost.md).

# Buff Boost

To celebrate the launch of the AirPuff Points System, we are introducing Buff Boost from April 2nd to April 16th, 2024.&#x20;

During this period, for every 1 ETH deposited in the ETH lending pools (Ethereum / Arbitrum / Mode), you will receive 500 bonus AirPuff points or the proportionate amount. To prevent looping, the bonus points will be distributed in a lump sum after the Buff Boost ends, and only the net deposit will be eligible for the bonus points.&#x20;

But that's not all! We're boosting all AirPuff points by 2x for everyone during the Buff Boost. The 2x boost will be automatically applied, and your points will be updated daily.&#x20;

Sit tight and enjoy the Buff!


---

# 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.airpuff.io/airpuff/points-and-referrals/buff-boost.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.
