Launch a token and its market.
Add your image and story, review every detail, then launch with permanent liquidity in one transaction.
Start a launch →Browse every launch, open its market, and trade with your own wallet.
THE GENESIS 100
The first 100 launches through the configured Nexus Arc release launcher receive a permanent, verifiable Genesis number from #001 to #100.
99 numbers remain
Assigned only after a launch is confirmed and indexed. A later launcher cannot restart the count.LAUNCHED COINS
The newest verified Nexus launches, with permanent liquidity and exact coin addresses.
Add your image and story, review every detail, then launch with permanent liquidity in one transaction.
Start a launch →Give your agent the Nexus instructions, review the exact launch plan, and approve it when you are ready.
Get agent instructions ↓View Nexus tokens, balances, activity, and P&L for any address.
View portfolio →03 / LAUNCH WITH AN AGENT
Prefer an agent? Send these instructions to any agent that can use a wallet. The full agent guide lives at cli.nexus/agent.md; no Nexus account or software package is required.
Launch a token on Nexus using your own wallet. Read and follow: https://cli.nexus/agent.md This procedure works with any agent that can make HTTPS requests, parse JSON, and use an EVM wallet. If you cannot control a wallet, stop after presenting the unsigned plan for approval. Launch parameters: - name: Signal - symbol: SIGNAL - PFP: use the attached square image, or ask me for one before planning - story: A concise description of why this coin exists - website: https://example.com - X / Twitter: https://x.com/example - fixed supply: 1,000,000,000 tokens - optional initial buy: 25 USDC - initial-buy slippage: 500 bps - creator fee recipient: my wallet - anti-sniper window: 300 Arc blocks - temporary max wallet: 200 bps (2%) - block launch-block pool buys: yes - launch route: agent-assisted Authenticate the creator wallet with the Nexus SIWE flow and stage the PFP, story, and typed HTTPS links as a content-addressed profile. Then request an unsigned simulated plan from https://cli.nexus with that profile hash and launchMethod "agent". Show me the exact profile hash, launch route, agent wallet identifier, complete plan, exact USDC funding and approval, permanent V3 position custody, temporary protection settings, predicted token and pool, deadline, salt, gas estimate, and plan ID. STOP before signing. Do not sign or broadcast until I explicitly approve that exact plan ID in a later message. After approval, if the plan requires funding permission, approve exactly the displayed USDC amount for the exact launcher and re-request the plan. Then sign exactly the returned zero-value launch transaction with your wallet, broadcast it on Arc Testnet 5042002, wait for receipt success, verify the token, exact registry-derived token/USDC V3 pool from the release-pinned test stack, position custody, registry record, liquidity, and initial-buy output, then publish the prepared profile to that verified token. Never count the same USDC balance twice: ERC-20 USDC funds the launch while the native USDC view must retain enough for gas. Retry delayed profile indexing without replaying the launch. Return the profile hash, approval transaction hash when required, launch transaction hash, receipt block/hash, deployed addresses, and finality status. Never send your private key to Nexus.