> For the complete documentation index, see [llms.txt](https://trywink.gitbook.io/wink/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://trywink.gitbook.io/wink/crypto/like-tokenomics.md).

# LIKE Tokenomics

Tokenomics is the study of how a utility token operates within a platform. The value of digital assets is determined by their supply and demand dynamics; when demand exceeds supply, prices increase.

To sustain the value of the platform's native token, deflationary factors must outweigh inflationary ones. Additionally, the platform must offer value beyond token rewards to users. In essence, platform's revenue-driven token buybacks should exceed the token outflow for user rewards. In addition to implementing a buyback mechanism, there should be additional utilities that confer direct usage of the token within the application. This all is, Wink's vision for LIKE.

Read more about [LIKE utilities](/wink/crypto/like-token-utility.md), or dive into LIKE's tokenomics below:

1. [Basic Information](/wink/crypto/like-tokenomics/basic-information.md)
2. [Release Schedule](/wink/crypto/like-tokenomics/release-schedule.md)
3. [Token Allocation](/wink/crypto/like-tokenomics/token-allocation.md)
4. [Wallets](/wink/crypto/like-tokenomics/wallets.md)


---

# 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://trywink.gitbook.io/wink/crypto/like-tokenomics.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.