# Distribution and emission

|                        |               |
| ---------------------- | ------------- |
| Token Ticker           | $BCA          |
| Token Contract         |               |
| Token Type             | *ERC-20*      |
| Total Supply           | 1,000,000,000 |
| Initial Supply         | 3%            |
| Token Generation Event |               |

## Token Allocation

<figure><img src="/files/mPeJBvLrbGvyYrQWwoV7" alt=""><figcaption></figcaption></figure>

## &#x20;Vesting and Details <a href="#perp-token-distribution" id="perp-token-distribution"></a>

<table data-full-width="true"><thead><tr><th width="202">Allocation</th><th width="117.66666666666669">From Total supply</th><th> Vesting</th><th>Details</th></tr></thead><tbody><tr><td><p></p><p>Token sale</p></td><td>10%</td><td>10% on TGE | 3 months cliff | Linear unlock over 12 months</td><td>Private and Public.  Possibility to keep allocation for future investors after launch. To be used for liquidity and listings. </td></tr><tr><td>Team &#x26; Advisors</td><td><p>15%</p><p></p></td><td>0% at TGE, 12 months cliff, daily release over 24 months. </td><td>4% goes to advisors, same vesting as the core team.  </td></tr><tr><td>Development</td><td>25%</td><td>0% on TGE, 3 months cliff<strong>,</strong> Linear unlock over 24 months</td><td><p></p><p>1.Web3- AI data infrastructure</p><p>2.Data marketplace </p><p>3.Layer 3 blockchain               </p></td></tr><tr><td>Liquidity</td><td>12%</td><td>Linear unlock over 36 months</td><td>50% for DEX, 50% CEX, subject to change. All liquidity on dex will be renounced  </td></tr><tr><td>Rewards &#x26; Staking</td><td>10%</td><td>0% on TGE, 3 Months cliff | Linear unlock over 48 months</td><td>Ecosystem and staking rewards for users, publishers, advertisers, LP providers.</td></tr><tr><td>Partnerships/Acquisitions/Marketing</td><td>15%</td><td>0% at TGE, 3 months cliff, linear unlock over 48 months</td><td>Used for Acquiring new ad networks and KOL/PR marketplaces.</td></tr><tr><td>User Growth pool/Airdrop</td><td>13%</td><td>Linear unlock over 48 months</td><td>A program for acquiring non-crypto natives.</td></tr></tbody></table>

##

## Token Emission Chart

<div data-full-width="true"><figure><img src="/files/a9DKipinhGECYWFnk1DR" alt=""><figcaption><p>Check in detail 👉<a href="https://docs.google.com/spreadsheets/d/1_u9XeQDoOQjMGsYGbuxku6wumCmaLIzKLjewiiGF0eU/edit?usp=sharing"> </a></p></figcaption></figure></div>

## **Deflationary Mechanism**

`A %` of the Network generated revenue are used to buy back and burn BCA. A mechanism that will be used to stabilize the supply of BCA in a unique buyback model.

Buyback rate, varying from 5% to 15% from the revenue, Dynamically adjusting based on data training revenue, market conditions, and the ecosystem's growth, ensuring sustainability and adaptability.

To calculate the percentage of funds from generated revenue ($$D\_r$$ - training Data revenue) that will be allocated to treasury buybacks ($$T\_{bb}$$), we utilize this formula:

$$
T
bb
​
\=B
r
​
⋅D
r
​
$$

* $$Tbb​$$ = Total amount allocated for buybacks.
* $$Br​$$ = Buyback rate, varying from 0.05 to 0.15.
* $$Dr​$$ = Revenue generated within the quarter.

To give an example of projected buyback treasury values, a total of $100,000 will be dedicated towards BCA buybacks assuming that quarter BCA generated $1 mill in revenue .

Buybacks will be made strategically and occur over weeks. The BCA bought back from the market will be burned every quarter.&#x20;


---

# 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.bcaprotocol.org/usdbca-token/distribution-and-emission.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.