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

WalletSupportNotes
MetaMaskBrowser extension and mobileAdd c8ntinuum as a custom network.
RabbyBrowser extensionAdd c8ntinuum with the same EVM network values.
Coinbase WalletBrowser extension and mobileAdd c8ntinuum as a custom network where custom networks are supported.
WalletConnect-compatible walletsMobile wallet protocolDapps should advertise c8ntinuum as eip155:2184.
Ledger NanoHardware wallet through an EVM walletLedger Nano S Plus and Nano X are supported through MetaMask, Rabby, or another EVM wallet using the Ledger Ethereum app and derivation path.

​
Mainnet network details

Use these values when a wallet asks for manual network configuration.
FieldValue
Network Namec8ntinuum
RPC URLhttps://public-evm-rpc.c8ntinuum.com
Chain ID2184 / 0x888
Currency SymbolCTM
Block Explorerhttps://ctmscan.io
For step-by-step wallet setup, see Add c8ntinuum Mainnet to Wallet.

​
Testnet network details

FieldValue
Network Namec8ntinuum testnet
RPC URLhttps://public-testnet-evm.c8ntinuum.link
Chain ID2185 / 0x889
Currency SymboltCTM
Block Explorerhttps://testnet.ctmscan.io
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.
MetadataValue
Namespaceeip155
Chaineip155:2184
Native currencyCTM
RPC URLhttps://public-evm-rpc.c8ntinuum.com
Explorer URLhttps://ctmscan.io
{
  "chains": ["eip155:2184"],
  "rpcMap": {
    "2184": "https://public-evm-rpc.c8ntinuum.com"
  }
}

​
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.
WorkflowWallet behavior
Account generationWallets generate Ethereum-compatible eth_secp256k1 accounts. The EVM address is the primary wallet address.
Account selectionUsers choose an Ethereum-style account in MetaMask, Rabby, Coinbase Wallet, a Ledger Nano (S Plus or X) through an EVM wallet, or a WalletConnect-compatible wallet.
Network selectionWallets must be switched to chain ID 2184 for mainnet or 2185 for testnet before signing.
Transaction constructionDapps request standard EVM transactions with eth_sendTransaction; wallets fill or confirm nonce, fee, gas, recipient, value, and data.
SigningBrowser and mobile wallets sign in-app. Ledger Nano signs through the Ledger Ethereum app and the connected EVM wallet.
BroadcastingMost wallets broadcast through their configured RPC after signing. Custody systems can broadcast offline-signed transactions with eth_sendRawTransaction.
ConfirmationWallets and dapps should poll eth_getTransactionReceipt and treat status == 1 as success.
For custody and exchange systems that construct transactions without an interactive wallet, see Offline Signing and Broadcasting.

​
Wallet support matrix

Wallet pathAccount generationTransaction constructionSigningBroadcastingConfirmation
MetaMask browser/mobileGenerates or imports Ethereum-compatible accounts.Dapps request eth_sendTransaction; users confirm recipient, value, fees, and data.In-wallet software signer, or Ledger when connected.Wallet broadcasts through the configured c8ntinuum RPC.Wallet activity, CTMScan, or eth_getTransactionReceipt.
Rabby browserGenerates or imports Ethereum-compatible accounts.Dapps request standard EVM transactions with chain ID 2184.In-wallet software signer, or Ledger when connected.Wallet broadcasts through the configured c8ntinuum RPC.Wallet activity, CTMScan, or eth_getTransactionReceipt.
Coinbase WalletGenerates or imports Ethereum-compatible accounts where custom networks are supported.Dapps request standard EVM transactions after the network is added.Browser or mobile wallet signer.Wallet broadcasts through the configured c8ntinuum RPC.Wallet activity, CTMScan, or eth_getTransactionReceipt.
WalletConnect-compatible walletsWallet owns account generation; dapps advertise eip155:2184.Dapps submit EVM transaction requests through WalletConnect.Wallet signs in-app after the user approves the request.Wallet broadcasts through its configured RPC or connected session policy.Dapp should poll eth_getTransactionReceipt; users can also inspect CTMScan.
Ledger Nano through an EVM walletLedger Ethereum app derives Ethereum-compatible accounts on the selected path.Connected EVM wallet constructs the transaction and displays the signing prompt.Ledger Nano S Plus or Nano X signs through the Ledger Ethereum app.Connected EVM wallet broadcasts through the configured c8ntinuum RPC.Connected wallet activity, CTMScan, or eth_getTransactionReceipt.

​
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: 
0xc8Fb80fCc03f699C70ff0CC08C09106288888888
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

Use caseAddress format
EVM wallets, contracts, JSON-RPC, and token imports0x...
Cosmos account UX, REST queries, and IBC-facing account flowsc8...
Validator operator addressesc8valoper...
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

SymptomLikely causeFix
Wallet shows the wrong chainChain ID was entered as a different value.Edit the custom network and use 2184 or 0x888.
Wallet says the network is unsupportedThe wallet has not added c8ntinuum as a custom EVM network.Add the mainnet values from this page manually.
Transaction cannot be sentAccount has no native CTM for gas.Fund the account with CTM before sending transactions or token transfers.
Token is not visibleThe ERC-20 was not imported into the wallet UI.Import the token contract address manually and confirm it on CTMScan.
MetaMask mobile opens the wrong networkThe mobile app is still connected to another chain.Switch networks inside MetaMask mobile before approving the dapp connection.
Ledger Nano signing fails or shows an unexpected addressThe connected EVM wallet is using a different derivation path or Ledger app.Open the Ledger Ethereum app on the Nano S Plus or Nano X and use the Ethereum path documented in Accounts.
RPC is unavailablePublic endpoint is temporarily unreachable or blocked by local networking.Retry later, check https://public-evm-rpc.c8ntinuum.com, or use a documented provider when more are published.
Explorer links do not openExplorer URL is missing from the custom network.Set the block explorer URL to https://ctmscan.io.