Bridge to Arc, Robinhood and Stable
To fund a CATCO token launch, choose the destination network first: Arc uses USDC for gas, Robinhood Chain uses ETH, and Stable uses USDT0. A balance on another chain is not a balance on your launch network.
Choose your bridge guide
Each guide covers that network's routes, gas requirements and checks before you sign. Transfers take place with external providers; CATCO does not operate a bridge or hold your funds.
Bridge USDC to Arc
Fund your Arc wallet with USDC, the asset used for both token launches and network fees.
Bridge ETH to Robinhood Chain
Move ETH onto Robinhood Chain and keep gas available, even when your launch uses a Stock Token pair.
Bridge USDT0 to Stable
Move USDT0 onto Stable and use one balance for launch funding and gas, without a separate wrapping step.
Compare destination networks
Network names, chain IDs and gas assets must all match. Adding a network to your wallet only changes its connection settings; it does not move any assets.
| Network | Chain ID | Gas | Before you transfer |
|---|---|---|---|
| Arc | 5042 | USDC | Use the Arc mainnet destination, not a testnet faucet. |
| Robinhood Chain | 4663 | ETH | Keep ETH for gas even when your launch pair is a stock token. |
| Stable | 988 | USDT0 | Confirm Stable and USDT0 in the receive quote, not just a dollar ticker. |
What a bridge does, and what it does not
A bridge moves value between networks. A swap changes the asset you own. Some providers combine both in one quote, so check the receiving chain and token rather than assuming the source asset arrives unchanged.
- Choose the same destination network you will use in the launch terminal.
- Compare the amount received after fees, any minimum receive amount, the route and estimated arrival time.
- Keep source-network gas for approvals and the transfer, then leave a destination gas reserve for your launch.
- Verify the recipient wallet and approval allowance. For an unfamiliar route, test with a small amount first.
- Track the transfer with its provider before opening a second transfer or preparing a launch.
Keep the bridge and the launch separate
Bridges add smart-contract, liquidity and provider risks. Routes and quotes can change; no fee or arrival time on a static guide is guaranteed. A completed bridge does not pay your token creation fee or deploy a token.
Never share a seed phrase or private key. If a transfer is delayed, use the original provider's tracker and support with the transaction hash. Read our risk disclosure before moving funds.