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.
CRC20 Tokens Cross Space
This tutorial guides developers on transferring any CRC20 token from Core Space to eSpace, The goal is to transfer a CRC20 token (A) issued on coreSpace to become an ERC20 token (eA) in eSpace. Currently, if there is no corresponding token in eSpace, it's not possible to use the official cross-space bridge directly.
CrossSpaceCall
CIP-90 introduces a new internal contract: CrossSpaceCall. CrossSpaceCall enables CFX and data to be transferred between the two spaces.
CrossSpaceCall Contract
Detail explain of CrossSpaceCall contract
eSpace Mapped Addresses(Cross Space)
Mapped addresses in cross-space operations
EVM Compatibility
EVM Compatibility of Conflux eSpace
Internal Contracts
Conflux introduces several built-in internal contracts for better system maintenance and on-chain governance. Now Conflux has seven internal contracts. These contracts provide solidity interfaces defined here. These function can only be called via CALL or STATICCALL operation. Using operation CALLCODE or DELEGATECALL to interact with internal contracts will trigger an error.