> For the complete documentation index, see [llms.txt](https://docs.neverland.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.neverland.money/dust-incentives.md).

# DUST Incentives

The **DUST Incentives System** distributes protocol rewards to users who participate in Neverland’s lending markets and governance.

Rewards are generated continuously from supplying and borrowing activity across the protocol and are allocated transparently through the emission controller.

This system is designed to strengthen user participation in both the **lending markets** and **governance**, rewarding those who contribute liquidity or maintain long-term commitment through veDUST.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Overview

Every market in Neverland, including the isolated markets, is connected to the **DustRewardsController**, which tracks reward emissions and accruals for each user based on their supply and borrow balances.

The system continuously distributes DUST to active participants, aligning incentives for suppliers, borrowers, and governance participants.

Each market side carries its own emission rate, and your share of it scales with your balance.\
The more you contribute supplying or borrowing, the larger your share of rewards.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">How Emissions Work

1. **Emission Source**

   <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">DUST rewards are distributed across Neverland’s **supply and borrow markets**.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Each supported asset has a defined emission rate, which determines how many DUST tokens are emitted per second to that pool.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Supply and borrow emissions may differ based on governance settings or liquidity priorities.
2. **Reward Accrual**

   <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Rewards accrue automatically as users supply or borrow assets.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">The controller tracks each user’s share relative to total market activity.
3. **Claiming Rewards**

   <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Users can claim their accrued DUST rewards directly through the app.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Upon claiming, users can decide how to handle their rewards: lock them into a new time-lock, add to an existing lock, create an infinite lock, or withdraw with a penalty for immediate liquidity. The longer the commitment, the smaller the penalty.

Emissions are distributed fairly and proportionally to each user’s participation.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Claiming Options

Users can choose between several ways to handle their accumulated DUST rewards:

<table><thead><tr><th width="164">Option</th><th>Description</th><th width="157">Penalty</th><th width="244">Ideal For</th></tr></thead><tbody><tr><td><strong>Create New Lock</strong></td><td>Claim rewards into a new veDUST with a chosen duration (1 month – 1 year).</td><td>0–40%, lower for longer locks</td><td>New governance participants</td></tr><tr><td><strong>Add to Existing Lock</strong></td><td>Add claimed rewards to an existing veDUST with at least 28 days left.</td><td>0–40%, based on the lock’s time left; none for an infinite lock</td><td>Users consolidating voting power</td></tr><tr><td><strong>Create Infinite Lock</strong></td><td>Claim rewards into an infinite veDUST (1:1 voting power, no decay).</td><td>None</td><td>Long-term governance holders</td></tr><tr><td><strong>Direct Transfer</strong></td><td>Claim as liquid DUST to your wallet.</td><td>50%</td><td>Users needing liquidity</td></tr></tbody></table>

#### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Timed-Lock Claim Pricing

A claim routed into a timed lock pays a penalty that falls linearly with the commitment, starting at **40%** at the 28-day minimum. For commitments shorter than 358 days it is:

$$
P\_{\text{claim}} = A \times 40% \times \frac{t\_{\text{max}} - c}{t\_{\text{max}} - t\_{\text{min}}}
$$

Where:

$$
\begin{aligned}
A &= \text{DUST claimed} \\
c &= \text{time left until the unlock time (the commitment)} \\
t\_{\text{max}} &= \text{365 days} \\
t\_{\text{min}} &= \text{28 days}
\end{aligned}
$$

Once the commitment reaches 358 days, one week short of the one-year maximum, the penalty drops to **zero**, the same as for an infinite lock.

<table><thead><tr><th width="260">Commitment</th><th>Claim penalty</th></tr></thead><tbody><tr><td>5 weeks</td><td>about 39.2%</td></tr><tr><td>3 months</td><td>about 32.5%</td></tr><tr><td>6 months</td><td>about 21.7%</td></tr><tr><td>9 months</td><td>about 10.8%</td></tr><tr><td>358 days or more, or infinite</td><td>0%</td></tr></tbody></table>

New locks are measured to the unlock time after it is rounded down to the week, so the real commitment can be up to a week shorter than the duration you pick, and a duration that lands under 28 days after rounding is not accepted. When adding to an existing lock, the commitment is the time that lock has left. Opening a new lock from a claim requires at least 10 DUST after the penalty, and adding to an existing lock at least 1 DUST.

***

#### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Claiming Flow

<figure><img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fc2uY6IdZ79Pw4yyp5nZD%2F4.png?alt=media&amp;token=e0fdc87f-0c02-40b2-a051-fdcebfb4ef51" alt=""><figcaption></figcaption></figure>

Each option is fully on-chain, with rewards distributed from the emissions vault through the **DustRewardsController** and **DustLockTransferStrategy** contracts.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Penalty Logic

When choosing **direct transfer** (claiming without locking), a penalty is applied to discourage short-term extraction. The penalty is a fixed **50%**.

<img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">The user receives 50% of the claimed DUST as liquid tokens.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">The remaining 50% is sent to the protocol’s **early-exit burn wallet**, where it gets burned.

Penalties on timed-lock claims follow the same route. This structure aligns emissions with long-term participation and reduces circulating supply over time.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Integration with Governance

The DUST Incentives system works alongside veDUST governance:

<img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Users who lock DUST as veDUST gain **voting power** in governance.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">Locked users also receive a share of protocol revenue.

Together, this creates a continuous flywheel between **liquidity**, **governance**, and **emissions**.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Key Characteristics

<img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Activity-driven emissions:** Rewards are generated directly from lending pool participation.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Automatic accrual:** Rewards accumulate seamlessly as users supply or borrow.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Flexible claiming:** Four claim options to match user preferences.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Penalty-aligned:** Direct claims reduce supply and strengthen token value.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Governance-integrated:** veDUST holders steer the protocol.\ <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-68c76a6b902c12f9d24356c98f186dc875172d77%2Fbullet_star.png?alt=media" alt="" data-size="line">**Composable architecture:** Designed to work across all Neverland markets.

***

### <img src="https://3611561064-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWsM8j790KEBUuc1aV7HE%2Fuploads%2Fgit-blob-2325c76ba770d49fce56f639267a8bb00ed178f7%2Fmain_stars.png?alt=media" alt="" data-size="line">Summary

DUST emissions are distributed to those who make Neverland function: suppliers and borrowers; they also empower governance participants.\
Every action in the protocol earns DUST rewards, and every claim choice influences both personal and ecosystem growth.

By combining activity-based emissions with veDUST governance, Neverland creates a sustainable incentive model that rewards liquidity, strengthens governance, and reinforces long-term alignment between users and the protocol.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.neverland.money/dust-incentives.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
