Welcome
to Protocol.

One interface. Clear responsibilities.#

Creators choose the new token’s identity and a compatible quote asset. Protocol prepares the request, stores launch information and follows its result. Pump.fun’s on-chain program creates the mint and curve; Solana executes the transaction.

The selected quote asset is the other side of the token’s market. In TOKEN / USDC, TOKEN is the new base token and USDC is the quote. SOL, USDC, STOCK and CUSTOM are categories in the launch studio; each selected mint must pass the existing compatibility check.

From wallet to market.#

Six stages describe the user journey. Select a stage to inspect what happens and which parts depend on wallet approval or on-chain state. This is an educational flow, not a live launch tracker.

Prepare for your first launch

Have your name, ticker and artwork ready. Review the selected quote mint, keep SOL for fees and account deposits, and hold enough of the selected quote token if you choose an initial purchase. The sequence diagram groups the journey; the studio itself lets you edit identity and pair details before submission.

Choose your market’s other side.#

A quote asset defines what the new token is priced and exchanged against. Protocol has four selection categories. Explore each below; these cards explain the existing studio options and never submit a launch.

A valid mint is the starting point.#

Paste the full Solana mint address in CUSTOM. Protocol reads the mint account, token program and decimal precision, then resolves available Token-2022 or Metaplex metadata for its identity and image. Metadata may be absent; an available symbol or image is descriptive, not proof of support.

1. 01

   Identify the mint

   Use the complete address, not a ticker, pool address or wallet token-account address. A mint identifies the asset; an owner’s token account holds its balance.

2. 02

   Review the resolved identity

   Check the displayed name, symbol, full address and decimals. The quote’s token program is resolved independently of the new base mint.

3. 03

   Check launch compatibility

   The installed SDK resolves the quote against supported configuration and eligible Pump.fun quote paths. Invalid, uninitialized or unsupported assets cannot proceed as verified launch quotes.

4. 04

   Recheck during preparation

   Protocol performs quote resolution again on the server when building a launch. A prior preview cannot guarantee that configuration or availability will remain unchanged.

Give the idea an identity.#

The creation studio combines the existing token form, identity preview and launch summary. The preview follows your edits; it does not create an on-chain token or reserve a name.

The form has no controls for custom token supply, editable launch fees, cashback, holder rewards or Mayhem mode. Do not infer those options from features offered elsewhere in the protocol.

Artwork, metadata and persistence.#

When you launch, Protocol uploads the image and metadata JSON through Filebase and receives IPFS references. The JSON contains your identity fields, image URI and supported links. Its URI is included in the prepared creation instruction.

{
  "name": "Example Token",
  "symbol": "EXAMPLE",
  "description": "Illustrative metadata, not a live token.",
  "image": "ipfs://<IMAGE_CID>",
  "website": "https://example.com",
  "twitter": "https://x.com/YOUR_ACCOUNT",
  "telegram": "https://t.me/YOUR_COMMUNITY",
  "external_url": "https://example.com"
}

The database stores the mint, creator, metadata references, selected quote mint, symbol, decimals and pair category alongside launch state. Stock identity and an optional initial-buy amount are also persisted where applicable. Historical quote records keep their original asset identity.

What the launch actually creates.#

Protocol uses the installed @pump-fun/pump-sdk 4.1.0 and its create_v2 mechanism. The base token is created with Token-2022; the selected quote’s program is resolved separately. The connected creator is the fee payer, and a new mint keypair supplies the mint’s creation signature.

The native-SOL builder uses the SDK’s SOL create or create-and-buy path. Token-quoted launches resolve the quote and required accounts; initial buys use the SDK’s V2 token-quote instructions and a versioned transaction with an address lookup table. These are existing execution paths, not settings you need to configure in the docs.

Your wallet authorizes the launch.#

Use a registered Solana Wallet Standard wallet with mainnet transaction-signing support. The available-wallet list is based on the capabilities exposed by installed or registered wallets, rather than a fixed list of brands.

Inspect the intended creator, token, quote mint, optional buy and SOL costs in the wallet request. Protocol’s server verifies the returned signatures and matches the signed transaction message against the prepared launch before submission. Token-quoted initial buys request a versioned transaction, so the wallet must support that format.

A confirmed result shows the mint and transaction signature and links to the token page and Pump.fun. If the outcome is still pending, follow the recovery instructions in Submission & recovery.

Read the reserves.#

