> For the complete documentation index, see [llms.txt](https://ai-pin.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ai-pin.gitbook.io/whitepaper/ai-pin-bitcoin-treasury.md).

# AI-PIN Bitcoin Treasury

To align $AI (AI-PIN)  with the long-term ethos of sound money and decentralized value, we are establishing an official **Bitcoin Treasury Reserve**. This initiative supports both the sustainability of the AIPIN ecosystem and the rewards for committed community members.

#### 🔹 Treasury Allocation

* 🔢 **Total Allocation**: 10% of $AI's total supply
* 🏦 **Treasury Reserve**: 10,000,000 $AI allocated for conversion into Bitcoin (BTC)

This treasury is not meant for selling AIPIN in large batches, but rather for a **controlled and transparent conversion into BTC** over time to build a strong, long-term reserve asset.

#### 🔹 Use of Treasury BTC

The BTC accumulated through AIPIN Treasury will be used for:

1. 💸 **Community Incentives** — including burn-to-earn campaigns
2. 🔐 **Protocol Reserves** — securing the ecosystem against volatility
3. 🧠 **R\&D Fund** — investing in AI Agent development or Bitcoin-native integrations
4. 🏅 **Sats Rewards** — rewarding AIPIN holders and stakers via sats airdrops

#### 🔹 Burn-to-Earn BTC Model

Every month, we allocate a fixed pool of Bitcoin (e.g., **0.005 BTC**) to reward AIPIN holders who **burn their tokens**.

**Burn Logic:**

* 🔥 AIPIN tokens are sent to a burn wallet:\
  `0x000000000000000000000000000000000000dEaD`
* 📊 The monthly BTC pool is distributed **proportionally** to the amount burned
* 🔒 Max BTC pool is **capped each month** to ensure sustainability
* 🧠 Users may get **more sats** if fewer people burn, and **less** if burn demand is high

#### 🔹 How It Helps AIPIN Ecosystem

| Benefit                | Explanation                                                                  |
| ---------------------- | ---------------------------------------------------------------------------- |
| 🔥 Supply Reduction    | Burned tokens lower circulating supply, potentially increasing token value   |
| 🟠 BTC Integration     | Ties AIPIN to the Bitcoin economy, increasing resilience and narrative power |
| 🧲 Community Growth    | Bitcoin rewards attract more users and long-term holders                     |
| 📈 Deflationary Impact | Aligns with long-term value creation and reduced inflation                   |

#### 🔹 Future Plans

* Integrate Lightning-based sats rewards (via Alby, Strike, BTCPay)
* Offer AIPIN staking options that yield BTC instead of native tokens
* Enable BTC-based AI Agent subscriptions and affiliate payouts

***

#### 📝 Transparency & Tracking

* All burns are trackable on-chain
* BTC rewards are distributed with full public disclosure


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://ai-pin.gitbook.io/whitepaper/ai-pin-bitcoin-treasury.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.