HYPED / DOCUMENTATION

Understand what
powers every trade.

The guide to HYPE-paired coins, transparent fee allocation and reserves that belong to each token.

SolanaHYPE pairsOnchain settlement

Your token. Your HYPE reserve.

Trading fees charge this token’s reserve. Burn tokens to redeem your proportional share.

HYPED is a launchpad for HYPE-paired tokens on Solana. Tokens launch through pump.fun and can graduate to PumpSwap. Each registered token has its own HYPE reserve, its own rewards budget and its own allocation records.

01

Launch

Launch a token with a HYPE trading pair and select its reward mode.

02

Charge

Collect creator fees and settle them into five fixed destinations.

03

Redeem

Burn tokens to redeem a proportional share of that token’s HYPE reserve.

Status

Onchain and irreversible. Not independently audited. Not affiliated with Hyperliquid or pump.fun.

Every launch, trade and redemption is a real Solana transaction signed in your own wallet. The website re-verifies the deployed program, treasury and lookup table before any transaction flow opens; the proofs list every address so you can check them yourself.

HYPE, on Solana.

The quote asset used by this application is the SPL HYPE token on Solana. Transactions are signed by a Solana wallet such as Phantom, and network fees are paid in SOL.

HYPE mint · Solana98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5gView mint ↗

Pump’s supported-pairs list identifies Sunrise / Wormhole Labs as the listing provider for this Solana HYPE mint. HYPED executes on Solana and does not currently provide a native Hyperliquid connection. Native HYPE on Hyperliquid is on a different network. A Solana token transfer does not move assets across networks. Any bridge or exchange used to obtain Solana HYPE has its own fees, availability and custody assumptions. Check the destination network and mint before transferring.

Verify the supported HYPE mint and provider ↗

Open Move HYPE →

From an idea to a HYPE pair.

  1. Connect your Solana wallet.

    Keep SOL available for network fees and account creation, plus the SOL for any dev buy.

  2. Prepare the token details.

    Enter a token name, ticker and a public HTTPS metadata JSON URL. The JSON must contain the same name and ticker, plus an image URL.

  3. Choose creator or holder rewards.

    This determines who can receive the token’s 30% rewards allocation. It does not change the five-way fee split.

  4. Optionally add a dev buy.

    Enter a SOL amount (or pick a preset) to buy your own coin at launch; 0 means no dev buy. Your SOL is swapped to HYPE through a public Jupiter route (1% minimum output), then the coin is bought with that HYPE using the same pump.fun buy and 1% slippage cap as a normal trade. The launch, swap and buy are approved in one wallet prompt; any HYPE left over stays in your wallet.

  5. Launch with one wallet approval.

    The page shows the simulated SOL cost before you click Launch. Your wallet then approves once. The launch creates the pump.fun token and registers it with HYPED in one atomic transaction, so a failed transaction cannot leave a partially registered launch. A dev buy is a second transaction approved in the same prompt and sent as soon as the launch confirms; if it would no longer succeed, it is not sent and your HYPE stays in your wallet.

The token-launching wallet may be different from the platform’s treasury or program administrator. A new token becomes visible in Coins once its confirmed registered accounts can be read.

Launch a coin

Trade with a wallet-signed quote.

Open a registered token in Coins, choose buy or sell, and enter an amount. Review the quote, slippage setting, fees and expected output before signing. The client routes trades through the token’s pump.fun curve or its canonical PumpSwap pool after graduation.

A quote can change.

Market movement, available liquidity and other transactions affect execution. Slippage bounds the input or output accepted by the selected trade; it does not guarantee the quoted price.

The 2% creator fee applies to buys and sells. Pump.fun or pool fees and Solana network fees are separate. Selling transfers tokens into the market; burning to redeem destroys tokens and redeems from their reserve. These are different actions.

2% creator fees,
split five ways.

Every buy and sell feeds project operations, token vaults and the community. The compiled program enforces the allocation on every fee settlement.

The percentages below are shares of the creator fee, rather than shares of total trading volume. Creator fees are first collected and then settled by the program; the split is enforced when settlement executes.

DestinationOf creator feesOf trade volume
Per-token HYPE reserve30%0.60%
Platform-token buyback & burn30%0.60%
Development, security, infrastructure & listings5%0.10%
Creator / holder rewards30%0.60%
Long-term treasury & growth5%0.10%
Total100%2.00%
Two budgets. One treasury wallet.

Development and long-term growth each receive 5% of creator fees. Both are transferred to the project’s treasury wallet: together, 10% of creator fees or 0.20% of trade volume. These are treasury funds, not an automatic personal payout.

Try a trade volume

Amounts in USD
$USD
Total creator fees$20,000.00
Combined treasury allocation$2,000.00

Illustrative USD amounts; this is not a live price conversion or an earnings forecast. The protocol settles actual fees in HYPE. This example rounds to cents; onchain allocation preserves every HYPE base unit. Venue and network fees are excluded.

At $100 in trading volume, the illustrative creator fee is $2: $0.60 for the token’s reserve, $0.60 for platform buybacks, $0.10 for development, $0.60 for rewards and $0.10 for long-term treasury. At $1 million, the fee is $20,000 and the combined treasury allocation is $2,000.

Redeem a share of your token’s reserve.

Each token’s reserve holds the HYPE allocated to that token. A holder can burn tokens to redeem a proportional share of the available reserve. The program burns the tokens and pays the HYPE in the same atomic transaction.

