> 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/mechanism/staking.md).

# Staking

> *"Through staking, participants align with the ecosystem's long-term success."*

## Staking as Internal Coordination

Staking represents the primary form of internal coordination within the DCA ecosystem. When participants stake DCA tokens, they remove them from circulation and commit to long-term growth, receiving compounded rewards through automated mechanisms.

This reflects a cooperative outcome in game theory, where collective participation outperforms short-term individual actions. As staking increases, circulating supply decreases, improving market stability and network confidence.

## Staking Duration Structure

To support diverse participation strategies, the DCA protocol provides multiple staking durations:

| Type                 | Duration | Purpose                                          |
| -------------------- | -------- | ------------------------------------------------ |
| **Flexible Staking** | 0 days   | Liquidity accessibility with basic rewards       |
| **Fixed Staking**    | 90 days  | Short-term commitment with enhanced returns      |
| **Fixed Staking**    | 180 days | Medium-term alignment with higher yields         |
| **Fixed Staking**    | 360 days | Maximum commitment with highest reward potential |

This tiered structure balances liquidity accessibility with long-term commitment. Shorter durations provide flexibility, while longer lock periods strengthen supply stability and reinforce ecosystem confidence.

## Automated Reward Distribution

Staking rewards within the DCA protocol are distributed through an **automated on-chain mechanism** operating on a **12-hour cycle rebase**.

Key features of the reward system:

* All stakers receive rewards proportionally at a uniform rate, ensuring fairness and consistency across the network
* The system supports **automatic compounding**, allowing rewards to be continuously reintegrated into staking without requiring manual interaction
* This mechanism reduces operational friction while reinforcing long-term participation

## Reward Rate and Participation Dynamics

Yield in the DCA ecosystem is not solely driven by emissions. It depends on the relationship between reward rates and overall staking participation.

As the protocol matures and participation increases, reward rates can gradually decrease while maintaining attractive yields due to higher staking ratios. This reflects a natural shift from **incentive-driven growth** to **confidence-driven participation**.

## Reward Vesting and Acceleration

Once rewards are withdrawn, they enter a **180-day linear vesting schedule**. Users may accelerate the vesting process by burning a specified amount of the ecosystem token WBNB, allowing rewards to unlock earlier.

| Vesting Speed | WBNB Burn Ratio |
| ------------- | --------------- |
| 180 Days      | 0%              |
| 150 Days      | 5%              |
| 100 Days      | 10%             |
| 45 Days       | 20%             |
| 15 Days       | 25%             |

Vesting can be accelerated by burning WBNB based on the value of remaining unreleased tokens. Higher acceleration speeds require proportionally higher burn ratios.

Learn about [Protocol Infrastructure](file:///2028808/protocol-infrastructure/) — the economic engine behind DCA.


---

# 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/mechanism/staking.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.