Skip to main content
cNGN is issued on multiple blockchain networks. Endpoints that move value on-chain (Withdraw, Bridge, and Whitelist Address) identify the target chain with a networkId.

Getting network IDs

Network IDs are environment-specific database identifiers, not fixed enums. Always fetch the current list at runtime or integration time from Get Networks:
Decrypted response payload:
Use the id value as networkId in subsequent requests. Pass ?includeBlockchain=true to include underlying blockchain metadata in the response.

Supported chains

cNGN supports EVM chains (Ethereum, BNB Smart Chain, Polygon, Base, Asset Chain), Tron, and Bantu (XBN). The authoritative list for your environment is always the Get Networks response. Networks with isDisabled: true cannot be used for withdrawals or bridging.
Never hard-code network IDs across environments; test and live environments have different IDs for the same chain. Resolve IDs per environment.

Contract addresses

Verified cNGN token contract addresses for every chain, mainnet and testnet, are listed on the Contract Addresses page. Always verify contract addresses from the official source before interacting on-chain.