> For the complete documentation index, see [llms.txt](https://etherfi.gitbook.io/etherfi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://etherfi.gitbook.io/etherfi/events/events/previous-seasons/season-2/s2-stakingfrens/gearbox-frens-may-4-8.md).

# Gearbox Frens (May 4-8)

From May 4 to May 8 2024

Introducing StakingFrens with Gearbox!

<figure><img src="https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2FdZHgE9m15YUIu55UF0Nd%2Fimage.png?alt=media&amp;token=112a7f39-e6b1-413e-8236-b34641ee8d6b" alt=""><figcaption></figcaption></figure>

## **Earn ETHFI plus $70k USD worth of GEAR rewards!**

Stake ETH while StakingFrens is on and earn ETHFI, from May 4 through May 8, 2024. Some conditions apply.

## How it works

1. Stake ETH in ether.fi during the event. The more you stake, the more ETHFI + GEAR you earn.\
   Earn 1 ETHFI for every 1 ETH staked, per day, from May 4 00:01 UTC until May 8 23:59 UTC, 2024
2. Automatically accumulate ETHFI rewards while you stake!\
   You'll see this displayed in your Portfolio, along with a "StakingFrens" badge confirming your participation in the event. This may take \~60 minutes to display for some users.\
   \
   ![](https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2Fkl1H9WOnS36EwmcKoycV%2Fimage.png?alt=media\&token=5bfa3021-44b9-41dd-a6fd-e4a01b5a4e9e)![](https://1029745181-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FG3Lk76lfvw9ecPIg0mK8%2Fuploads%2F7xXUlgKKPi00fY2JXvmP%2Fimage.png?alt=media\&token=e2355bb3-e5df-487a-9d1c-fefe5e6a02aa)<br>
3. At the end of the event, your ETHFI rewards plus allocation of the $70K USD worth of GEAR tokens will be automatically airdropped to you within \~10 days. No need to claim, no need to spend on gas. If you earn < 1 ETHFI, your amount earned will be automatically added to your Season 2 airdrop allocation!
4. **Existing stakers, we see you 👀**\
   For every ETHFI token earned during the StakingFrens event, ether.fi will match that amount to top up Season 2’s airdrop allocation for **all** S2 participants.\
   For example, if the total ETHFI awarded to people who staked during the event was 10,000, ether.fi would add 10,000 ETHFI tokens to the already planned 5% Season 2 airdrop allocation.

Stay tuned for more frens to come throughout Season 2!

## Conditions

* ETHFI and GEAR rewards are limited to the 100,000 ETH staked during the event
* GEAR rewards are limited to 4,268,292 GEAR tokens. \~$70K USD based on market value as of May 1, 2024
* ETHFI and GEAR tokens earned by stakers within the May 4-8 event period
* Any attempt to exploit loopholes or manipulate the rules to game the system will result in disqualification for this promotion and all of your points on all accounts will be removed


---

# 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://etherfi.gitbook.io/etherfi/events/events/previous-seasons/season-2/s2-stakingfrens/gearbox-frens-may-4-8.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.
