> For the complete documentation index, see [llms.txt](https://dca-1.gitbook.io/dca-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dca-1.gitbook.io/dca-white-paper/dca-whitepaper/ecosystem/token-issuance.md).

# Token Issuance

> *"DCA operates under a minting-based model without a fixed total supply, where issuance is dynamically driven by protocol activity and market conditions."*

## The Foundation of Commerce

In the DCA ecosystem, the protocol itself serves as the foundational layer for all commercial activity. Rather than existing as a separate financial tool, the DCA protocol is **embedded within the commerce process** — every transaction, every staking action, and every bond interaction is a protocol-level event.

This design ensures that as commercial activity grows, the protocol infrastructure scales alongside it.

## Dual Token Distribution

DCA employs a **dual distribution model** that creates two complementary pathways for token circulation:

### 1. Protocol Minting

New DCA tokens are minted by the protocol through controlled mechanisms:

* **Staking rewards** — Tokens are minted and distributed to stakers on a 12-hour rebase cycle
* **Bond issuance** — New tokens are minted when participants purchase bonds, expanding supply in proportion to treasury growth
* **Sales contract** — When market price exceeds backing value, the protocol may mint and sell tokens to capture demand

Protocol minting is always governed by treasury backing — each new token must be supported by a corresponding amount of treasury risk-free value (RFV).

### 2. Commerce-Driven Acquisition

In parallel with protocol minting, the commerce layer drives **market-based token acquisition**:

* Merchant profits from DCA Mall transactions are partially converted into DCA tokens through market purchases
* These acquired tokens are deposited into staking pools, removing them from circulation
* This creates sustained buy-side demand that is independent of speculative activity

## Economic Alignment

The dual distribution model ensures that token supply grows in alignment with real economic value:

| Distribution Path    | Source                     | Effect                      |
| -------------------- | -------------------------- | --------------------------- |
| Protocol Minting     | Treasury-backed issuance   | Controlled supply expansion |
| Commerce Acquisition | Merchant profit conversion | Market demand generation    |

Together, these mechanisms prevent the common DeFi failure mode where token emissions outpace value creation. In DCA, supply expansion is always **backed by either treasury reserves or real commercial activity**.

## Token Model

The DCA token operates with the following fee structure:

* **Buy fee:** 0%
* **Sell fee:** 5%

The sell fee is allocated as follows:

| Allocation                | Percentage |
| ------------------------- | ---------- |
| Operation and Development | 2%         |
| Community Development     | 1.5%       |
| Marketing Development     | 1.5%       |


---

# 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://dca-1.gitbook.io/dca-white-paper/dca-whitepaper/ecosystem/token-issuance.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.