HYPE payoutreserve × tokens burned ÷ total token supply before burn

For example, burning 1% of the pre-burn total supply redeems approximately 1% of the current HYPE reserve, subject to integer rounding. The denominator is total mint supply, not just the tokens in your wallet or circulating outside the pool.

A burn is permanent. A reserve is not a guaranteed market-price floor, and the payout may differ from what selling the same amount would return. Review the current reserve and payout quote before signing. An empty reserve cannot fund a redemption.

One rewards budget. Two launch modes.

Creator mode

The token’s 30% rewards allocation can be claimed to the creator recipient fixed at launch. The caller cannot redirect the payout to another wallet.

Holder mode

The operator or delegated keeper publishes a holder snapshot and allocation manifest. Each eligible holder claims their assigned amount with an onchain Merkle proof.

Holder snapshots use finalized Solana balances and a published eligibility policy. The keeper excludes frozen or delegated accounts and the canonical curve, pool and vault accounts; any additional exclusions must be disclosed in the manifest. Holding a token does not by itself guarantee a reward at a particular time.

Published Merkle roots are immutable. The root and claim receipt protect the published allocation from duplicate claims, but the correctness of the snapshot depends on its publisher. Reward epochs remain claimable for 180 days. After expiry, anyone can return unclaimed HYPE to that same token’s rewards budget.

The keeper can sponsor delivery to the fixed recipients when it has sufficient SOL. Holders can also claim themselves using the published manifest and proof.

Volume funds a bounded buyback budget.

30% of creator fees accrues to a platform-token buyback budget. The owner configures the platform token once. Execution waits until that token has a canonical HYPE PumpSwap pool.

The operator or authorized keeper can buy the platform token using that budget, then burn the purchased tokens atomically. The native program caps spending at 0.25 HYPE per execution, enforces a global five-minute cooldown and checks a minimum output against the current pool reserves.

A budget is not a completed buyback.

Funds can accumulate while configuration, pool liquidity, operator access or keeper funding is unavailable. Actual completed buybacks and burns must be verified from their confirmed transactions.

The current global cap permits at most 72 HYPE of buyback input per day in theory. Larger budgets queue; bot settings cannot exceed the native cap. Increasing native capacity requires a verified program upgrade signed by its upgrade authority. Holder deliveries are also batched and depend on the keeper’s SOL budget. The output check uses current reserves, not a time-weighted oracle. Buybacks do not guarantee token price, returns or a continuous execution schedule.

Separate the treasury from the keeper.

The treasury receives its two operating and growth allocations. Token reserves and rewards remain in program-controlled custody with instruction-specific payout rules. The deployed program remains upgradeable by its upgrade authority; its current build and authority are part of the verification process.

The keeper is a separate service the owner delegates onchain. Its delegation and service status are shown on the Activity page. Execution still requires available token budgets; platform buybacks also require the configured platform token and its canonical PumpSwap pool.

Owner controls

Deploy and initialize the program, configure the platform token, and grant, rotate or revoke the keeper’s delegation.

Keeper permissions

Collect and settle fees, deliver fixed claims, publish holder epochs and execute bounded buybacks. It cannot change the treasury or upgrade the program.

The delegated keeper is trusted to publish correct holder allocations within the available rewards budget. Its service enforces simulation, SOL funding limits and persistent tracking of pending transactions. Uncertain transaction confirmation pauses further spending until resolved.

Read the accounts. Check the build.

The website verifies the Solana mainnet identity, deployed program bytes, treasury configuration and frozen lookup table before enabling real transaction flows. A missing program or mismatched configuration keeps the app gated.

Before deployment the program was compiled and exercised against captured mainnet pump.fun and PumpSwap programs in a local fork. Onchain and irreversible. Not independently audited. Not affiliated with Hyperliquid or pump.fun.

Activity shows confirmed transactions available to the application and links to explorers. It does not invent a complete market-volume history or an independent global index. This product does not provide shielded transactions or private transfers.

Check it yourself.

Every value below can be checked on a public Solana explorer. The sha256 hash of the compiled program published on this site must match the bytecode deployed at the program address.

Deployed program — verified 2026-10-29

Read-only mainnet check on 2026-10-29: the bytecode deployed at the program address matches the SHA-256 below. Compare every address with an explorer before you sign; the program, treasury and lookup table are re-verified by the site before any transaction opens.

Program ID
7y3Y6hkaiRH73vr5EYXnCSYrRQyUpAwChJQ8bH3QXqL3Explorer ↗Solscan ↗
Program bytecode SHA-256
fd7fb80711f740fd34f00117d0bc1ad6c1ca5c43ad36728449f6ddcae45765ad183,144 bytesDownload binaryBuild record
Address lookup table
5CL1TjWVUr4WhDegKHmvMizAkhofsGHwCU8Ry7s5Je48Explorer ↗Solscan ↗
Treasury (5% dev/infra + 5% long-term)
Cx64PYoAD5a61fds7vRjJsMPxd2AHkecBu62x1FC6biQExplorer ↗Solscan ↗
HYPE mint (SPL, Pump-listed)
98sMhvDwXj1RQi5c5Mndm3vPe9cBqPrbLaufMXFNMh5gExplorer ↗Pump supported pairs ↗

Launch with intent.
Understand what you sign.

Explore coins →