> ## Documentation Index > Fetch the complete documentation index at: https://docs.layerzero.network/llms.txt > Use this file to discover all available pages before exploring further. # Bridge Canton Coin with Stargate > Step-by-step guide to bridge Canton Coin between a Loop wallet on Canton and BSC, Solana, HyperEVM, or HyperCore with Stargate, including registration and fees. > [!NOTE] > > Available when Canton Coin launches on Stargate and the Value Transfer API. > > Canton Coin on BSC, HyperEVM, and Solana is bridged CC: an OFT that LayerZero Labs deployed and administers. It is minted when native CC is locked on Canton through the LayerZero CC adapter. On HyperCore, `LZCC` is a spot token linked to the HyperEVM OFT through the Hyperliquid asset bridge. The Global Synchronizer Foundation, Digital Asset, and the Canton Network did not deploy bridged CC and do not administer its contracts. See [Canton Coin Across Chains](https://docs.layerzero.network/v2/developers/canton/canton-coin/overview.md). Use [Stargate](https://stargate.finance) to move Canton Coin (CC) between Canton and BSC, Solana, HyperEVM, or HyperCore. On Canton, you send and receive native CC. On the other chains, you send and receive bridged CC. Stargate builds each transfer with the LayerZero [Value Transfer API](https://docs.layerzero.network/v2/developers/value-transfer-api/overview.md). You approve it in your wallet, and your wallet submits it. On Canton, Stargate supports Loop and Canton wallet extensions that implement CIP-0103. If your wallet's node does not run the LayerZero packages, Stargate shows an error that names one missing package when you send or register. The node needs the full LayerZero package set, not only that package (see [Troubleshooting](https://docs.layerzero.network/v2/developers/canton/canton-coin/troubleshooting.md)). ## Before You Start ### On Canton 1. **Create a Loop wallet.** Your wallet has a Canton party ID in the form `hint::1220<64 hex characters>`. 2. **Fund it with CC.** Canton fees are paid in CC, so you need CC on Canton before you can bridge in either direction. 3. **Turn on One-step Transfers** in the Loop settings. With this setting on, CC from another chain arrives in your wallet directly. With it off, CC arrives as an offer that you must accept within 24 hours. 4. **Keep the fee in separate holdings.** Each transfer you receive arrives as a separate holding. A send from Canton pays the amount and the protocol fee from different holdings, so fund your wallet in at least two transfers. One or more holdings pay the fee, and the holdings that are left must cover the amount. Stargate passes your holdings to the Value Transfer API, which picks them. Your Loop Fee Balance does not count: it pays Canton network costs, not the protocol fee. If all your CC is in one holding, receive a second transfer of at least the fee from another wallet or an exchange. ### On BSC, Solana, or HyperEVM 1. Use a wallet for that chain, for example MetaMask on BSC or HyperEVM. 2. Hold the chain's native token (BNB, SOL, or HYPE) for the transaction fee. 3. On Solana, use a wallet that signs Solana v1 transactions. See [Solana Wallets](#solana-wallets). ## Bridge Out of Canton Use these steps to send CC from Canton to BSC, Solana, HyperEVM, or HyperCore. **1. Connect your wallets** Open Stargate. Connect Loop as the source wallet. Connect a wallet for the destination chain, or have its address ready. **2. Choose the route** Select Canton as the source chain and Canton Coin as the token. Select BSC, Solana, HyperEVM, or Hyperliquid (HyperCore) as the destination chain. **3. Enter the amount and the recipient** Enter the amount. Enter the destination address, or use the connected destination wallet. **4. Review the fee** Stargate shows the fee in CC. **5. Approve in Loop** Approve the transaction in Loop. Loop submits it to Canton. If Stargate reports a timeout, check Loop's activity before you send again. **6. Receive on the destination chain** The CC arrives at the destination address. Check that the token address matches the [token table](https://docs.layerzero.network/v2/developers/canton/canton-coin/overview.md#token-identifiers). To send to HyperCore, the destination address must already be activated on HyperCore. See [HyperCore](#hypercore). ## Bridge Into Canton ### One-Time Setup: Register Your Canton Party A LayerZero message carries only the 64-character part of your party ID after `1220`. Canton finds your full party ID in the CC adapter's registry. Before anyone can bridge CC into Canton for you, your Canton party must register in that registry once. Registration is a Canton transaction. Your Canton wallet, for example Loop, signs it, and the one-time registration fee is paid in CC from holdings that your party already has on Canton. Stargate cannot register your party from BSC, HyperEVM, or Solana, and no flow registers your party automatically from another chain. Stargate has no separate registration page. It checks registration when you start a transfer into Canton, not when you connect your wallets: 1. Connect your Canton wallet as the destination wallet, and connect the wallet for the source chain. Start a transfer of CC from BSC, HyperEVM, or Solana to Canton, with your connected Canton party as the recipient. 2. When you start the transfer, Stargate checks whether the recipient party is registered. If it is not, Stargate shows the registration fee in CC, if there is one. 3. Select **Register**. Stargate asks your connected Canton wallet to sign the registration transaction on Canton. The fee comes from your CC on Canton. After the registration, the transfer continues. Stargate offers **Register** only when the recipient is the Canton wallet that you connected. For any other recipient, Stargate does not offer **Register** and tells you to ask the recipient to register. Only the recipient can register, with their own Canton wallet and their own CC on Canton. > [!WARNING] > > You must already hold CC on Canton, in a Canton wallet that can sign, to register. If your CC is only on BSC, HyperEVM, or Solana, first get CC into a Canton wallet such as Loop, for example from another Canton wallet or an exchange. Register on Canton, and then bridge CC in. ### Send CC to Canton Use these steps to send CC from BSC, Solana, or HyperEVM to Canton. **1. Check your Canton setup** Your Canton party is registered (see [One-Time Setup](#one-time-setup-register-your-canton-party)), and One-step Transfers is on in Loop. **2. Connect your wallets** Open Stargate. Connect your BSC, Solana, or HyperEVM wallet, and connect your Canton wallet. **3. Choose the route** Select the source chain and Canton Coin. Select Canton as the destination chain. **4. Choose the recipient** Select your connected Canton wallet as the recipient, or paste a full party ID. A full party ID starts with the party hint and `::`, for example `alice::1220…`. Do not paste only the 64-character part. Stargate offers **Register** only for your connected Canton wallet. **5. Approve and send** Review the fee in the source chain's native token. Approve the transaction in your source wallet. **6. Receive on Canton** The CC arrives in your Loop wallet. If One-step Transfers is off, accept the incoming offer in Loop within 24 hours. Stargate does not send to an unregistered recipient. See [One-Time Setup](#one-time-setup-register-your-canton-party). ## Track a Transfer Stargate shows the status of each transfer. You can also find the transfer on [LayerZero Scan](https://layerzeroscan.com) from the link in Stargate. ## Solana Wallets A send of CC from Solana uses Solana's v1 transaction format. Your wallet must be able to sign it. When you send, Stargate checks whether your wallet reports v1 support. If it does not, Stargate stops the send before your wallet signs and says that the transaction requires a wallet that supports Solana v1 transactions. Transfers into Solana are not affected. | Wallet | Signs Solana v1 transactions | | - | - | | Backpack | Yes | | Jupiter browser extension | Yes | | OKX Wallet browser extension | Yes. The wallet reports v1 support. | | Phantom browser extension | Only if Phantom has turned on v1 support for your wallet. Phantom controls this setting. | | Solflare | No | | Coinbase Wallet | No | | Glow | No | | Ledger | No | | Trezor | No. Trezor says support is due in its next firmware release. | This table shows wallet support on October 28, 2026. Mobile apps were not checked. If you use a Ledger or Trezor account inside Phantom, Solflare, Backpack, Jupiter, or OKX, the device signs the transaction. Expect it to fail until the device firmware supports v1 transactions. ## HyperCore On HyperCore, bridged CC is the spot token `LZCC`. CC moves between HyperEVM and HyperCore through the Hyperliquid [asset bridge](https://docs.layerzero.network/v2/developers/hyperliquid/hyperliquid-concepts.md#10-transfers-between-hyperevm-and-hypercore) at `0x20000000000000000000000000000000000004E7`. ### Move CC to HyperCore Select Hyperliquid (HyperCore) as the destination chain, as in [Bridge Out of Canton](#bridge-out-of-canton). The CC arrives as `LZCC` at the same address on HyperCore in one transfer. The destination is an EVM address, so connect an EVM wallet such as MetaMask, or have its address ready. The destination must be an EOA that you control, because HyperCore does not support multisig receivers. It must already be activated on HyperCore: an address is activated by its first incoming transfer on HyperCore, which costs 1 USDC. Stargate does not send to an address that is not activated. [Activate it on HyperCore](https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/activation-gas-fee) first. If your CC is already on HyperEVM, activate the address on HyperCore first (see above). Then transfer the CC to the asset bridge address `0x20000000000000000000000000000000000004E7`. The `LZCC` balance appears at the same address on HyperCore. ### Move CC from HyperCore to Canton HyperCore has no direct route to Canton. Move the CC to HyperEVM first, in two steps. 1. Hold at least 0.001 HYPE on HyperCore for gas. On HyperCore, spot-send `LZCC` to the asset bridge address `0x20000000000000000000000000000000000004E7`, or select Hyperliquid (HyperCore) to HyperEVM in Stargate. The CC appears at the same address on HyperEVM. 2. Bridge the CC from HyperEVM to Canton, as in [Send CC to Canton](#send-cc-to-canton). Hold HYPE on HyperEVM for the fee. ## If Something Goes Wrong | What you see | What it means | What to do | | - | - | - | | Stargate says the validator has not vetted a LayerZero package | Your wallet's node does not have the LayerZero packages | Ask your wallet provider to vet the full LayerZero package set, not only the named package, or use Loop | | Stargate says the recipient party is not registered | The Canton party has not registered | If it is your connected Canton wallet, select **Register** and sign in that wallet. The fee is paid in CC on Canton. Otherwise, ask the recipient to register on Canton with their own wallet. | | Stargate says your CC is in one holding | The amount and the fee must come from different holdings | Receive a second transfer of at least the fee from another wallet or an exchange. Then send again. The error message also suggests a transfer to yourself. In Loop, receive a second transfer instead. | | Stargate shows `Invalid request` when you send from Canton or register | Your Loop wallet has more than 200 holdings. The request can list at most 200 holdings. | Reduce the number of holdings in your wallet, then try again. If you cannot, [contact the LayerZero team](https://layerzeronetwork.typeform.com/to/U9hMgxf1). | | Stargate shows an internal error when you send from Canton | The send would need more than 100 holdings. A send can use at most 100 holdings. | Merge small holdings, or send a smaller amount | | Stargate says the recipient's namespace is already registered to a different party | That fingerprint belongs to another party. Stargate reports this when it builds the transfer, not when it checks registration. | Do not send to this party | | Stargate says the transaction requires a wallet that supports Solana v1 transactions | Your Solana wallet does not report v1 support | Use a wallet from the [Solana Wallets](#solana-wallets) table that signs v1 | | CC sent to Canton has not arrived | The party may not be registered, or an offer may be waiting | See [Troubleshooting](https://docs.layerzero.network/v2/developers/canton/canton-coin/troubleshooting.md) | | You see an incoming CC offer in Loop | One-step Transfers was off | Accept the offer within 24 hours | For other problems, see [Canton Coin Troubleshooting](https://docs.layerzero.network/v2/developers/canton/canton-coin/troubleshooting.md).