> For the complete documentation index, see [llms.txt](https://whitepaper.octo-gaming.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.octo-gaming.com/pure-gaming-elements/about-golds/how-to-get-golds.md).

# How to get Golds?

Golds can be obtained in different ways: 

* During 1V1 games: After choosing which game you want to play, you will have the option to bet 1, 5, 10, 20, 50, 100 or 200 Golds against another player. The winner of the game wins the pot.

  Example: If you decide to bet 100 Golds on Flappy Octo and you manage to make a better score than your opponent, then, you win his Golds and go from 100 Golds to 200 Golds
* By following us on social networks and taking various actions
* By integrating the ranking of the week. Each week, the players who have played the most games on the application are rewarded. The first one wins 200 golds, the second one 160 golds, the third one 140 golds, the fourth one 120 golds and the fifth one 100 Golds. This mechanism rewards the most active players on the app, not just the best players
* By watching rewarded video ads, you can go from 0 Golds to 100 Golds


---

# 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://whitepaper.octo-gaming.com/pure-gaming-elements/about-golds/how-to-get-golds.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.