Launch flow

One wallet approval funds a dedicated launch wallet. Automatic execution handles the remaining protocol steps.

1. Add the coin

Choose the name, ticker, description, image and optional social links. Metadata and media are pinned before the coin is created, and the permanent metadata URI is bound to the launch record.

2. Choose the commitment

Select a Stray, Prowler or Panther tier and a 30M or 50M community reserve. The interface requests the exact SOL funding quote plus a limited gas reserve.

3. Confirm from your wallet

Your connected wallet signs authentication once per session, approves any required $CATE tier transaction, and funds the child launch wallet. Catepad verifies confirmed on-chain transfers before execution continues.

4. Create and secure

The child wallet creates the Pump.fun coin and buys the selected reserve atomically in one Solana transaction. Catepad then moves the purchased tokens into the program vault and publishes the token page.

The community reserve

Every Catepad launch buys a fixed reserve from the fresh bonding curve for future distribution to $CATE holders.

Reserve sizes

Creators select either 30,000,000 or 50,000,000 tokens for the community reserve.

Where the tokens go

After the Pump.fun create-and-buy transaction confirms, the reserve is deposited into the Catepad program vault derived for that mint. The creator cannot withdraw or redirect holder allocations.

How allocations are calculated

After migration, each qualified wallet receives the same fraction of the reserve as its fraction of eligible $CATE at the snapshot. Integer rounding dust remains in the vault rather than being assigned arbitrarily.

Launch tiers

Tiers are public commitment signals determined by confirmed $CATE burns—not by a label selected in the browser.

Burn verification

The backend builds the tier transaction and checks its mint, amount, sender, dedicated launch-wallet destination and confirmation before SOL funding is unlocked. During execution, that wallet submits a real SPL token burn before Pump.fun creation; this reduces supply and is not merely a transfer to a generic dead wallet. The burn signature becomes part of the public launch record.

Migration snapshot

Holder eligibility is frozen at the finalized Solana slot containing the Pump.fun migration.

Who qualifies

Every wallet with a positive $CATE balance at the cutoff is included. Balances across multiple token accounts owned by the same wallet are consolidated. Purchases after the migration slot and zero-balance accounts are excluded.

How Catepad proves the list

The Helius-backed holder watcher keeps finalized token-account history. At migration, Catepad reconstructs balances at the exact cutoff, calculates every allocation and creates a deterministic Merkle tree. The root and snapshot slot are activated on-chain.

Custodial wallets

Tokens held through a centralized or custodial service belong to the controlling on-chain address at snapshot time. Catepad cannot identify a service’s internal user balances.

Claiming airdrops

Qualified holders claim directly from each launch’s program vault after its migration snapshot is activated.

Check your allocations

Open the Airdrops page and connect the same Solana wallet that held $CATE at migration. Catepad checks all finalized launch snapshots and shows any allocation available to that address.

Submit a claim

1. Select Claim allocation for an eligible launch.
2. Review and sign the Solana transaction in your connected wallet.
3. The program verifies the Merkle proof and sends the launch tokens from its vault.
4. An on-chain claim receipt prevents the same wallet from claiming twice.

When claims appear

A launch remains marked “snapshot preparing” until migration is finalized, the holder tree is complete and the on-chain distribution state is active.

Safety and verification

The chain is the source of truth. Catepad’s interface exposes protocol state, but you should independently verify high-value actions.

Before signing

• Confirm the site's address before connecting your wallet.
• Check the requested SOL or $CATE amount in your wallet.
• Never share a seed phrase or private key with Catepad.
• Verify the mint address from the token page before trading.

Backend enforcement

Launch rules, tier payments, funding caps, claim ownership and state transitions are enforced server-side and on-chain. The browser is never treated as the authority for eligibility or payment confirmation.

Transaction safety

Pump.fun creation is simulated before broadcast, uses a fresh blockhash and is retried only within that blockhash’s validity window. Launch records are idempotent so a retry cannot silently create a second launch.