Define the launch.
Set your project name, ticker, intended raise and Solana recipient. Save a draft to review before deployment.
Build on Solana. Plan participation from Solana, Ethereum and Base with one clear destination for your token launch.
CROSS is designed around cross-chain participation. This first version prepares launch drafts and route plans without moving funds.
Set your project name, ticker, intended raise and Solana recipient. Save a draft to review before deployment.
Explore how USDC participation from Ethereum or Base would reach a Solana launch. Network-specific token and provider checks are required.
The intended launch and token delivery take place on Solana. A route provider and launch contract must coordinate settlement before this can go live.
Build a route outline. This is not a quote: provider fees, exchange rates, minimums and delivery time are not calculated.
No wallet connection, approval or payment occurs. The actual route needs a supported provider, a live quote, transaction review and recipient validation.
Save draft terms in this browser and export them. No token, sale or deposit address is created.
Drafts are not public launches. Export a backup before switching devices or clearing browser data.
Not in this version. You can save launch drafts and generate route outlines. Wallet connection, executable bridge quotes, token minting and token delivery require integrations that are not connected.
The proposed launch token lives on Solana. Cross-chain participation concerns the source of payment, not deployment of the token on every network.
A production integration must define recovery, refunds and settlement states before taking payments. This version sends no transactions. A bridge transfer alone must never be presented as a completed launch purchase.
No. A real provider quote must show the supported asset, destination amount, fees, expiry and route conditions. The planner displays your entered amount only, not a guaranteed amount received.
The intended flow requires a valid Solana recipient for the launch token. A production integration must confirm that recipient and explain any destination fee requirements.