Full Token Launch Matrix

A production-style planner for choosing a Solana token launch profile before any transaction is built. It covers supply, decimals, metadata, authorities, extensions, launch route, airdrops, vanity minting, and runtime-aware SPL support.

tokenLaunch

Launch command center

One planner, clean launch profiles

Solana launch choices affect wallets, liquidity, fees, ownership, and future integrations. This example keeps the public surface simple: pick a profile, preview the plan, review the risk notes, then let Conduit build the signed-user flow when the launch is ready.

Profile

Compatibility-first

Classic SPL planning for the broadest wallet, exchange, and indexer support.

Profile

Extension-aware

Token-2022 planning for metadata, transfer-fee, and authority settings that must be chosen at mint creation.

Profile

Launch curve

Curve-style launches with supply, quote asset, timing, and migration checks handled as a profile.

Profile

Liquidity route

Pool-ready launches with extension allow-list checks before users are asked to sign.

Profile

Airdrop plan

Recipient lists, ATA creation, batching, and fixed-supply accounting before transactions are built.

Profile

Runtime optimizer

Classic SPL runtime planning for token-heavy CPI flows, wrapped-SOL cleanup, and indexer readiness.

Profile

Vanity mint

Bounded vanity estimates and paid reservation flow without exposing seed phrases or private keys.

example.tsx

import {
  checkTokenLaunchCompatibility,
  createPTokenOptimizationPlan,
  createTokenLaunchPlan,
  createTokenLaunchRequestPreset,
  estimateSolanaVanitySearch,
} from "@conduitexchange/connect";

const creator = "YourSolanaPubkey";

const launch = createTokenLaunchRequestPreset("token2022SafeDex", {
  cluster: "devnet",
  creator,
  token: {
    name: "Conduit Launch Demo",
    symbol: "CXFULL",
    description: "A full-featured Solana launch planned with Conduit.",
    decimals: 6,
    supply: "1000000000000000",
    uri: "https://example.com/cxfull.metadata.json",
    mutableMetadata: false,
  },
  authorities: {
    mint: "revoke-after-mint",
    freeze: "none",
    metadataUpdate: "immutable",
  },
  extensions: {
    metadataPointer: true,
    tokenMetadata: true,
    transferFee: { basisPoints: 50, maximumFee: "5000000" },
  },
  vanity: { target: "mint", startsWith: "CX", ignoreCase: true },
  airdrop: [
    { recipient: "RecipientPubkey", amount: "1000000000" },
  ],
});

const compatibility = checkTokenLaunchCompatibility(launch);
const vanity = estimateSolanaVanitySearch(launch.vanity);
const plan = createTokenLaunchPlan(launch);
const runtime = createPTokenOptimizationPlan({
  cluster: "mainnet-beta",
  tokenProgram: "spl-token",
  flow: "launch-airdrop",
  executionSurface: "conduit-managed-cpi",
  operations: [{ operation: "transfer", count: 250 }],
  expectsIndexerParsing: true,
});

if (!compatibility.ok) {
  throw new Error("Review launch settings before continuing.");
}

console.log({
  risk: plan.risk.level,
  requiredPayments: plan.requiredPayments,
  runtimeBatchReady: runtime.useBatch,
  runtimeSavings: runtime.estimatedCompute.savingsCu,
  vanityDifficulty: vanity?.difficultyLabel,
  nextSteps: plan.nextEndpoints,
});

What stays private

Conduit examples never ask for private keys, seed phrases, RPC secrets, or custody credentials. Public code plans and validates; Conduit-controlled services handle production build steps.

What gets checked

Authority risk, Token-2022 extension compatibility, route fit, vanity difficulty, airdrop size, runtime support, and CPI-batch suitability are reviewed before a user or agent signs anything.