# Tokenomics

The total supply of $WEB is allocated among the community, ecosystem growth, liquidity, and the core team. 

<figure><img src="/files/9VWuEPe82J8H0vhGg7LA" alt=""><figcaption></figcaption></figure>

Below is the breakdown:&#x20;

* **Community Airdrop** (45%):
  * 45% of the total supply will be distributed to **Radbro Webring NFT** holders, on both ETH and SOL.&#x20;
    * The tokens distributed to ETH tokens will be migrated to ETH from SOL via Wormhole. These will be vested via "Radbro-Style" token Emission, meaning Radbros, Radcats. and SchizoPosters will *emit* tokens on a vesting schedule over the course of a year. NFT holders can periodically claim tokens from a vesting contract.
    * Tokens distributed to SOL holders will be vested via Streamflow. **Streamflow Link**:
  * 15% allocation will be unlocked at launch.
    * The remaining 30% allocation will be distributed over the following 12 months.&#x20;
* **Liquidity Pool** (10%):
  * 10% of the supply is reserved for providing liquidity on Raydium.
  * This liquidity will be permanently locked.
* **Ecosystem Growth** (35%):
  * 35% is allocated to the Ecosystem Growth Treasury.
  * This allocation is designated for community incentives and initiatives that foster growth within the Webring AI ecosystem.&#x20;
  * This allocation will be locked under a 3-year vesting contract.
* &#x20;**Team** (10%):&#x20;
  * This allocation will be locked under a 3-year vesting contract.

<br>


---

# 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://radbro-webring.gitbook.io/webringai/project-token/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.