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

# TOKENOMICS

0x00096697dc24bd10423690126d91546a20ccb3f0

**Token Ticker:** $VPT 

**Token Network:** Base 

**Token Standard:** ERC20

**Token Utility:** The token has three main utilities:

1. Holders get access to the products (token-gated membership), vote on platform decisions about risk, claims and updates
2. Projects get insurance coverage by depositing $VPT into an insurance pool and earn rewards on top of that
3. And it will also act as a Revenue share vehicle with so called token ageing approach, meaning, revenue share for holder increases based on token holding duration

**Total Supply:** 1,000,000,000 

**Initial Circulating Supply:** 85,389,610 (8.54%)

**Initial Implied Market Cap:** $597,727.27 (w/o liquidity $247,727)

<figure><img src="https://541736356-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUFhgIP5fPj0D5R0MmvSp%2Fuploads%2FwA78NXL9ogpqsvO1jjJf%2Fimage.png?alt=media&amp;token=b06e4197-94ea-4c0b-acbb-22445473f2a3" alt=""><figcaption></figcaption></figure>


---

# 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.veritasprotocol.com/veritas-protocol/tokenomics.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.