Conflux (CFX): CFX Gas and Core Space Storage Collateral

Core Space uses Conflux-native conventions

Core Space is the original Conflux environment. It uses Conflux transaction formats and Base32 addresses beginning with a network prefix such as cfx. Its virtual machine resembles the EVM but includes Conflux-specific internal contracts, sponsorship and storage collateral.

eSpace exposes Ethereum-compatible RPC, transaction and address behavior for Solidity applications. It is not Ethereum Mainnet, and a 0x address on eSpace has its own balance and contracts. Core Space and eSpace communicate through the documented CrossSpaceCall mechanism rather than sharing application state automatically.

Address format is part of the route

Wallets and exchanges may support only one space or require an explicit network selection. Copying a Core Space address into an eSpace workflow, or assuming the matching account has the intended balance, can fail or send funds through an unsupported route.

Confirm the space, address format, explorer and token representation before transferring. An exchange can perform a supported conversion internally, but an ordinary transaction cannot cross spaces without the designated mechanism.

Concurrent blocks are not simply discarded

Conflux miners create proof-of-work blocks that can reference other recent blocks. Tree-Graph and the GHAST rule select a pivot chain and order the wider block graph into a deterministic transaction sequence, allowing concurrent blocks to contribute rather than treating every non-tip block as wasted.

PoS nodes sign pivot blocks to finalize the proof-of-work ordering. Mining and finality therefore have different roles. A wallet confirmation count and a PoS-finalized state are not necessarily the same signal, so high-value applications should use the documented finality status.

Before signing

Check Core Space or eSpace, the address format, chain configuration and destination support. On Core Space, estimate both gas and storage collateral. Keep CFX available even if an application usually sponsors fees, because sponsorship can be unavailable.

Do not treat CrossSpaceCall as a general bridge guarantee or assume contracts share addresses and state. Verify token mappings, approvals and the final receiving balance on the correct explorer.

Core Space, eSpace or tools

Use Conflux documentation for current RPC estimates and cross-space calls. Review Ethereum when comparing eSpace behavior, and use address or fee tools only after selecting the correct Conflux space. Confirm the destination explorer before broadcasting.

The CFX result needs context

Proof-of-work miners produce concurrent blocks organized through Tree-Graph and GHAST ordering. A proof-of-stake layer signs pivot blocks for finality. Core Space and eSpace share underlying consensus but keep logically separate accounts, contracts and transaction formats.

A Conflux transaction can execute successfully while the application state, contract permission or later exit remains wrong for the user's goal. CFX is the asset shown in the market snapshot. CFX pays gas; Core Space can also lock CFX as storage collateral.

What Conflux users should verify and why this design differs

Conflux parameters and space tooling can change. Sponsored gas and collateral are conditional.

For Conflux, the practical sequence is Choose network, Fund fee asset, Review action, Execute, Check finality. Confirm the official destination and current network, then inspect the final balance, position, receipt or documented exit state that actually completes the task: Use Conflux Core Space or eSpace while understanding addresses, CFX costs, storage and finality.