Creator fees, explained.Creator fees, explained.

tagd lets anyone launch a Solana token whose creator fees are routed to a named X account. Each fee is split as it is collected, and the recipient's share waits in the recipient vault until they sign in with X, accept the token and claim it.

Every recipient gets a fee wallet: a Solana wallet that only their X account can open. It is created the first time they sign in, claims are paid there, and tagd never holds its key. Until then their share waits in the vault, so a token can name anyone, even someone who has never heard of tagd.

The launch form has three modes:

• Launch creates a new token from your wallet.
• Register points the fees of an existing token you control at a recipient.
• Walletless gives you a one-time funding address, and tagd launches on your behalf.

You can add a deployer reward of up to 10% of collected fees. It comes out of the recipient share, so the live preview updates as you type.

Each fee is split when collected: 65% recipient pool, 10% treasury, and 25% $TAGD buyback and burn. A 10% deployer reward leaves 55% for the named recipient.

1. 01

   Fees accrue

   Each collected fee is recorded against the recipient named by the token.

2. 02

   Sign in

   Sign in with the recipient account. A wallet address alone does not prove eligibility.

3. 03

   Request

   Choose one allocation. It is paid to your fee wallet, or to any Solana address you enter and confirm.

4. 04

   Track

   Follow it through queued, processing, submitted and confirmed. Only confirmed means final.

Not available yetRecipients will be able to set a minimum once. When a balance passes it, the claim is paid to their fee wallet automatically, or to another address they choose.

Either way, amounts under $1.00 stay in the vault and add to later fees, so nobody pays more in network costs than they receive.

Each allocation has its own 90-day window, which starts when it becomes claimable. A new allocation does not extend an older one, and the claim page shows the days left on each. A request made in time keeps its allocation, even if processing finishes later.

If a recipient declines or a window ends, the fees follow the token's fallback rule. The deployer chooses it at launch, and it cannot change afterwards:

• Buy and burn this token buys the token on the open market and burns it.
• Donate to public goods sends the fees to a published public-goods wallet.

Neither option pays tagd or the deployer, so nobody earns more when a recipient fails to claim.

A token can name an account before its owner knows about it, so being named is never treated as agreement. Every token shows one of three states:

• Not yet accepted: named by the deployer, with no response from the owner.
• Accepted: the owner signed in and agreed to receive fees. It does not endorse the token's value.
• Declined: the owner refused, and unpaid fees follow the fallback rule.

Proof of Funds places every collected dollar in one line of a public ledger, so the total must equal what was collected. Money owed to recipients, fallback rules and buybacks sits in separate vaults from the treasury.

The buyback share buys $TAGD on the open market, then burns it. Funding and burning are separate stages, so a pending allocation has not reduced supply yet. Each run is listed on Analytics, including failed ones.