Funding & recovery
Keep track of each wallet, transfer, and launch.
Funding your launch
Your chosen developer-buy amount is an all-in spending cap in the native currency of the network shown beside it. Splits divides that amount equally by value between selected destinations. Each share includes source transaction fees and the destination’s funding and launch costs.
Existing destination balances can pay their allocated value without a transfer. Current prices estimate the equivalent native share independently of bridge routes. Otherwise, funds move directly on the same chain or through Relay to another chain. Relay delivers SOL on Solana, ETH on Robinhood Chain, Base, and Ethereum, or BNB on BNB Chain.
For Relay funding, the review shows the exact native amounts and ties each quote to your wallets, chains, amount, and expiry. The estimated initial buy uses its minimum output after launch costs and reserves, and the flow checks delivery before launching. With existing funds, only the allocated native value is available to the batch. Extra balances, delivery, or unspent reserves remain in the launch wallet.
If delivery falls short, the launch stops for review. An additional top-up requires a separate spending decision; the flow does not silently increase your original budget.
Independent transactions
All selected wallets must be ready before launch transactions are prepared. Connected EVM wallets request transaction approvals one chain at a time. Confirmation is independent on every chain. One token can be live while another is pending or has failed.
Pons holder setup follows token creation. A successfully created token may still need its distributor and fee-routing steps completed.
Returning to a launch
The browser saves public recovery data: coin details, wallet addresses, reviewed allocations, funding references, and transaction identifiers. Generated private keys stay in memory and are excluded from that record.
Use the same browser, reconnect your connected funding and launch wallets, and restore generated wallets with their exported keys. Check the recorded funding and launch transactions before continuing. Confirmed launches are preserved.
When a status is uncertain
A timeout can happen after a transaction was submitted. Check the recorded signature or transaction hash and Relay status before sending funds again. The flow keeps uncertain attempts recorded to prevent duplicate payments.
A failed transaction can still consume network fees. Review any retry or top-up separately. A confirmed launch remains live and follows its launchpad’s rules.