This page is a side-by-side EVM/Cosmos lifecycle walkthrough with operational guidance for senders. For the canonical reference on transaction types, ordering, and receipt fields, see Transactions.
c8ntinuum accepts both Ethereum-style EVM transactions and Cosmos SDK transactions. For EVM users, the normal path is familiar: sign, submit, wait for inclusion, read the receipt. The difference is that an EVM transaction can also call precompiles that execute native chain logic.

​
Lifecycle

​
Ordering and nonces

Transactions are ordered by effective tip while preserving nonce semantics for each EVM account. c8ntinuum supports nonce gap queuing, but applications should still manage nonces carefully for high-throughput senders.

​
Finality and confirmations

Protocol finality is one block under standard CometBFT assumptions. Business workflows may wait longer for operational reasons. For example, exchange deposit processing recommends 60 confirmations to absorb RPC, log, receipt, and scanner lag.