Protocol specification

01 / Overview

Tagg converts a token's creator fees into dollars at an X handle. A deployer tags @use_tagg with an image, a name, and the handle to pay. Tagg creates the coin on pump.fun (Solana) and sets the fee recipient to the Tagg treasury. The metadata description is the source of truth for who is paid.

Fees accrue as the token trades. Tagg claims them on a schedule. Each claim is keyed on its transaction signature. 80% is paid through X Money from a pre-funded float. 20% is spent buying $TAGG and burning it. There is no discretionary override.

The named handle is not a customer. There is no account to create and no wallet to connect. X Money remains the control plane for who can receive. Direct removal is section 13.

1. 01Fee direction: 100% of creator fees assigned to the treasury, permanently. §03
2. 02Recipient line written into token metadata. §04
3. 03Indexer observes the on-chain config and registers the mint. No approval queue.
4. 04Claim tx collects accrued fees. Obligation is computed once, at claim time.
5. 05Recipient share settles in USD via X Money. Public reply confirms the payout.

02 / Venue

Tagg is Solana only. pump.fun is the only launchpad. BNB, Ethereum, and other venues are not supported.

03 / Directing fees

End state: Tagg is the sole fee recipient on the mint, permanently. Partial shares are rejected — a published payout would then be an unknowable fraction of what the mint earned. A mutable pointer is a withdrawn promise.

On pump.fun, direction happens after create_v2. Tag launches write the Pump Fees sharing config as one shareholder at 10000 bps, then revoke authority. Manual launches use the fee-sharing screen (max 10 wallets): treasury at 100%, then revoke. Detected without revoke is not payable.

External fee proof: fee-sharing admin signs a Solana Memo and submits the signature. Memo program MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr. Admin must be a required signer.

The memo is not sufficient. Verifier also requires a finalized config: one 100% Tagg shareholder and revoke set. This proves routing and fee-admin control, not original creator identity and not an X Money payout.

Directing creator fees to the treasury is acceptance of the Terms of Use by the deployer.

04 / Naming the recipient

Recipient is parsed from token metadata description. Tag launches write this exact UTF-8 line:

Self-launches must include that line, substituting the handle. Fees to and via UsePaid bracket the handle so only one parse is valid when several accounts appear in the text.

The recipient does not pre-consent. A mint can be created for a handle that has never heard of it.

05 / The 80/20 split

Computed per claim, at claim time. No tiers. No negotiation.

06 / How claims work

Fees accrue to the treasury and sit until claimed. Per-trade claims would spend more in tx fees than a quiet mint collects. The ledger key is the claim signature: a claim cannot be recorded twice, and every obligation traces to one on-chain event. Recipient and protocol amounts are frozen at that moment.

Failed claims (halt, RPC, revert) create no obligation and are retried. Accrued fees remain on chain.

Payout milestones

Recipient balance is sent when it crosses, in order: $5 $10 $20 $50 $100 $250 $500 $1000, then every $1000. Each crossing pays the full balance. Sub-milestone balances do not expire for a resolved recipient. Unopened X Money still receives a claimable payment (usually 14 days). §09.

07 / Getting your fees

If a mint named your handle, the obligation is already yours. No form. Paid at the next milestone, X Money open or not.

1. 01A tag or a self-launch writes your handle into metadata.
2. 02Trades accrue creator fees. Scheduler claims them.
3. 0380% leaves the float over X Money.
4. 04@use_tagg posts a public confirmation.

Receipt does not make you a Tagg customer or a promoter of the mint. Amounts may be taxable. Tagg does not issue tax documents. Where law requires KYC before paying, the share is held until that resolves.

08 / X Money setup

Settlement rail is X Money. Open-to-receive is configured on X. Tagg cannot open or mutate that account.

09 / Unclaimed payments

Any X account can be named. If X Money is open, deposit is automatic. If not, X holds a claimable payment and notifies the handle. The window is X's. Expired funds return to the sender.

10 / Public confirmation

Every payout is announced by @use_tagg: amount and source mint. Most recipients were not asked in advance; the reply is the first public record they and their audience can check.

11 / Treasury

Everything is Solana. Fees are claimed into the treasury on Solana. $TAGG trades on Solana. Recipient share does not touch a bridge: it settles in USD through X Money from a pre-funded float.

12 / $TAGG and the buyback

The protocol cut from other mints is spent on the open $TAGG market and sent to a burn address. Both legs are on chain. Holding $TAGG does not change the split, launch rights, or who is paid.

Creator fees earned by $TAGG itself are held as protocol treasury and used to pay Solana / pump.fun fees for tag launches. That is what makes deploys free. The free path is capped at 3 launches per X account per UTC day.

13 / Stopping payments

Disable incoming payments on X Money to stop Tagg the same as any other sender.

Or write @use_tagg from the handle (or with proof of control). Removal SLA: 7 days. Handle is delisted, added to do-not-pay, and we stop claiming mints that name it. Fees stay unclaimed on chain. An already-sent payment remains claimable for the rest of its window. Accrued-but-unsent balance at removal is split 50/50 treasury / $TAGG burn, same as an expired payment.

14 / If a token is not registering

Registration is automatic. Failure is one of:

15 / Glossary

16 / Source preview

Not production. Public cut of listen / parse / fee-share. Keys, signing, and the create path are omitted.

Loading…