How Hype Launcher Works.

Protocol overview#

A launch moves from user intent to a signed transaction, then to program execution on Solana. The diagram distinguishes interfaces and signers from on-chain programs and assets. Hover, focus, or select a component to inspect its role.

ONE NETWORK. THREE RESPONSIBILITIES.Explore each component

CreatorYOUSolana walletAUTHORIZATIONHype LauncherINTERFACEPump.funON-CHAINHYPE quoteSOLANA ASSETToken / HYPEBONDING CURVEPumpSwapAFTER MIGRATION

Hype Launcher

Configure the launch and review its progress. Hype Launcher is a user interface, not an on-chain program.

Interface & authorizationSolana program execution

After successful creation, the token trades against HYPE on its Pump.fun curve. If protocol conditions are met, migration establishes a PumpSwap market. Neither launch nor a first purchase guarantees graduation.

Your first launch#

Prepare your token identity and keep enough SOL for network fees and required account deposits. HYPE is needed only for a selected initial purchase.

1. 1

   Connect your wallet

   Use a compatible Solana Wallet Standard wallet, such as Phantom or Solflare. Select your intended mainnet account; it will authorize the launch.

2. 2

   Prepare token metadata

   Add a name, symbol, description, and token image. You can also include a website, X profile, and Telegram link.

3. 3

   Review the HYPE pair

   The trading pair is fixed. Verify the full mint below rather than relying on a symbol or image.

   98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5gCopy mint
4. 4

   Choose your initial buy

   Enter an optional amount in HYPE. Zero is supported. A selected initial buy is combined with creation in the current launch flow.

5. 5

   Inspect, sign, and launch

   Review the transaction in your wallet. Approval authorizes submission; wait for successful on-chain confirmation before treating the token as created.

6. 6

   View your token

   Use the resulting mint to open its Hype Launcher coin page or Pump.fun market. Save the actual launch signature for verification.

Launch architecture#

Pump.fun’s create_v2 instruction establishes the new base mint and its bonding curve. The user wallet authorizes creation, while the creator public key identifies the creator. The mint address is the token’s unique on-chain identity.

A supported instruction example

This instruction-level example matches the installed SDK, version 4.1.0, and the current Hype Launcher creation configuration. It is not a complete executable transaction: connection setup, validation, transaction assembly, signatures, fees, submission, and confirmation are deliberately omitted.

// Instruction example · @pump-fun/pump-sdk 4.1.0
// Assumes connection, mintKeypair, creator, name, symbol,
// and metadataUri have already been supplied.
import { PublicKey } from "@solana/web3.js";
import { OnlinePumpSdk, PUMP_SDK } from "@pump-fun/pump-sdk";

const quoteMint = new PublicKey(
  "98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5g"
);
const online = new OnlinePumpSdk(connection);
const resolved = await online.resolveQuoteMint(quoteMint);

const createInstruction = await PUMP_SDK.createV2Instruction({
  mint: mintKeypair.publicKey,
  name,
  symbol,
  uri: metadataUri,
  creator,
  user: creator,
  mayhemMode: false,
  cashback: false,
  quoteMint,
  quoteTokenProgram: resolved.quoteTokenProgram,
  pumpQuote: resolved.pumpQuote?.accounts,
});
// An instruction is not a signed or submitted transaction.

Quote resolution supplies the correct token program. When the quote is itself an eligible Pump.fun coin, pumpQuote carries the additional curve and pool accounts required by that path. Do not remove those resolved accounts or assume every quote follows the same path.

Understanding HYPE as the quote asset#

For a token named ABC, the market is ABC / HYPE. ABC is the base token. HYPE is the quote token: a price expressed in this pair measures the HYPE required per ABC, not its USD value.

HYPESolana · Fixed quote asset

View mint ↗

98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5gCopy mint

A mint identifies a token; a token account holds a particular owner’s balance of that mint. Decimal precision converts integer base units into display amounts. Account derivation depends on the mint’s actual token program, so implementations must resolve it rather than assuming that the base and quote use the same program.

Read-only mainnet verification on 30 October 2026 resolved this HYPE mint with 9 decimals and the original SPL Token program. These are verified mint properties, not assumptions about other tokens. The launch implementation resolves them at preparation time.

Creating a token#

The launch studio requires a name, ticker, description, and image. Preview the identity before signing. Images can be PNG, JPEG, or WebP, up to 4 MB. Optional website and social links must use HTTPS.

The token lifecycle#

Preparation, authorization, and execution are separate events. Select a stage to see what has actually happened. This describes the process; it is not tracking a live launch.

Token metadata#

Metadata describes the asset for wallets and market pages. The mint’s metadata URI points to descriptive information, and the document’s image field points to the artwork. Both references matter for a complete token display.

