> For the complete documentation index, see [llms.txt](https://dyorhq.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dyorhq.gitbook.io/docs/launchpad/fees-and-rewards.md). # Creator Fees & Holder Rewards Every launch chooses one of two fee modes at creation, and it can't be changed afterwards. | Fee mode | Shown as | Who earns the creator side | | ------------------------------------- | --------------------- | ----------------------------------------------------- | | **Share fees with holders** (default) | "Shared with holders" | Every holder, pro-rata to balance, claimable any time | | **To creator** | "To creator" | The launching wallet | The DyorHQ side is always 50% of the curve fee and early-buy tax; the creator side is the other 50% plus the whole creator tax. ## Where fees come from | Source | Rate | Phase | | -------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | | Curve trade fee | 1% | Bonding | | Early-buy tax | 98% (less the creator tax) / 25% / 3% / 0.3% in seconds 0–3 | Bonding | | Creator tax | 0–10% | Bonding, and on Uniswap v4 pool swaps after graduation | | Pool fee (Uniswap v4 hook) | 1% | After graduation on Uniswap v4 | | Pool fee (Monday Trade) | Monday's 1% tier | After graduation on Monday Trade: earned by the locked position and harvested by DyorHQ, **not** distributed to the creator or holders | ## Holder rewards (fee-sharing coins) If you hold a fee-sharing coin, your share of its fees accrues in the pair asset. * On the coin's page, **Your Holdings** shows **Pending rewards** and a **Claim Rewards** button. A **Queued for holders** line shows rewards that are one block away from being claimable.\ In **My Launchpad → Claimable Fees**, every fee-sharing coin with rewards ready to claim has a "TICKER rewards" row with a **Claim** button, plus **Claim All** when there's more than one thing to claim. * Rewards are settled to your balance before every transfer, so buying or selling never loses you what you've already earned. * After a Uniswap v4 graduation on the current launchpad, the holders' share of a pool swap's fee and creator tax (in the pair asset) goes to fee sharing in that same swap and becomes claimable a block later; only DyorHQ's part waits in the hook until the pool's fees are swept. On previous launchpads the holders' share also waits for that sweep. ## Creator fees (to-creator coins) If you launched a coin with fee sharing **off**, your curve fees are **paid straight to your wallet on every trade**. After a Uniswap v4 graduation, your share of the pool fee and the creator tax collect in the DyorHQ hook and reach your wallet when the pool's fees are swept, which anyone can trigger; the coin's page shows what's **Waiting for a sweep**. After a Monday Trade graduation there's nothing more to collect: the pool's 1% fee goes to DyorHQ. The fee escrow only comes into play if a payment can't be delivered; that amount is then booked as claimable: * On the coin's page, **Creator Fees** shows **Your claimable fees** and **Claim Creator Fees** (or "Nothing to claim yet, fees accrue as people trade your coin."). In the normal case this stays at zero because the fees already reached your wallet. * One claim sweeps undelivered fees across **all your launches paired in that asset** on the same launchpad. In **My Launchpad → Claimable Fees** you'll see one "Creator fees · \" row per pair asset and launchpad. ## Fee recipient changes * A creator can hand their fee stream to another address on-chain. * For abandoned launches, DyorHQ can propose a new recipient with a **3-day timelock** and a 3-day window to execute, the "community takeover" mechanism. The current recipient can cancel a pending takeover. --- # 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://dyorhq.gitbook.io/docs/launchpad/fees-and-rewards.md?ask=&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.