Why two address formats
Conflux Network has two execution environments under one consensus. Each uses a different address format because they are different VMs underneath:
- Core Space uses Conflux's CIP-37 base32 address format with built-in error detection. Mainnet addresses start with
cfx:(e.g.,cfx:aakd0e7yh3kabskanjugzaadfpxbhe8tj9ymbn0ubr). - eSpace uses Ethereum's standard EIP-55 hex format. Addresses start with
0x(e.g.,0x1B3F4C...).
The address format itself encodes which space the address belongs to. Sending to the wrong format fails at the network level — funds are not lost, the transaction is rejected.
How to recognize each format
| Format | Starts with | Example | Length |
|---|---|---|---|
| Core Space mainnet | cfx: | cfx:aakd0e7yh3...ubr | 47 chars |
| Core Space testnet | cfxtest: | cfxtest:aamsxq3kp...f3 | 51 chars |
| eSpace (mainnet/testnet) | 0x | 0x1B3F4CF8e3D9F2a8e4... | 42 chars |
What this means for sending
- Sending to a
cfx:address sends within Core Space. Use Core Space CFX. - Sending to a
0xaddress sends within eSpace. Use eSpace CFX. - Cross-space sends require bridging — see Move CFX between Core and eSpace.
Conflux Wallet labels every address by space when you copy or paste, and warns you before any cross-space mistake. The address format itself prevents the most common error.
Hex address (0x...) caveat
The eSpace 0x... format is the same format Ethereum uses. Sending Ethereum to a Conflux eSpace 0x address sends Ethereum to a different chain entirely — Ethereum and Conflux are different networks even though they share address format. Always check which network you're on, especially when copying addresses across wallets.
Cross-space mapping
A Core Space address cfx:aa... and an eSpace address 0x1B3F... derived from the same seed phrase are DIFFERENT accounts. They are linked by your wallet, not by the protocol — your seed phrase generates both. To move funds between them, use the cross-space bridge.