Every step, and whether it exists

Where it goes

1 of 5 steps below are built. The rest are described in the future tense and marked, in the step, because a page that describes an intended pipeline in the present tense is a page that will be read as a receipt.

1. 01

   A token is launched on pump.fun

   The launcher signs it from their own wallet and pays the cost. The names and shares they choose are written into the token's own public metadata, so the arrangement travels with the coin and does not depend on this site staying up.

   built
2. 02

   Its creator fees are pointed at one account

   pump.fun pays creator fees to a single creator, so a split has to collect first. That account is Sent's. It means this product holds money that is not its own, which is a different risk from a site that only writes instructions.

   Not built. the fee account has not been created, so no launch can point anywhere yet.

   not built
3. 03

   Fees are claimed, and the claim is recorded

   Creator fees sit in a pump.fun vault until somebody claims them. A claim is only written to the ledger with the signature that moved it — there is no row for fees we believe have accrued.

   Not built. claiming is not automated; no claim has been recorded.

   not built
4. 04

   80% becomes payouts, 20% stays with the treasury

   Each named account gets a row with an amount and an empty signature line. The row exists the moment the split is decided; it is not a payment and this site never draws it as one.

   Not built. splitting a claim is not automated.

   not built
5. 05

   A payout is sent, and the line gets a signature

   This is the only step that changes the word on a row. Until a transaction signature exists, the line stays empty — in the database as well as on the page, because the CHECK constraint refuses a sent_at without one.

   Not built. no payout rail is connected; nothing has been sent.

   not built