🗃️ Infrastructures
5 items
🗃️ SDKs
1 item
📄️ EVM Compatibility
EVM Compatibility of Conflux eSpace
📄️ JSON-RPC Compatibility
JSON-RPC compatibility with Ethereum
📄️ Transaction
Conflux eSpace initially supports transactions in the Ethereum 155 format (legacy transactions). After the v2.4.0 hardfork, it starts to accept type-1 (EIP-2930) and type-2 (EIP-1559) format transactions. This compatibility enables seamless transition for mainstream Ethereum SDKs and tools. Type-3 transactions (EIP-4844) are currently not supported.
📄️ eSpace Mapped Addresses(Cross Space)
Mapped addresses in cross-space operations
📄️ CrossSpaceCall Contract
Detail explain of CrossSpaceCall contract
📄️ Run an eSpace Node
eSpace and Core Space share a common node program, so please refer to the Core Space Node Operation Guide for running a node. Below are some eSpace specific configurations.
📄️ Deployed Contracts
Useful utilities contract addresses for Conflux eSpace
📄️ CIP-90
Conflux has a virtual machine that is similar to the EVM. However, there are still some considerable differences between Conflux and Ethereum. Conflux uses a different transaction format and a different rule for generating addresses from public keys. These differences often make it hard to port EVM compatible dApps to Conflux. Replacing CIP-72 and CIP-80, CIP-90 introduces a transaction execution environment called the Conflux eSpace. eSpace achieves full EVM compatibility without changing the existing accounts and transactions.