> For the complete documentation index, see [llms.txt](https://whitepaper.xtrip.travel/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.xtrip.travel/game-fi/daily-cap-of-tokens-earned-and-travel-distance.md).

# Daily cap of Tokens earned and Travel Distance

### Daily Token Cap

Daily Token Cap determines the maximum number of tokens users can earn. \
It depends on the number and type of Transportation NFTs users own. 

<figure><img src="/files/cUhlgLKavrkOtwM9LmNl" alt=""><figcaption></figcaption></figure>

E.g: \
If a user has 2 Shoes NFTs and 1 Bicycle NFT, the Daily Token Cap is:\
Daily Token Cap = 30 XTR + 30 XTR + 60 XTR = 120 XTR.\
\
**Currently, Daily Token cap can be increased up to 600 XTR**.

### Daily cap of Travel Distance

\
Total Travel Distance users can will be determined by total distance of NFTs users have.\
\
E.g.: If a user has \
Shoes: Distance 3 KM\
Shoes: Distance 4 KM\
Bicycle: Distance 10 KM\
The user can travel up to 17 KM with full ability.


---

# 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.xtrip.travel/game-fi/daily-cap-of-tokens-earned-and-travel-distance.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.