> 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/archive/introduction/loyalty-points/referrals.md).

# Referrals

This referral program covers ETH deposits on Ethereum mainnet and L2s at app.ether.fi. Each 0.1 ETH staked via ether.fi earns the person who stakes and the person who referred 10000 loyalty points.

**Note**: Referral points may take up to 2 hours to display in your Portfolio.

### Referrals on ether.fi

Referrals are now live for ether.fi eETH staking! You can generate your referral link by connecting your wallet on [https://www.ether.fi](https://www.ether.fi/) and then navigating to the portfolio page where you'll find a button to generate the link.

On sharing your link with your friend, they should see a confirmation message when they stake ETH.

For every 0.1 ETH staked, you and your friend will both earn 10,000 loyalty points!

Happy staking and remember to spread the cheer to everyone!

### Other notables

The protocol reserves the right to review and remove any instances of users gaming the referral point program. This program is meant to promote the ecosystem and is not designed for users to gain an unfair advantage through wallet manipulation tactics.


---

# 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/archive/introduction/loyalty-points/referrals.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.