What is the difference between Conflux Core and eSpace?

Core Space is Conflux's native execution environment with a custom VM, CIP-37 base32 addresses (cfx:...), and storage-collateral mechanics. eSpace is fully EVM-compatible with standard Ethereum 0x addresses and Chain ID 1030. Both run on the same Conflux Network consensus. Most user activity happens on eSpace because most DApps target the EVM.

Can I use MetaMask with Conflux?

Yes, for Conflux eSpace. Add a custom network: RPC https://evm.confluxrpc.com, Chain ID 1030, currency CFX. MetaMask cannot access Conflux Core Space — that requires a Conflux-native wallet like Conflux Wallet or Fluent.

What's the Conflux Chain ID?

Conflux eSpace mainnet is Chain ID 1030. Conflux Core Space is Chain ID 1029. Testnet uses different IDs (eSpace 71, Core 1).

Conflux eSpace

Q: How do I add Conflux to MetaMask?

Settings → Networks → Add network. RPC URL https://evm.confluxrpc.com, Chain ID 1030, Currency symbol CFX, Block explorer https://evm.confluxscan.io. Save. The network is now available for switching.

EVM-compatible execution. Same Conflux Network, Ethereum-style addresses and tooling.

Download Conflux Wallet

Chain ID 1030 · 0x address format · MetaMask compatible

Conflux eSpace is the EVM-compatible execution environment of the Conflux Network (see what CFX is). It runs Ethereum smart contracts unchanged, uses standard Ethereum 0x address format, and works with Ethereum tooling — MetaMask, Hardhat, Foundry, Solidity, ethers.js, web3.js. The eSpace Chain ID is 1030. Conflux Network's other execution environment, Core Space, uses Conflux's native VM and CIP-37 base32 addresses. Both are part of the same Conflux Network and share the same Tree-Graph consensus underneath. Manage both spaces in Conflux Wallet or bridge CFX between them.

Core Space vs eSpace at a glance

	Core Space	eSpace
VM	Conflux native	Ethereum-compatible (EVM)
Address format	cfx:aa... (CIP-37 base32)	0x... (Ethereum hex)
Chain ID	1029 (mainnet)	1030 (mainnet)
Storage model	Storage collateral (CFX-locked)	Standard EVM (gas-only)
Native staking	Yes (protocol-level)	No (use bridge to Core Space)
Tooling	Conflux SDK, Fluent, Conflux Wallet	MetaMask, Hardhat, all Ethereum tooling
DApps	Conflux-native (Swappi via cross-space, ConfluxHub)	Most Conflux DeFi, NFT, GameFi
Smart contract language	Solidity (with Conflux extensions)	Solidity (Ethereum-standard)

Using MetaMask with Conflux eSpace

eSpace works with MetaMask via custom RPC. The values:

Network name: Conflux eSpace
RPC URL: https://evm.confluxrpc.com
Chain ID: 1030
Currency symbol: CFX
Block explorer: https://evm.confluxscan.io

Add the network in MetaMask → Settings → Networks → Add network. After adding, MetaMask manages your eSpace accounts the same way it manages Ethereum mainnet accounts. Limitation: MetaMask only sees eSpace. To use Conflux Core Space (cfx:… addresses, native staking, storage collateral, governance), you need a Conflux-native wallet — Conflux Wallet, Fluent, or another Conflux-compatible wallet.

How Conflux Wallet handles both spaces

Conflux Wallet manages both Core Space and eSpace accounts in the same wallet. The wallet labels every address by its space — when you copy or send to an address starting with cfx:, the wallet treats it as Core Space; addresses starting with 0x are eSpace. The two spaces are linked by your seed phrase but have separate balances and separate transaction histories. Move CFX between them via the in-wallet bridge.

When to use each space

Use Core Space for

Native CFX staking, storage-collateral interactions, on-chain governance voting, Conflux DAO participation, and any Conflux-native DApp that requires Core Space (most native staking pools).

Use eSpace for

DeFi (Swappi, lending protocols), NFTs, EVM-compatible DApps, MetaMask-based interactions, cross-chain bridges that connect to Ethereum or BSC, and most general DApp activity.

Move between them

Conflux Wallet's in-wallet bridge moves CFX between Core and eSpace in one signature. The bridge is implemented as a Conflux protocol-level CrossSpaceCall, not a third-party bridge.