c8ntinuum provides official EVM network metadata for third-party wallet applications. There is no separate official c8ntinuum wallet application documented in this repository; users connect through EVM-compatible wallets by adding the c8ntinuum RPC, chain ID, currency, and explorer values.

Supported wallets

Mainnet network details

Use these values when a wallet asks for manual network configuration. For step-by-step wallet setup, see Add c8ntinuum Mainnet Beta to Wallet.

Testnet network details

For step-by-step testnet setup, see Add c8ntinuum Testnet to Wallet. For the canonical testnet endpoint and status table, see Network Information - Testnet.

WalletConnect metadata

WalletConnect dapps should expose c8ntinuum as an EVM chain in the eip155 namespace.

Wallet application workflows

No separate official c8ntinuum wallet application is published in this repository. c8ntinuum is integrated through EVM-compatible wallets and wallet protocols using the network metadata above. For custody and exchange systems that construct transactions without an interactive wallet, see Offline Signing and Broadcasting.

Wallet support matrix

Third-party wallet instructions

Use these instructions when documenting c8ntinuum support for third-party wallet users:
  1. Add c8ntinuum as a custom EVM network using the mainnet or testnet values above.
  2. Select an account derived with an Ethereum-compatible path.
  3. Confirm the wallet shows the expected chain ID before signing.
  4. Keep native CTM in the sending account for gas.
  5. For ERC-20 tokens, import the token contract address manually if the wallet does not auto-detect it.
  6. After signing, confirm the transaction in the wallet activity list, CTMScan, or by querying eth_getTransactionReceipt.
Wallet applications should display the EVM address for contract and token flows. If a product also shows the c8... account representation, label it clearly as the Cosmos-format alias of the same account.

Wrapped CTM

c8ntinuum’s wrapped native token is the WETH9-compatible wrapped CTM contract:
Use this address when a wallet, portfolio app, or dapp needs an ERC-20 representation of native CTM. For token model details, see Tokens and Pre-deployed Contracts.

Address formats and conversion

Both the 0x and c8 account formats refer to the same underlying account. Use the Accounts page for key type and prefix details, and the Bech32 precompile when a contract needs to convert between formats.

Common wallet errors