Everything about Spot.

01

Overview

On pump.fun, every trade pays the coin’s creator, and only the creator. That one seat collects fees for as long as the coin lives. Spot opens it up: creators sell a share of their future fees for SOL on day one, and the people who believe in a coin get a spot in what it earns.

Every pump.fun coin pays its creator a fee on every trade. Spot splits that fee stream into ten equal shares, called Spots, and sells them in an auction. Whoever holds a Spot receives 10% of the coin’s creator fees, in SOL, for as long as the coin trades.

The split is set once, at launch, inside Pump’s own fee-sharing program, and then locked. Nothing about owning, buying or claiming a Spot touches Pump again. The Spot program only keeps track of who owns each of the ten vaults and lets that owner withdraw.

02

What a Spot is

A Spot is a record in the Spot program: launch.owners[i], for i from 0 to 9. Each index has its own vault, an on-chain address that only the program can pay out of. Pump pays 10% of the coin’s creator fees into each vault.

A Spot is not a token. It doesn’t sit in your wallet’s token list; it lives in the coin’s launch account, and this site reads it from there. That keeps it cheap and makes the ownership rules simple: one owner per Spot, changed only by buying it at auction or by its owner sending it.

03

Launching on pump.fun

The launch form creates a normal pump.fun coin. It shows up on pump.fun and trades there like any other. The difference is where its creator fees go. Your wallet asks once and signs all three transactions together; the site then sends them in order.

1. Create the coin

   Pump’s create_v2, plus your optional dev buy in the same transaction, so nobody can buy before you. Your image and metadata are pinned to IPFS first.

2. Register the Spots and turn on fee sharing

   The Spot program records the launch and checks on-chain that you are the coin’s creator, so nobody can register someone else’s coin. Then Pump’s create_fee_sharing_config moves the coin’s creator fees into a sharing config.

3. Point the fees at ten vaults, lock them, open the auction

   Pump’s update_fee_shares sets the shareholders to the ten Spot vaults at 1,000 bps each. Pump allows that list to be set once and then locks it. In the same transaction, open_auction_pump reads Pump’s config and refuses to open unless all ten vaults are there at exactly 10% and the config is locked.

What you need

• A Solana wallet: Phantom, Solflare or Backpack.
• A name (32 characters max), a ticker (10 max) and a square image under 5 MB.
• A narrative: the story of your coin, up to 500 characters. It’s saved in the coin’s metadata, so pump.fun, wallets and the Spot market all show it. It’s the first thing a Spot buyer reads.
• About 0.03 SOL for rent and network fees, plus the pre-buy fee and your dev buy.

04

The auction

Spots are sold one at a time in a descending-price (Dutch) auction. The price starts high and drops a fixed amount every 15 seconds until it reaches a floor. The first person to take it pays the current price. Then the clock restarts at the top for the next Spot.

You can’t overpay. When you take a Spot you sign a maximum price: the price you saw. If someone takes it first, the price restarts higher, your maximum is too low, and the transaction fails. You pay nothing but the network fee.

Where the money goes. The sale price goes to the coin’s creator, minus a 2% protocol fee to the treasury. The program pays both directly in the same transaction.

Pre-buys. A creator can keep up to five Spots at launch. They pay only the 2% fee on the floor price for each, because the rest of the price would be paid to themselves.

05

Earning & claiming

Fees reach your Spot in two steps, and anyone can run either one.

Because collecting pays every vault, one holder pressing Collect fees helps all ten. If you hold several Spots of the same coin, collect once, then claim each.

06

Sending & trading

Today a Spot changes hands in two ways: buying it in the auction, or its owner sending it with transfer_stack. Use Send in My Spots. The Spot moves together with any SOL still unclaimed in its vault, so claim first if you want to keep that.

Because a send is one signed transaction, two people can trade a Spot over the counter: the buyer pays, the seller sends. That needs trust between them. An on-chain order book, where a sale and the payment settle in one transaction, is the next thing on the roadmap.

07

Fees

08

What’s enforced on-chain

Buyers shouldn’t have to trust the creator or this website. These checks run inside the Spot program:

• Only the real creator can register a coin. create_launch reads Pump’s bonding curve and requires the signer to be its creator.
• The auction can’t open until fees are locked to the vaults. open_auction_pump reads Pump’s sharing config and requires all ten vault addresses at 1,000 bps each, an active config, and a revoked admin.
• Vaults only pay their owner. claim requires the signer to own that Spot. No one else can withdraw, including the creator and the protocol.
• No overpaying. take_stack fails if the price is above the maximum you signed.

Check it yourself

On Solscan, open the coin’s fee-sharing config (the sharing-config account of Pump’s fee program for the mint). You should see ten shareholders at 1,000 bps each, and the admin revoked. Each shareholder address is a Spot vault derived from ["vault", mint, i].

09

Risks

10

For developers

The program is written in Rust with Anchor. The site is Vite + TypeScript; every Pump SDK call lives in app/src/chain/pump.ts.

Addresses

Run it

# 1. build + deploy the program (devnet first)
cargo build-sbf --manifest-path programs/stacks/Cargo.toml
solana program deploy target/deploy/stacks.so --program-id keys/stacks-program-keypair.json

# 2. initialize the protocol config
cd scripts && npm install
RPC_URL=… npx tsx init-config.ts --treasury <WALLET> --meteora-config <ADDR>

# 3. run the site
cd app && npm install && cp .env.example .env
npx vercel dev

Without VITE_RPC_URL and VITE_TREASURY the site runs as a preview with sample data. Image uploads need PINATA_JWT on the server.

11

FAQ