Learn pages explain how c8ntinuum works and why its design differs from a standard EVM chain. If you need exact network values or deployment commands, use Developer Essentials. If you are building a mental model of the system, start here.

​
Choose a path

ReaderStart withThen read
EVM developerExecution and EVMEVM Compatibility, Transaction Lifecycle, Modules & Precompiles
Cosmos or IBC developerInteroperability and IBCIBC, Cross-chain Verification, ICS20
Protocol readerChain ArchitectureConsensus, Transactions, Precompile Families
Integrator or custodianTransaction LifecycleAccounts, Tokens, Exchange and Custody Integration

​
Concept map

Core Concepts

Accounts, tokens, transactions, IBC, and EVM compatibility.

Chain Architecture

The high-level shape of c8ntinuum’s EVM, Cosmos, precompile, and interoperability layers.

Execution and EVM

How Ethereum-compatible execution fits with native module access.

Interoperability and IBC

Trust-minimized cross-chain communication, IBC, and light-client verification.

Modules & Precompiles

Native precompile families exposed to Solidity contracts.

Transaction Lifecycle

Submission, validation, mempool handling, execution, receipts, and finality.

​
What Learn is for

Learn pages are intentionally conceptual. They explain relationships, trust boundaries, and developer implications. Exact ABI signatures, RPC method availability, endpoint limits, and operational runbooks live in Reference, Documentation, and Node Operations pages.