# Tokenomics

### Initial Distribution (10% of total supply)

* Airdrop: 40%
* Team Allocation: 20%
* Treasury: 40%;

Tokens will be soul-bounded at the beginning. Not allowing for transfers except for in-game systems like staking, minting NFTs, or burning. This is designed to incentivize players and disincentivize traders.

### Inflationary Distribution (Rest) 

Once the initial distribution happens, RUBY will be minted by different mechanisms:

* Game Staking / Mining: 25% 
* LP: 35%
* Fights: 20%
* RUBY Stakers: 10%
* Team: 10%

Note: These quantities might be adjusted, please provide feedback in our Discord. 

#### Airdrop

The initial distribution will allow early Arbitrum NFT ecosystem projects, friends, and collectors to earn RUBY. The players that will qualify for the airdrop are:

* Players Airdrop: 20%
* CastleDAO owners airdrop: 40%
  * Generals
  * DefiHeroes
  * Castles
  * Ballot
* Community Airdrop: 40%
  * SmolBrains
  * FootyNouns
  * Arbidudes
  * REALM
  * Farmland
  * Mint your EGG
  * Arbibots
  * ToadsToolz
  * Tales of Elleria
  * Blueberry Club
  * Diamond Pepes
  * Battlefly
  * Mithical
  * Imbued Souls
  * The lost donkeys

### Deflationary Mechanisms

* Purchasing Booster Packs 
  * Percent burned / Percent sent to RUBY stakers
* Purchasing CastleDAO consumables & Items
  * Percent burned / Percent sent to RUBY stakers
* Initiating fights in the game
  * Loses will be burned
* SmolBrawlers Mint
  * SmolBrawlers Upgrades
* Other integrations


---

# 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://castledao.gitbook.io/castles/castle-protocol-v1/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.