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

# Rewards

![How holder rewards work](https://899946093-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpV7Nql16MHxTtZSco9iM%2Fuploads%2FFLmVzjGZN78WNvo89uTG%2Frewards-explainer.svg?alt=media)

HoodSwaps is built on one idea: **the fees the platform generates flow back to the people who create the value — traders, holders, and creators — not to a middleman.**

Rewards are paid in **real ETH** (as WETH, 1:1 with ETH). They are *not* paid in the meme token itself, so they never dilute a token's supply or price — the ETH comes from actual trading fees.

## How a trade rewards everyone

Every token launched on HoodSwaps charges a small trading fee — the creator sets it between **1% and 3%**. That fee is split **automatically, inside the same transaction**, with no middleman and no manual step:

* **50% to holders** of that token, in ETH, weighted by how much they hold
* **25% to the creator**
* **25% to the platform**, which fuels **$CVNDLES** (below)

```mermaid
flowchart TD
  T["Trade on a HoodSwaps token — 1-3% fee, paid in ETH"] --> S{"Fee split (atomic, on-chain)"}
  S -->|50%| H["Token holders"]
  S -->|25%| C["Creator"]
  S -->|25%| P["Platform treasury"]
  H --> W["Your wallet — real ETH, auto-delivered"]
  P --> B["Fuel $CVNDLES rewards"]
  B --> HH["$CVNDLES holders — earn from ALL platform volume"]
```

## The two layers

**Layer 1 — hold a token, earn from its trades.** Every token you hold on HoodSwaps is a real-yield asset: as people trade it, 50% of the fees land in your wallet as ETH. You don't have to do anything (see *Auto-delivery* below).

**Layer 2 — $CVNDLES, the platform token — LIVE.** Holding **$CVNDLES** earns you a share of **all** platform volume — every swap on HoodSwaps — paid in real WETH. It's how you back HoodSwaps as a whole rather than a single token. **$CVNDLES is live now:**

* **Contract:** `0x601f3D58Da4199d13bD02Ccb18fCE0c2AdEeB6B2` (Robinhood Chain)
* **Buy it:** [hoodswaps.xyz/app](https://hoodswaps.xyz/app?token=0x601f3D58Da4199d13bD02Ccb18fCE0c2AdEeB6B2)
* Every swap's 0.25% fee is split **60% to $CVNDLES holders / 40% to the platform**, paid as WETH — funded by real volume, no token inflation.

## Auto-delivery — rewards just appear

You never have to hunt for a claim button. A keeper periodically pushes each holder's accrued ETH straight to their wallet, so rewards **land automatically**. A manual **Claim** is always available as a fallback — your rewards are yours on-chain the moment they accrue.

## Early days — the honest state

Rewards are a **share of real trading fees**, not printed tokens. That means they start small and grow with volume: the more trading flows through HoodSwaps, the more holders earn. It's real yield, so it's only ever as big as the activity behind it — sustainable, and never at the expense of the token's price.

## Points

As you trade and launch you earn **points** for activity — first trade, volume, claiming a handle. Points are a usage and status signal today; they climb the leaderboard. They are not a promise of tokens — the real reward is the ETH described above.

## The honest fine print

* Rewards are a share of **protocol trading fees**, paid in ETH/WETH. Nothing here is a dividend, a security, or a promise of profit.
* Fee sharing varies with real trading volume, which can be zero.
* Crypto is volatile and trading is risky. Always do your own research.


---

# 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://hoodswaps.gitbook.io/hoodswaps-docs/rewards.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.