# Tokenomics

## PST Token Overview

| Parameter              | Value                        |
| ---------------------- | ---------------------------- |
| **Token Name**         | PENGU Strategy Token         |
| **Symbol**             | PST                          |
| **Total Supply**       | 1,000,000,000 PST            |
| **Additional Minting** | Not possible                 |
| **Standard**           | ERC-20 (Abstract compatible) |
| **Decimals**           | 18                           |

## Supply Distribution

**100% Fair Launch - No Pre-allocation**

* **1,000,000,000 PST** (100%) added to liquidity at launch
* **0 PST** reserved for team
* **0 PST** reserved for private sales
* **0 PST** reserved for marketing
* **0 PST** reserved for development

## Deflationary Supply

* No minting. Supply only decreases.
* 100% of all PENGU sale proceeds buy back and burn PST.
* Burned tokens are permanently destroyed (sent to dead address).
* Each buyback makes PST scarcer.

All tokens were made available to the public from day one through decentralized liquidity pools.

## Fair Launch Mechanics

### Dynamic Fee Launch System

PENGU Strategy launched with a unique anti-bot mechanism:

* **Starting Fee:** 95% on all transactions
* **Fee Reduction:** Decreased by 1% every minute
* **Final Fee:** 10% (current operational fee)
* **Launch Duration:** 85 minutes to reach final fee structure

This approach ensured:

* Protection against MEV bots and snipers
* Fair price discovery for all participants
* Gradual transition to sustainable fee structure


---

# 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://pengu-strategy.gitbook.io/pengu-strategy/tokenomics.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.