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

# $VEIN token

**$VEIN** is the token associated the BITE VEIN STUDIOS company as a whole and not to a single game. It follows the **ERC-20 standard** and it has been created, minted, and distributed by BITE VEIN STUDIOS to represent our products.

* The $VEIN token is a governance token that allows owners to receive a **30% of the commissions of the marketplaces** of all our games as "dividends".<br>
* **We support the players community.** Players will be able to own a part of the company without making any investment thanks to the prizes allocated for e-sports.<br>
* Owners of the token will also have preference and **discounts on presale** for future game launches as well **as air-drops** of existing games.<br>
* The holders of the governance token will have access to **our staking system.**<br>
* The governance token will also count **as a voting voice for the proposals** presented by the BITE VEIN STUDIOS team.<br>
* Content creators **will be rewarded for their creations**.


---

# 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.biteveinstudios.com/tokenomics/vein-token.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.