> For the complete documentation index, see [llms.txt](https://docs.gofi.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gofi.cash/gofi-token.md).

# The GOFI token

GOFI is a membership token: owning it unlocks real services every month. It launches in a later phase; nothing in this section is live yet.

| Parameter                    | Value                            |
| ---------------------------- | -------------------------------- |
| Total supply                 | 1,000,000,000 GOFI               |
| Time to unlock benefits      | 5 days of staking or holding     |
| Revenue to buyback and burn  | 25% of monthly platform revenue  |
| Burn target                  | 450,000,000 GOFI (45% of supply) |
| Supply after the burn target | 550,000,000 GOFI                 |

## What GOFI does

* **Pay with it.** Buy eSIMs, virtual numbers and card top-ups with GOFI.
* **Stake it.** Staking (or holding) for 5 days unlocks the membership tier that matches the balance.
* **Benefit from usage.** Each month, a quarter of platform revenue buys GOFI on the market and burns it, until 450 million tokens are gone.

## The flywheel

1. People buy, stake or spend GOFI.
2. Their tier unlocks discounts, free plans and card benefits each month.
3. They use eSIMs, numbers and the card more.
4. More usage means more revenue.
5. A quarter of that revenue buys back and burns GOFI, shrinking supply toward 550 million.
6. The loop starts again at step 1.

The buyback is funded by service revenue, not by new token sales, so it only grows when real usage grows.


---

# 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://docs.gofi.cash/gofi-token.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.