Where creator fees go

The creator, another wallet, or a GitHub account

A creator can send their rewards to another wallet or a GitHub account once, at launch or later, then it is locked; every token page shows where they go.

By default, the creator

A token's creator rewards — the 0.5% fee share and any tax the creator set — go to the wallet that launched it. The creator may send them somewhere else once, either in the launch form or later from the token's page: to another wallet, or to a GitHub account. The new recipient is then permanent. Nobody can change it again: not the creator, not the recipient, not Bluu.

Changing the recipient changes who is paid, never who the creator is. The launching wallet keeps the reputation score, stays responsible for the token under the rug rule, and still cannot claim from its insurance pool.

What traders see

“Creator fees go to” sits beside the contract address on every token page, and in small on the Markets cards. Each links out in a new tab — to the explorer for a wallet, to the GitHub profile for an account.

Hammer — the creator's own wallet, the default.
Wallet — another wallet the creator named.
GitHub mark — a GitHub account, shown as @handle. Until its owner claims, it is marked “not endorsed until claimed”: anyone can name any account.
Lock — the one change has been made, so the recipient can never move again.

Claiming

Creator fees build up and are claimed, not sent on every trade. Everything you can claim is on one page, Claim, with what is ready now and what you have earned so far.

Robinhood Chain and Arc: fees are booked to whoever is the recipient at the time of each trade, and the recipient claims them in one transaction per chain. Fees from before the one change stay with the creator. A recipient chosen in the launch form is set in the launch transaction itself; on contracts deployed before that was possible, by a second confirmation straight after the launch.
Solana: Bluu's program holds the token's creator role, so Meteora's creator fees can only ever be paid to the recorded recipient. The page collects them for you, up to three tokens per transaction.
GitHub: the account's owner signs in with GitHub on the Claim page and claims, to a Bluu wallet the sign-in creates for them or to a wallet they connect (see collecting without a crypto wallet). Bluu's independent attestors each ask GitHub whose account it is, and once the required number agree the claim is paid at once — no waiting period. The wallet is bound for good, and later fees can be forwarded to it by anyone.

Where this stops

The one change cannot be undone. Name the wrong wallet and the fees go there for the token's whole life.
A recipient counts as one of the creator's own wallets: its selling counts towards a rug, and it cannot claim insurance on that token.
Fees held for a GitHub account that nobody claims for 30 days go to the site-wide insurance fund. Once the account has claimed, this never happens.
A GitHub account is identified by its permanent numeric id, not its handle, so whoever controls that account can claim. Losing the account means losing the fees.
Tokens launched before recipients existed keep paying their creator directly and cannot change.

By default, the creator

What traders see

Hammer — the creator's own wallet, the default.

Wallet — another wallet the creator named.

GitHub mark — a GitHub account, shown as @handle. Until its owner claims, it is marked “not endorsed until claimed”: anyone can name any account.

Lock — the one change has been made, so the recipient can never move again.

Claiming

Creator fees build up and are claimed, not sent on every trade. Everything you can claim is on one page, Claim, with what is ready now and what you have earned so far.

Robinhood Chain and Arc: fees are booked to whoever is the recipient at the time of each trade, and the recipient claims them in one transaction per chain. Fees from before the one change stay with the creator. A recipient chosen in the launch form is set in the launch transaction itself; on contracts deployed before that was possible, by a second confirmation straight after the launch.

Solana: Bluu's program holds the token's creator role, so Meteora's creator fees can only ever be paid to the recorded recipient. The page collects them for you, up to three tokens per transaction.

GitHub: the account's owner signs in with GitHub on the Claim page and claims, to a Bluu wallet the sign-in creates for them or to a wallet they connect (see collecting without a crypto wallet). Bluu's independent attestors each ask GitHub whose account it is, and once the required number agree the claim is paid at once — no waiting period. The wallet is bound for good, and later fees can be forwarded to it by anyone.

Where this stops

The one change cannot be undone. Name the wrong wallet and the fees go there for the token's whole life.
A recipient counts as one of the creator's own wallets: its selling counts towards a rug, and it cannot claim insurance on that token.
Fees held for a GitHub account that nobody claims for 30 days go to the site-wide insurance fund. Once the account has claimed, this never happens.
A GitHub account is identified by its permanent numeric id, not its handle, so whoever controls that account can claim. Losing the account means losing the fees.
Tokens launched before recipients existed keep paying their creator directly and cannot change.