# $PILSO Token Breakdown

The $PILSO token powers the PILSO OS ecosystem — aligning incentives between early adopters, contributors, and future users of AI-secured onchain operations.

$PILSO launching with a stealth, fair approach: no private rounds, no VCs, and no presales. This ensuring a clean and long-term alignment — setting the stage for a truly decentralized infrastructure layer for LLMs.

### $PILSO Token Details

| Token Name   | PILSO OS                     |
| ------------ | ---------------------------- |
| Token Ticker | $PILSO                       |
| Total Supply | 100,000,000                  |
| Chain        | Ethereum                     |
| DEX          | UniswapV2 (WETH/$PILSO pair) |
| Mint         | None — fixed supply          |
| Taxes        | 5% buy tax - 5% sell tax     |

### Allocation Breakdown

| Category                 | % of Supply | Notes                                   |
| ------------------------ | ----------- | --------------------------------------- |
| Liquidity (TGE)          | 75%         | Locked liquidity on Uniswap for 1 year. |
| Marketing                | 10%         | 50% vested over 1 year.                 |
| Development              | 5%          | 75% vested over 1 year.                 |
| Ecosystem                | 5%          | 75% vested over 2 years.                |
| Reserves / Future Growth | 5%          | 100% vested over 2 years.               |


---

# 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://docs.pil.so/pilso-token-utility/usdpilso-token-breakdown.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.