How Deposit works

Overview

Deposit turns a token's creator fees into dollars in someone's bank account. A deployer launches a token on pump.fun and points its creator fees at the Deposit treasury. The token's description names an X account, and that account is who the fees are for.

Everything between the two is mechanical. Fees accrue as the token trades, we claim them on chain, 80% is converted to dollars and held for the recipient, and 20% buys $DEPOSIT and burns it. Every step is recorded against the claim that produced it, and it's all on the public ledger.

The recipient isn't asked to do anything first, so a balance can build up from a token they've never heard of. To receive it, they sign in with that X account once and add a bank account or debit card. Until then it waits, and it never expires.

1. 1
   A token directs its fees

   The deployer points 100% of creator fees at the treasury, permanently. See Directing fees.
2. 2
   The description names a handle

   One line in the description says who the fees belong to: Fees to @yourhandle via Deposit
3. 3
   The token registers itself

   The indexer sees the fee direction on chain and registers the token. There is no approval step.
4. 4
   Fees are claimed

   We claim accrued creator fees on a schedule and record each claim against its transaction signature.
5. 5
   The recipient is paid in dollars

   Their 80% is held in dollars and sent to their bank or card at each payout milestone. A public post on X tells them it's there.

Directing fees

Deposit works with pump.fun on Solana. However a coin was launched, it ends in the same place: the Deposit treasury is its fee recipient, permanently, and that can't be changed afterwards.

Two rules always hold:

• It has to be the whole fee. A partial share would make every payout we publish a fraction of what the token earned, with no way for the recipient to tell which.
• It has to be permanent. A fee direction that can still be changed is a promise that can still be withdrawn.

On pump.fun

Fees are directed after the coin is created, not during: the create form has no fee-recipient field. Fee sharing is a separate screen on the coin, where a creator can split fees across up to ten wallets. Add the treasury there at 100% and it becomes the only shareholder in the coin's sharing config.

That config stays editable until its authority is revoked, so a token is detected but not payable until then. Revoking is what makes it permanent.

There's no approval step and no queue. A token that meets both rules registers on its own. Directing a token's creator fees to the treasury means the deployer accepts the Terms of Use.

Naming the recipient

The X account that gets paid is read from the token's description. Put this line in it, with the handle you want paid:

Use the format exactly, anywhere in the description, and write whatever else you like around it. A description can easily mention several accounts; “Fees to” and “via Deposit” bracket the handle so only one reading is possible.

If the line is missing we fall back to the first @handle in the description, then to the X account the token links to. Both work, and neither is as reliable as the line. pump.fun descriptions can't be edited after launch, so write it when you create the coin.

When a token registers, we look the handle up on X and record the account's permanent ID. If the account later changes its handle, the money still goes to the same account.

The 80/20 split

Every claim divides the same way. There's no discretion in it, no schedule to negotiate, and no tier that changes it.

How claims work

Creator fees don't arrive continuously. They accrue as a token trades and sit there until they're claimed, which we do on a schedule (every few minutes) rather than on every trade. Claiming per trade would spend more in transaction fees than it collected on a quiet token.

Each claim is written to the ledger keyed on its own transaction signature, so a claim can't be recorded twice and every dollar can be traced to the on-chain event that created it. The recipient share and the protocol cut are computed at that moment, from that claim, and neither is recalculated afterwards. The recipient share is converted to USDC in batches, so balances are held in dollars and don't move with the price of SOL.

A claim can fail: chains halt, RPC providers go down, transactions revert. A failed claim creates no obligation and is retried; the fees stay accrued in the meantime and aren't lost.

Payout milestones

Payouts go out at milestones. A recipient's share builds until it crosses $10, then $20, $50, $100, $250, $500, $1,000, and every $1,000 after that. Each crossing sends the full balance. Balances below a milestone keep building, and nothing expires.

Getting your fees

If a token names your handle, the money is already yours. Here's how it reaches you:

1. 1
   A token names your handle

   Somebody launches a token and points its creator fees at your X account.
2. 2
   Fees accrue and are claimed

   Trading generates creator fees. We claim them on chain on a schedule.
3. 3
   80% is set aside for you

   In dollars. @usedeposit posts on X when you reach a milestone, so you know it's there.
4. 4
   Sign in and add where to send it

   Sign in with X on the Claim page, accept the terms, and add a bank account or debit card. Once is enough.
5. 5
   Claim

   At each milestone your balance is sent to your bank account or debit card.

You aren't required to do anything, acknowledge anything, or agree to anything to be named. Receiving a payment doesn't make you a customer of Deposit or a promoter of the token that named you.

Payout methods

Payouts are sent by our payout partner, Laso Finance, from dollars we hold for you. The partner's transfer fee comes out of the payout, and each method has a minimum.

Both methods need at least $10.00 after fees, so a small balance waits for the next milestone. For bank transfers we keep only the last four digits of your account number. For debit cards you get a secure link to enter your card when a payout is ready; we never see the card number.

Unclaimed balances

Any X account can be named, whether or not it has ever heard of us. Its balance is held until the account signs in and claims it, however long that takes. Unclaimed balances never expire, and we never reassign them.

The public confirmation

When a recipient reaches a payout milestone, @usedeposit posts on X, mentioning them, with the amount waiting and the token it came from. Most recipients weren't asked before their handle was named, so this is usually the first they hear of it, and it's what they and their audience can check it against.

$DEPOSIT and the buyback

The protocol cut is spent buying $DEPOSIT on the open market and burning it. We buy from the same market as everyone else, at whatever the price is when we buy, and the tokens are burned. Both halves are on chain and linked from the ledger. Until $DEPOSIT exists, the 20% is set aside and spent on buybacks once it launches.

$DEPOSIT gates nothing. Holding it doesn't change the split, who can register a token, or who gets paid.

Stopping payments

Sign in with your X account and press Stop paying me: we stop claiming the creator fees of tokens that name you and leave them unclaimed on chain. You can undo it any time.

You can also ask us directly: message @usedeposit on X from your handle, email admin@usedeposit.app, or use the removal form with reasonable proof you control the handle. We act within 7 days: your handle goes on a do-not-pay list and comes off the site, and we stop claiming fees for tokens that name it. Anything already credited to you stays yours to claim.

If a token isn't registering

Registration is automatic, so a token that hasn't appeared has failed one of a short list of conditions. The checker tells you which. In rough order of how often each is the cause:

Glossary