How OnPaid works

ONPAID connects two things that normally never meet: the creator fees a token earns on Robinhood Chain, and a person's Money account. Whoever launches a token sets ONPAID as its fee wallet and names an X handle in the description. From then on, that handle is who the fees are for.

Nothing in between depends on a person making a decision. Fees build up in the treasury while the token trades. ONPAID claims them, sells 80% for dollars and sends that to the named account, and uses the other 20% to buy and burn $ONPAID. Each of those steps is tied back to the claim that caused it, and each payout gets a public receipt.

The person being paid has no setup to do. They do not sign up and they do not connect a wallet, which means money can reach them from a token they did not know existed. If they would rather not receive it, section 13 explains how to turn it off.

1. 1The token picks its fee walletAt launch, the ONPAID treasury is set as the fee wallet. See section 3.
2. 2The description names a handleA single line tells us which X account the fees belong to. See section 4.
3. 3The indexer picks it upNew tokens with the right fee wallet are registered automatically — nobody approves them.
4. 4Fees get claimedClaims run on a schedule, and each one is stored under its transaction hash.
5. 5The account is paid in dollarsThe recipient share goes out through Money from a pre-funded float, followed by a public reply.

ONPAID currently works with one launchpad. More may follow, but nothing is promised until it is listed here as live.

pons.family

Robinhood Chain. Live. The fee wallet is chosen when the token is created. $ONPAID trades here.

Direct ERC-20

Tokens deployed outside a launchpad. Under review, not supported today.

On pons.family the fee wallet is one of the launch fields, next to the name, ticker and image. Put the ONPAID treasury address there and the routing is done in the same transaction that creates the token. There is no second step.

Two conditions have to hold. The treasury has to receive the entire creator fee — a partial share would make every published payout a fraction of what the token really earned, with no way for the recipient to tell. And the choice has to be final, since a fee wallet that can be switched later is a promise that can be broken.

pons.family handles the second condition on its own terms: only the address currently holding the fee wallet can transfer it. Once ONPAID holds it, the deployer has no way to take it back.

When

In the launch transaction

What we read

The fee recipient stored on the token

Why it is final

Only the current holder can reassign it

Treasury address

Published together with the contract

Pointing a token's fee wallet at the ONPAID treasury means the deployer accepts the Terms of Use.

We look for the recipient in the token description. Add this line, with the handle you want paid:

Pay @handle via OnPaid

The line can go anywhere in the description, and the rest of the text is up to you. The fixed wording exists because descriptions often mention more than one account; “Pay” and “via OnPaid” on either side of the handle leave only one possible reading.

Without the line, we use the first handle that appears in the description, then the X link attached to the token. Both fallbacks work, but the line is the only form we can read with certainty.

pons.family caps descriptions at 256 characters, so keep the line near the start. The person named does not have to agree beforehand or own a wallet — that is intended. A token can be made for someone, and they find out when the first payment arrives with a reply explaining where it came from.

Every claim is divided the same way, for every token. Nobody negotiates it and there are no tiers.

Recipient

80%, paid in dollars through X Money

Protocol

20%, used to buy $ONPAID and burn it

When it applies

At claim time, for that claim

Extra fees

None — the 20% is all of it

Exception

$ONPAID does not split its own fees; they stay in the protocol treasury

Creator fees are not pushed out on every trade. They collect in the treasury until a claim runs, and claims run on a schedule. Claiming after each trade would burn more gas than a quiet token earns.

Every claim is stored under its own transaction hash. That makes double-counting impossible and lets any payout be traced to the on-chain event behind it. Both shares are calculated once, at that moment, and never recalculated.

Claims sometimes fail — an RPC goes down, a transaction reverts, the chain pauses. A failed claim creates no obligation. It is retried on the next run, and the fees sit safely in the meantime.

Payout thresholds

A recipient's balance is sent when it crosses a threshold: $5, then $10, $25, $50, $100, $250, $500, $1,000, and every further $1,000. Crossing one sends the whole balance. Amounts below the next threshold keep accumulating and never expire while the account can receive.

