Differences from Ethereum - c8ntinuum Docs

This page is a builder-focused quick reference. For the full feature-by-feature compatibility matrix and “what’s enhanced” coverage, see the canonical EVM Compatibility page.

Quick Reference

Area	Ethereum	c8ntinuum
Block time	~12 seconds	Expected 4s
Finality	Multiple confirmations are common	1-block finality under standard CometBFT
Reorganizations	Possible	Governed by CometBFT BFT consensus
Consensus	Proof of Stake (Gasper)	CometBFT (2/3+ validator agreement)
Base fee destination	Burned	Burned
Address format	`0x` only	`0x` + `c8` (Bech32 alias)
Chain ID	Single integer	Dual: Cosmos string + EVM integer (`8`)
Cross-chain	Bridge protocols	Native IBC
Max contract size	24.576 KB (EIP-170)	EVM-compatible; confirm release-specific overrides against target `ctmd`
Precompiles	Standard Ethereum set	Standard + Cosmos modules + zk/PQ/Solana/VRF

Smart Contracts

All standard EVM opcodes are supported
ERC-20, ERC-721, ERC-1155 and other standards work identically
Additional precompiled contracts provide access to Cosmos modules and advanced cryptographic primitives
Pre-deployed contracts (Multicall3, Permit2, WETH9, Safe, etc.) are available at genesis

Transactions

Supported types: Confirm the exact transaction-type matrix against the target ctmd release before relying on newer Ethereum transaction types
Dual transaction types: Both Ethereum and Cosmos SDK transactions are supported
Ethereum transactions are wrapped in MsgEthereumTx for Cosmos SDK processing
Transaction ordering is by effective tip (gas priority), same as Ethereum

Gas & Fees

EIP-1559 fee market is fully supported
Base fee is burned, unused gas refunds follow EVM/EIP-1559 behavior, and fee-market parameters are governed through the governance module. See Gas.
Use eth_estimateGas through the standard EVM RPC flow and verify provider behavior for production transactions

JSON-RPC

Common eth_*, web3_*, and net_* methods are expected on Ethereum-compatible endpoints
Mining-related methods return stub values (CometBFT consensus, not PoW)
txpool_* methods require compatible node configuration
WebSocket endpoints are published; subscription limits are provider-dependent

Account Model

Every account has dual representation: 0x hex and c8 Bech32
Both reference the same underlying account
HD derivation path: m/44'/60'/0'/0 (Ethereum-compatible, coin type 60)
EIP-7702 Set Code is fully supported for EOA code delegation