Zerofuse is a Solana token launchpad built on Meteora. Every launch starts at zero: either right away on a bonding curve, or after a countdown — the fuse — so everyone gets the same start instead of bots buying the first block.

Protections are on by default: liquidity is locked forever, the mint is revoked, team tokens vest, and a creator-chosen anti-sniper fee makes the first seconds expensive for snipers. When a curve fills, liquidity moves to a Meteora DAMM v2 pool and the token keeps trading on Zerofuse.

1. 1Connect a Solana wallet (Phantom, Solflare, Backpack or any Wallet Standard wallet).
2. 2Identity — name (up to 32 characters), ticker (2–10 letters and numbers), logo, description and links. The ticker must be free on Zerofuse and can't copy a well-known token.
3. 3Tokenomics — total supply (1M to 1T), decimals (6–9) and an optional team share (0–20%).
4. 4Launch — instant or timed, target raise (10–500 SOL), the anti-sniper fee and buyer protections. The live preview shows the exact card buyers will see.
5. 5Review — confirm the summary, then approve in your wallet. Logo and metadata are pinned to IPFS, then the launch transactions are built in your browser for you to sign.

Your wallet pays the network fees and account rent (about 0.06 SOL). The draft saves as you type, so a refresh never loses your work.

Countdown only: the pool creation is signed with a durable nonce, so the signature never expires. Zerofuse checks it, simulates it and submits it at zero. Until then the creator can cancel: closing the nonce account voids the signed transaction and returns its rent.

With commitments: the countdown must be at least 2 hours, because commitments close 65 minutes before zero (see Commitments).

Bots buy in the first seconds. The anti-sniper fee starts high when trading opens and drops to the normal 2% in equal steps, so sniping costs a lot and real buyers get a fair shot. It is enforced on chain by Meteora's fee scheduler.

Example with the defaults: buyers in the first second pay 50%, the fee falls about 1.6% every second and is back to 2% after 30 seconds. Cards and the trade panel show the current fee and countdown live. For commitment launches, the vault's own purchase before zero always pays only 2%.

Every token page has a Buyer protection card, and Explore can filter to Only fully safe launches.

• Trade on the token page: pick Buy or Sell, enter an amount, check the quote, approve in your wallet.
• Or use Swap. It swaps any Solana token at the best price via Jupiter; SOL ↔ Zerofuse launches trade straight on their Meteora pool (same quote, fee and protections as the token page). Tokens Jupiter hasn't verified are flagged: check the contract address. Links like /swap?from=<mint>&to=<mint> open a pair.
• The quote shows what you receive, the minimum received with your slippage, the price impact and the fee (including any anti-sniper fee).
• Slippage: 0.5%, 1%, 2%, 5% or custom; remembered in your browser. Default 1%.
• Price impact above 5% shows a warning; above 15% you must confirm before trading.
• Near the end of a curve, a buy larger than the room left only fills up to completion; the rest stays in your wallet.
• After graduation, trading continues on the token page through the DAMM v2 pool (also linked to Axiom).

Commitment launches let buyers get in before zero at one shared price:

1. 1Commit SOL during the countdown. You can take it back any time until commitments close.
2. 2Commitments close 65 minutes before zero. The vault cap is the launch's target raise; above it, SOL is refunded pro rata.
3. 3In the last hour, anyone presses Buy for committers now (it costs only a network fee). The vault buys once, so every committer pays the same average price.
4. 4At zero the pool opens. Claim your tokens (and any refund) from the token page or Portfolio → Commitments.

Pricing: a full vault buys 20% of the pool's tokens. The opening price is set so that happens exactly at the cap; a full vault pays on average 1.25× the opening price.

When a bonding curve reaches its target raise, it is launched: trading on the curve stops and the liquidity migrates to a Meteora DAMM v2 pool with the LP locked. 20% of the supply seeds that pool. Meteora's keepers usually migrate within minutes; if it takes longer, anyone can press Trigger migration on the token page.

Once graduated, the token trades in-app on its DAMM v2 pool at the live price. Commitment launches start on DAMM v2, so they appear as graduated from zero.

• Charts are built from real on-chain trades in 1m, 5m, 1h and 1d candles, ending at the live pool price.
• Each trade is priced without the fee, so anti-sniper fees don't show as fake spikes.
• After graduation, the chart and trade list combine the curve's history with the DAMM v2 pool's.
• Market cap = price × total supply. Data refreshes every few seconds.
• Explore filters by protocol (Dynamic BC or Meteora) and quote token, by status, market cap and safety.

Every bonding-curve trade pays a 2% trading fee in SOL (more while an anti-sniper fee is active). It is split:

After graduation the DAMM v2 pool charges a 1% fee that goes to the liquidity positions — the creator's locked position — after Meteora's protocol share. Commitment-launch pools work the same way. Network fees and account rent are paid by whoever sends the transaction.

Creators see their earnings in Portfolio → Created: the curve's creator fees plus, after graduation, the fees of their locked LP position. Claim collects everything with one wallet approval. Locked liquidity can never be withdrawn, but its fees can always be claimed.

Every Zerofuse curve is created with this address as fee claimer, which is also how Zerofuse finds its launches on chain:

7jC6z7rg5PjpJw6o9SPusGLZisUKKyVkYVxBs6sb68zC

Platform fees can only be claimed by this wallet, from the partner dashboard.

• Curve launches: a DBC config (fees, curve, protections, partner wallet) and the pool. Token metadata is created by the DBC program.
• Commitment launches: the token (full supply minted, metadata, mint authority revoked), a DAMM v2 pool and an Alpha Vault.
• Metadata: name, ticker, description, logo and links, pinned to IPFS and linked from the token.
• Off chain: scheduled launches (the signed transaction until zero), the list of commitment launches, reports and Telegram subscriptions. Prices, balances and lock status are always read from chain.

Zerofuse doesn't deploy its own program; launches use Meteora's audited programs:

• Your wallet signs everything. Zerofuse never asks for, stores or sees private keys or seed phrases. New mint, config and position keys are generated in your browser and only co-sign their own transaction.
• Checked before it's stored. A scheduled launch is decoded, checked (right nonce, right pool, nothing else in it, valid signatures) and simulated before Zerofuse accepts it.
• No custody. Tokens and pools are standard Meteora accounts. Zerofuse can't freeze, mint or move them; funds only move with your signature.
• Hardened site. Strict security headers (no embedding in other sites), rate limits, and the RPC key stays on the server.
• Know the risks. New tokens are highly risky and can lose all value. Read the risk disclosure.

Tickers of well-known tokens (SOL, USDC, BONK, JUP…) and names that impersonate projects or use bait words like “official” or “airdrop” are refused, and such tokens are left out of Explore even if created elsewhere.

Anyone can report a token from its page. The Zerofuse team reviews reports and can hide a token from Explore and search — a decision signed by the partner wallet. Hidden tokens stay on chain; their page shows a warning.

On a launch that's counting down, Get Telegram alerts opens the Zerofuse bot and follows that launch. You get a message 10 minutes before zero, at zero, and for commitment launches 30 minutes before commitments close and when the vault can buy. Send /stop to the bot to stop.

Read-only JSON endpoints used by the app. They're rate-limited and only accept browser requests from this site; server-side scripts can call them directly. Token data itself is on chain — read it with any Solana RPC.

Reasons for reports: impersonation, scam, offensive, other.