Skip to main content
Available when Canton Coin launches on Stargate and the Value Transfer API.
Canton Coin (CC) on BSC, HyperEVM, Solana, and HyperCore is bridged CC. LayerZero Labs deployed and administers its contracts. It is not native CC.
  • Native CC is the Canton Network’s own token. It exists only on Canton.
  • Bridged CC on BSC, HyperEVM, and Solana is an OFT that LayerZero Labs deployed and administers. Its symbol is CC.
  • LZCC on HyperCore is bridged CC as a spot token, linked to the HyperEVM OFT through the Hyperliquid asset bridge. It is not an OFT.
  • When you send native CC from Canton, the LayerZero CC adapter on Canton locks it, and the OFT on the destination chain mints the same amount of bridged CC. When you send bridged CC back to Canton, the OFT burns it, and the adapter unlocks the same amount of native CC.
  • On HyperCore, the Hyperliquid asset bridge releases LZCC only in exchange for bridged CC on HyperEVM.
  • The Global Synchronizer Foundation, Digital Asset, and the Canton Network did not deploy bridged CC and do not administer its contracts.
Other tokens with the Canton Coin name exist, for example “wCC” on BSC and Base. LayerZero Labs did not deploy them and does not administer them. Check the address in the token table before every transfer.
Canton Coin (CC) is the native token of the Canton Network, where it is also called Amulet.

​
Token Identifiers

Always check the token address before you buy, send, or receive CC. Only the addresses in this table are bridged CC that LayerZero Labs administers. Each address links to the chain’s explorer. On Solana, the OFT is a program, and its state is in a separate store account. The OFT store is the address that other chains set as the Solana peer. Your wallet holds the mint. Every chain uses 6 shared decimals, so a transfer carries at most 6 decimal places. The token named “wCC” on BSC and Base is a different token: 0x6050D829F5a5E0eA758D8357DDcdeC1381699248.

​
Supported Routes

The CC OFTs on BSC, Solana, and HyperEVM are also connected to each other. These guides cover only routes to and from Canton. A single send into Canton can carry at most about 922 million CC. The cap comes from the LayerZero adapter on Canton, which stores the amount as a 64-bit integer in CC’s 10 decimals: (2^63 − 1) / 10^10. It is not a Canton or holding limit. The adapter refuses a larger delivery, and the CC stays burned on the source chain. Every Canton Coin route requires four DVNs: LayerZero Labs, Deutsche Telekom, Twinstake, and Horizen. To send CC into Canton, use Stargate or the Value Transfer API. Both check that the receiving Canton party is registered. Do not call send() on the BSC, HyperEVM, or Solana OFT directly. See Send from Another Chain to Canton for the risks.

​
Fees

The protocol fee is the LayerZero messaging fee plus, on a send from Canton, the LayerZero request fee on Canton.
  • From Canton: you pay the protocol fee in CC. The CC that pays the fee must be in different holdings from the CC that you send.
  • From BSC, Solana, or HyperEVM: you pay the LayerZero messaging fee in the chain’s native token (BNB, SOL, or HYPE).
  • Registration: before anyone can bridge CC into Canton for you, your Canton party must register in the CC adapter’s registry. Registration is a one-time Canton transaction. Your Canton wallet signs it and pays the fee in CC from your holdings on Canton. The app shows the amount. You cannot register from BSC, HyperEVM, or Solana.
The CC OFTs on BSC, Solana, and HyperEVM charge no OFT fee. Stargate, or the partner fees set on your Value Transfer API key, may add a fee. The quote shows it.

​
Choose Your Guide

Bridge with Stargate

For people who hold CC in a Loop wallet or on BSC, Solana, HyperEVM, or HyperCore.

Market Makers and Integrators

Build transfers with the Value Transfer API, then sign and submit them from your own node.

Wallet Operators

What a Canton wallet must support so that its users can bridge CC.
If a transfer does not arrive, see Canton Coin Troubleshooting.