# Token Utility

Learn how PROOF architects rug-resistant launches, through supply distribution, vesting timelines, strategic lockups, and multisig-controlled reserves. Together, these measures ensure accountability, long term protection, and a safer launch for the community.

***

### Token Details

| Category           | Details                                      |
| ------------------ | -------------------------------------------- |
| Chain              | Solana                                       |
| Total supply $GRAM | 1,000,000,000                                |
| Contract address   | JA5mHRoGXNvjfBQPYzhnoENLiVhZPhkKg2nxzx2xvaQT |

***

### Supply & Controls

#### Liquidity

Added directly to the DEX at launch, with liquidity locked to protect holders.

| Detail         | Value            |
| -------------- | ---------------- |
| Liquidity Lock | Minimum 730 days |

***

#### Strategic Reserve

Locked for 6 months, followed by a 12 month linear vesting. No supply enters circulation until month 6.

| Detail      | Value                   |
| ----------- | ----------------------- |
| Lock Period | 6 months                |
| Vesting     | 12 month linear vesting |

***

#### PROOF-Supervised Multisig

Held in a multisig that requires PROOF approval for any movement, ensuring strict oversight and long term accountability.

***

### Team Allocation

| Allocation | Details                                        |
| ---------- | ---------------------------------------------- |
| 25%        | Long lock up - 6 month cliff and 12 month vest |
| 8%         | Gnosis multisig with Proof sign off            |
| 2%         | Team float for day to day operations           |


---

# Agent Instructions: 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:

```
GET https://blockgram.gitbook.io/blockgram-docs/tokenomics/token-utility.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.