Launch on Arc
Create USDC- or EURC-quoted tokens with Ripper’s Arc launchpad.
Ripper on Arc
Arc is one of Ripper’s native EVM launchpad networks. It uses the same factory and bonding-curve integration as Robinhood Chain, with quote assets and transaction amounts configured specifically for Arc. Tokens begin on a curve and can graduate to a Uniswap v4 pool.
USDC and EURC pairs
Choose USDC for a dollar-quoted launch or EURC for a euro-quoted launch. USDC is the default pair. Both configured pair tokens use six decimal places. The selected pair is what buyers spend on the curve; changing the pair does not change the chain’s gas asset.
The application treats Arc’s native gas balance as USDC. Its native amount uses 18 decimal places, while the ERC-20 interface uses six. These represent the same USDC balance, not two balances to add together. The launch flow uses the ERC-20 form as the quote token.
Create an Arc token
- Open Create, choose Arc, and connect the EVM wallet you intend to use.
- Choose USDC or EURC, then enter the name, symbol, and artwork.
- Review the live factory terms, launch fee, optional first buy, creator settings, and approvals. Keep USDC available for gas even when the pair is EURC.
- Approve the quote asset if prompted. Review and sign the creation transaction, then wait for confirmation.
- Use the confirmed token address to open its page. Allow the launch indexer to catch up before retrying a confirmed launch.
Check current launch terms
The creation button depends on the factory being configured and launchEnabled being true. GET /api/v1/launch/terms?chain=arc reads the Arc factory configuration. A configured:false response means that deployment cannot currently supply usable launch terms; it is not permission to launch.
curl "https://ripper.fun/api/v1/launch/terms?chain=arc"Arc for developers
Use arc as the chain slug and carry the chain alongside every token address. Read the live terms and the selected pair’s decimals before building amounts. list_chains exposes the configured network metadata, while search_docs and get_doc expose this guide to MCP clients. MCP tools do not sign or create tokens.