Pump.fun uses virtual reserve quantities to price curve trades using constant-product principles. In the simplified relationship x × y = k, x represents base-token reserves and y represents quote reserves. A buy adds quote and removes base tokens; a sell moves assets in the opposite direction. The real protocol also applies fees, rounding and available-reserve limits.

How Protocol measures bonding progress

Protocol reads the token’s on-chain curve, checks its program ownership and quote mint, and uses the creation transaction’s matching Pump.fun creation event as the initial real-token reserve. The percentage compares that verified initial reserve with the curve’s remaining real-token reserve.

A completed curve reports 100%. If the necessary curve state or initial creation-event reserve cannot be verified, progress is unavailable. Protocol does not substitute a made-up percentage. Selling can replenish reserves and reduce the measured progress before completion.

Completion is a milestone. Migration is a state.#

The curve’s on-chain completion flag marks the end of its ordinary curve phase. Protocol separately checks the SDK’s migration result: completion and migration must both be true before the token is labeled Graduated.

The canonical migrated market is on PumpSwap. Protocol observes the state; it does not offer a migration button or promise graduation at a universal SOL amount, USD market cap or elapsed time. Use the selected quote’s actual protocol conditions.

Price, reserves and liquidity are different.#

Market capitalization is a valuation calculation, not the amount you can withdraw or sell into. A completed curve, a migrated pool and an indexed chart are three separate observations.

Find the token. Understand the source.#

The Market lists confirmed launches stored by Protocol. Search by name, ticker or mint; filter by All, SOL, USDC, Stocks or Custom, and by curve or graduation status. Sort by newest, oldest, market cap or 24-hour volume. Pagination uses the existing 24-record query size.

Select a token to open its existing detail route. The page brings together token identity, quote asset, full mint address, available market metrics, bonding status, metadata links and the existing chart integration.

Trading follows the selected quote.#

Protocol’s token detail page links to the token’s Pump.fun market. Execute buys and sells through that external interface and review its current quote, balances, fees and wallet request. The current Protocol page does not provide an embedded trade-submission form.

For TOKEN / USDC, a buy exchanges USDC for TOKEN and a sell exchanges TOKEN for USDC. The same base/quote distinction applies to SOL, stock-token and compatible custom pairs. The value of the quote asset itself can change.

A trade moves the market.#

Price impact is the effect of your own order changing reserves. Slippage is a difference between expected and execution-time terms, including changes while a transaction is pending. A slippage limit bounds an acceptable result; it does not improve liquidity or remove price impact.

Protocol’s current optional initial buy uses a 1% slippage cap. That setting belongs to the launch flow; external Pump.fun trades use the settings and executable quote shown there. If execution cannot satisfy a bound, it can fail.

Separate the purchase from the costs.#

Protocol rates can change. These published references are not a fixed all-in launch quote. The builders fetch current protocol configuration for initial-buy calculations; review the actual wallet request and current fee schedule.

What to hold in the connected wallet

Keep SOL for network fees and account creation in every quote category. For an initial buy, also hold sufficient SOL or the selected quote token for the purchase and its execution bound. Protocol checks the relevant quote account and funding during initial-buy preparation.

An initial buy of 0 creates without that purchase. It does not remove transaction or account costs. Solana fees are paid in SOL and can include an optional priority component; the current builder’s compute-unit limit is not itself a priority-fee payment.

Follow the result all the way through.#

Wallet approval, a returned signature and confirmed success are separate milestones. The existing flow uploads metadata, prepares the transaction, requests your signature, submits the signed bytes and checks the result.

The browser retains a pending signed launch in session storage for recovery. If confirmation is delayed, keep that browser session and use Check launch. Inspect the actual signature in wallet activity or on a Solana explorer. Recovery follows the existing signed transaction; it is not a new token configuration.

Trust the address. Inspect the signature.#

Your wallet controls authorization. Protocol does not ask for a seed phrase or wallet private key. The server checks the signed message against the prepared launch, validates its signatures, and matches confirmed execution to the same message before marking success.

Successful execution proves that the submitted instructions ran. It does not guarantee demand, liquidity, future returns or graduation. Metadata can be copied, quote assets can fluctuate, and providers or RPC reads can be unavailable.

The questions before the first move.#

Practical answers about quote support, wallets, launch costs and token verification. These describe the current Protocol implementation.

A shared language for the terminal.#

Search the terms used throughout the guide.