If a token names your handle, the money is already yours. You do not claim anything or fill anything in. It is sent as soon as your balance passes a threshold and your X Money account accepts payments.

1. 1Someone names your handleA token launches with ONPAID as its fee wallet and your X account in the description.
2. 2Fees build up and get claimedTrading produces creator fees, and we claim them on a schedule.
3. 380% is sent to youThrough Money, from a float that is already funded — no waiting on a bank.
4. 4A public reply confirms it@onpaidxyz replies so you and your followers can see the source.

Receiving a payout does not make you a customer of ONPAID and does not make you a promoter of the token. You are not asked to acknowledge or accept anything.

Payouts may count as taxable income where you live. ONPAID does not issue tax forms and nothing here is tax advice; if the amounts become significant, talk to a tax professional. Where the law requires identity details before we can pay, the balance is held until we have them.

Payouts land in X Money, so the only requirement is an X Money account that accepts incoming payments. That is managed inside X. ONPAID cannot create the account for you or change its settings.

Availability of X Money depends on X's own rollout and eligibility rules. Anyone can be named; only accounts that can receive are paid straight away.

When a named account cannot receive yet, its balance is not lost and not redirected. It is held for 7 days. If the account opens X Money within that time, the balance is paid on the following run with nothing to claim.

If 7 days pass and the account still cannot receive, the balance moves to the protocol treasury and funds the $ONPAID buyback, the same as the protocol share. Nothing else ever happens to a held balance, and the period is fixed so it is never decided case by case.

Who can be named

Any X account

Hold period

7 days

If X Money is opened

Paid on the next run

If it never is

Moves to the protocol treasury after 7 days

Every payout is announced. @onpaidxyz replies to the recipient with the amount and the token behind it. Most recipients never asked to be named, so this reply is usually how they learn about the payment — and it gives them and their followers something to verify it against.

Everything on-chain happens on Robinhood Chain. Tokens earn fees there, claims land in the treasury there, and $ONPAID is bought and burned there. There is no bridge anywhere in the path.

The only step that leaves the chain is the dollar payout: ETH is sold at the settlement desk and the recipient is paid from the X Money float.

The protocol share buys $ONPAID on the open pons.family market, at whatever the price is at that moment, and sends it straight to the burn address. Both transactions are public on Robinhood Chain.

$ONPAID does not unlock anything. Holding it does not change the split, does not affect who can launch, and does not affect who gets paid. The disclosures page explains what the token is not.

Contract

Published at launch

Your X Money settings decide who can pay you. Switching off incoming payments there stops ONPAID paying you, exactly as it stops everyone else.

You can also ask us. Send the request from your handle — or with reasonable proof that you control it — to @onpaidxyz on X or to hello@onpaid.xyz. Within 7 days your handle is removed from the site and added to a do-not-pay list, and we stop claiming fees for tokens that name it, leaving those fees unclaimed on-chain. A balance already held for you is still paid if you ask within its hold period; after that it moves to the protocol treasury like any held balance.

Registration is automatic, so a missing token has failed one of a few checks. Roughly from most to least common:

Wrong fee wallet

The fee wallet is not the ONPAID treasury. Compare it with the address on the launch page.

No handle found

The description names nobody and the token has no X link.

Handle on do-not-pay

The named account has opted out (section 13).

Too new

The indexer runs every few blocks. A token created seconds ago has not been read yet.

Creator fees

The share of trading fees a launchpad pays to a token's fee wallet.

Fee wallet

The pons.family field holding the address that receives creator fees. Chosen at launch.

Claim

An on-chain transaction that collects accrued creator fees for a registered token.

Recipient share

80% of a claim, owed to the named X account.

Protocol share

20% of a claim, used for $ONPAID buybacks.

Held balance

A recipient share that cannot be paid yet. Held 7 days, then moved to the protocol treasury.

Float

Dollars kept in the X Money balance so payouts never wait on a conversion.