{
  "name": "Example Coin",
  "symbol": "ABC",
  "description": "An illustrative token metadata document.",
  "image": "https://example.com/abc.png",
  "website": "https://example.com",
  "twitter": "https://x.com/YOUR_ACCOUNT",
  "telegram": "https://t.me/YOUR_COMMUNITY"
}

The example uses placeholder HTTPS addresses, not real token metadata. Hype Launcher’s upload flow produces IPFS references. Other valid metadata can use HTTPS URLs; a URI need not start with ipfs:// to be meaningful.

Understanding the bonding curve#

A bonding curve links token pricing to reserve state. Pump.fun uses constant-product principles with virtual reserves, allowing a new market to begin trading without a creator manually seeding a conventional pool. Virtual reserves are pricing quantities, not a claim that those exact assets sit in a vault.

Explore a normalized model below. A buy adds quote assets and removes base tokens; the marginal price rises in this idealized model. A sell does the reverse. Larger trades move farther along the curve.

Buying & selling#

Trading is an exchange of two assets. The quote amount is the HYPE paid or received; the base amount is the token bought or sold. An expected output is only useful alongside its input amount, fees, state, and permitted slippage.

Hype Launcher currently directs trading to the coin’s Pump.fun page. Review executable quotes and authorize trades there; the diagrams on this page never create or submit a trade.

Price impact is not slippage#

Price impact is caused by your own trade changing reserves. A larger order relative to available pricing liquidity usually produces a larger difference between the starting marginal price and the average execution price.

Slippage concerns how execution differs from the quote you expected, for example because another trade changes the state before yours lands. Tolerance defines a boundary, such as a maximum cost or minimum amount received. Exceeding that boundary can cause the transaction to fail.

Setting a wider tolerance does not improve liquidity or remove impact. It permits a broader execution outcome. The average-price impact metric above deliberately excludes network competition and fees.

From bonding curve to PumpSwap#

Graduation is a protocol-defined transition. A completed bonding curve and a migrated, tradable pool are distinct states. A completion flag alone does not prove that a PumpSwap market is ready.

The current protocol supports migrate_v2. Its synthetic-migration behavior applies to supported v3 buys that cross the curve boundary: the remaining purchase can be priced against the future pool reserves, and migration later creates that pool. Ordinary curve trading pauses after completion until migration.

That behavior must not be assumed for every instruction. Hype Launcher’s current initial-buy path uses the SDK’s V2 create-and-buy instructions. It is not a v3 synthetic-migration trading interface.

Liquidity before and after graduation#

Separate pricing reserves from actual spendable assets. A reserve number used in a pricing formula is not automatically a withdrawable token balance, and a displayed market capitalization is not a liquidity balance.

PumpSwap’s effective quote reserve includes its virtual quote reserve adjustment. That adjustment is signed and can differ from zero; treating the raw quote-vault balance as the whole pricing reserve can produce an incorrect quote.

Pump.fun’s documented canonical migration burns the resulting LP tokens. This does not grant the token creator custody over pool reserves, and it should not be generalized to unrelated permissionless pools.

Wallet signing#

Your public key identifies an account. Your private key authorizes signatures and should remain within your wallet. A transaction message names instructions, accounts, signers, a fee payer, and a recent blockhash; signatures authorize that exact message.

Inspect the wallet prompt for the intended token, quote asset, initial buy, and SOL costs. The new mint signs its creation, and your connected wallet supplies its required authorization. A mint key is not your wallet private key.

From signature to confirmation#

Wallet approval, submission, execution, and confirmation describe different milestones. Follow the transaction’s actual result rather than inferring success from a button click.

signature: <YOUR_ACTUAL_TRANSACTION_SIGNATURE>
explorer: https://solscan.io/tx/<YOUR_ACTUAL_TRANSACTION_SIGNATURE>

The placeholder is intentionally not a real signature. Solana uses cryptographic signatures; the transaction identifier commonly uses the first signature. Retrieve the actual value from your launch result or wallet activity.

Costs & fees#

These are dated references, not permanent prices. Custom pairs use their own fee schedule. Check the current official schedule and transaction before approving; do not apply SOL-pair tier tables to HYPE.

Why SOL is still necessary

Solana charges network fees in SOL independently of the trading quote asset. A base fee pays for processing, and an optional priority fee can influence scheduling. Neither priority fees nor wallet approval guarantee a successful execution.

Account deposits are distinct from trading spend and network fees. Refundability depends on whether an account can be closed and who has its close authority. A processed failed transaction can still consume network fees.

Security & ownership#

Hype Launcher uses non-custodial wallet authorization. Review the transaction you are signing and verify the full token and quote mint addresses. Names, tickers, logos, and social links can be copied by unrelated tokens.

Token markets can be volatile and illiquid. A successful launch proves execution, not legitimacy, future demand, profitability, or guaranteed graduation. HYPE’s own price movements add quote-asset risk.

Frequently asked questions#

From your first wallet connection to verifying your launch.

Technical glossary#

A shared vocabulary for token creators and traders. Search by term or definition.