> For the complete documentation index, see [llms.txt](https://docs.imaginaryones.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imaginaryones.com/how-to-get-bubble/3.-farm-for-bubble.md). # 3. Farm for $BUBBLE ### UPDATE: $BUBBLE farming season 1 has officially concluded! $BUBBLE is for mass adoption. That's why we have opened up $BUBBLE to everyone. You can farm for $BUBBLE via: * Social: Complete social tasks * Gaming: Play games It's our strategic approach to facilitate mass adoption and engagement in our Web3 entertainment ecosystem. #### 1. **Diversification of Participation** By providing two different methods to earn $BUBBLE, we want to cater to a broader audience. Some users might prefer social interactions and tasks, while others prefer gaming. This inclusivity ensures that we reach a broader demographic that can participate in and benefit from the ecosystem. #### 2. **Community Building and Engagement** Engaging in social tasks and gaming creates a sense of community among participants. It encourages users to interact, collaborate, and compete, fostering a vibrant and active community centered around $BUBBLE and our entertainment ecosystem. --- # 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.imaginaryones.com/how-to-get-bubble/3.-farm-for-bubble.md?ask=&goal= ``` `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.