TerminalPad
Connect wallet

Claiming your fees

If you launched a coin, 0.56% of every swap on it is yours. It does not expire, it does not need to be renewed, and it keeps accruing for as long as the coin trades — before the bond, through it, and after.

Where 0.56% comes from: every swap pays the pool's 1% fee; Rhea DCL keeps 20% of it as its protocol fee; the other 80% is earned by your coin's position, and 70% of that is yours. You also get back 70% of the 1% fee your own opening buy paid.

How to claim

  1. Connect the NEAR account that launched the coin, with a little NEAR in it for gas.
  2. Open the coin's page. The creator fees panel is visible only to you.
  3. Click the claim button. The panel sends the calls below for you, in one wallet prompt.

What happens underneath

Swap fees accumulate inside the Rhea DCL position, not in a balance with your name on it. Moving them to you takes:

  1. collect_fees(coin) asks Rhea to pay out the position's accrued fees — a removal of zero liquidity, which moves no principal — and books them: 70% to you, 30% to the protocol. Anyone can call it, including us, including a stranger. Whoever pays the gas, the split and the destinations are fixed in the contract.
  2. collect_extra_fees(coin), for a bonded coin only: the same, for the coin's second, tracker-only position (the bid band the bond creates — see The bond).
  3. claim_creator_fees(coin) sends your booked share to your account. Only you can call it.

The page shows both what has already been swept and what is still sitting in the position, so the figure you see is everything you are owed, not only the part someone has already moved.

What you get paid in

Both sides of the pair, because a swap fee is taken in whatever was swapped:

  • your own coin, and
  • the quote — USDC before the bond, the tracker after it. Fees swept during the bond itself are USDC. A tracker can be sold in its USDC pool, or redeemed for USDC at its NAV on the tracker's vault — at once when the vault holds enough idle USDC, otherwise through the vault's redemption queue while the keeper brings dollars back from the venue.

Each leg is paid separately. On NEAR a token can only be sent to an account registered on it: you are registered on your coin from its creation and on USDC because you paid in it, but to receive tracker fees your account must be registered on the tracker. A leg that cannot be delivered is put back on your books, untouched, and you can claim it again once registered.

Why nobody can redirect it

claim_creator_fees pays the creator written in the coin's launch record when the launch ran, and only that account can call it. There is no setter. The protocol's share goes to a treasury account fixed when the launchpad was deployed, also with no setter. Neither can be pointed anywhere else, by us or by anyone.

The one outside limit is USDC's own: Circle's USDC has a blocklist, and a USDC transfer to a blocklisted account fails. Your coin and tracker shares are unaffected by it.

Check the split yourself

The creator's share is a constant in the launchpad's code, not a setting:

CREATOR_SHARE_BPS = 7000     (70% of what the position earns)

and Rhea's cut is DCL's own protocol_fee_rate (2000, i.e. 20%, read on 2026-09-25; Rhea's DAO sets it, not us). Your booked-but-unclaimed share is public: creator_fees_of(coin) on the launchpad returns it per token, and the position's unswept fees are unclaimed_fee_x / unclaimed_fee_y in Rhea DCL's get_liquidity for the position.