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

# Tokens we use

## Token standard

FlatQube uses a common standard for Everscale network tokens - TIP-3.1. The need to use TIP-3.1 tokens is due to the technical features of the Everscale blockchain, aimed at reducing transaction fees, increasing reliability and speed through dynamic sharding and P2P architecture. See TIP-3.1 for details. Here are some useful links:

{% embed url="<https://everscale-org.github.io/Standard/TIP-3/core-description>" %}

{% embed url="<https://broxus.medium.com/tip-3-1-token-guide-a13169ff6017>" %}

## Root contract

The token root contract stores general information about the token, e.g. name, symbol, decimals, token wallet code and so on.

## User contract

Each token holder has its own instance of a token wallet contract. Transfers happen in a decentralized fashion - a sender token wallet SHOULD send a specific message to a receiver token wallet. Since token wallets have the same code, it's easy for receiver token wallets to check the correctness of sender token wallets.

\\


---

# 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.flatqube.io/use/tokens/concepts/tokens-we-use.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.