> 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/badges.md). # Badges Ether.fi Badges serve as Loyalty Point recognition, highlighting accomplishments and contributions of users within the protocol ecosystem. Each badge is uniquely designed for active eETH/weETH holders and participation in ether.fi community and events. There are two types of badges, variable and static. The variable badges have levels that you can unlock as you progress or stake more, where static badges are a one of kind badge that's unlocked by a certain action. As variable badges can increase with progress / more ETH staked, the same holds true if there is a reduction in the eETH/weETH held by the wallet. This means that points can go down by the same proportional amount. For static badges, they will remain as long as there is eETH/weETH held in the associated wallet. [**See your Portfolio tab**](https://app.ether.fi/portfolio) for current available badges --- # 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/badges.md?ask=&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.