> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/sonic-tokenomics/rewards-and-claims.md).

# Rewards & Claims

Canonical Creator Rewards allocation, entitlement lifecycle, claim settlement architecture and fee-domain separation including SONIC's 2% Token-2022 transfer fee policy.

Creator Rewards are a fixed allocation domain of **10% = 1,844,600,000 SONIC**.

{% hint style="info" %}
The Creator Rewards allocation is program funding, not a promise that every participant, leaderboard entry, token holder or social interaction is financially entitled to SONIC.
{% endhint %}

## Entitlement rule

Leaderboard position, social engagement, token ownership, community participation, points, reputation or campaign activity may be inputs to a reward program, but none creates a financial entitlement by itself.

A reward requires both:

1. **eligibility** under a versioned reward program; and
2. **a funded allocation** recorded for the eligible recipient.

## Canonical lifecycle

```
ESTIMATED → ELIGIBLE → ALLOCATED → CLAIMABLE → SUBMITTED → CONFIRMED → SETTLED → RECONCILED
```

| State      | Meaning                                                     |
| ---------- | ----------------------------------------------------------- |
| ESTIMATED  | Non-binding forecast, score or projected reward             |
| ELIGIBLE   | Program criteria satisfied; no funded entitlement yet       |
| ALLOCATED  | Funded amount recorded for an eligible recipient            |
| CLAIMABLE  | Claim conditions satisfied and claim path enabled           |
| SUBMITTED  | Transaction submitted                                       |
| CONFIRMED  | Required confirmation/finality threshold reached            |
| SETTLED    | Expected effects verified and ledger finalized exactly once |
| RECONCILED | Chain state, reward ledger and accounting agree             |

A transaction signature alone is not settlement proof.

## Funding boundary

The **1,844,600,000 SONIC Creator Rewards allocation** is the maximum allocation domain. It is not automatically circulating, claimable or owed supply.

Implementations should persist the reward program/version, eligibility decision, funding source, allocated atomic amount, recipient identity, claim conditions, transaction intent, signature, confirmation state, effect-verification result, settlement identity and reconciliation result.

SONIC uses **9 decimals**, so reward accounting should use integer atomic units and explicit decimal-safe conversions.

## Fee separation

Applicable reward transfers must account for fee domains independently.

| Fee domain                   |          Current policy |
| ---------------------------- | ----------------------: |
| Token-2022 transfer fee      |        **2% / 200 bps** |
| Marketplace service fee      | **3% where applicable** |
| SONIC Swap service fee       |        **2% / 200 bps** |
| Solana network fee           |                Variable |
| Priority fee                 |                Variable |
| DEX / routing / provider fee |        Provider-defined |

The Token-2022 transfer fee is a token-level transfer mechanic. It does **not** mean a Creator Rewards claim also carries the Marketplace or Swap service fee. Apply only the fee domains relevant to the operation and quote them separately before wallet signature where user authorization is required.

The transfer-fee rate may not exceed SONIC's **5% / 500 bps policy cap**. The Token-2022 absolute maximum fee amount is a separate deployment value and remains TBA.

## Claim execution contract

```
eligible creator
+ funded allocation
+ CLAIMABLE state
+ authenticated session
+ verified recipient wallet
+ versioned claim policy
→ durable claim intent
→ wallet authorization where required
→ Solana submission
→ confirmation / finality
→ expected-effect verification
→ exactly-once settlement
→ reconciliation
```

Retries may create new transaction attempts but must never create a second reward allocation or double settlement.


---

# 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://sonic-ai-works.gitbook.io/sonic-networks-docs/documentation/sonic-tokenomics/rewards-and-claims.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.