​
Transaction Types

c8ntinuum supports two transaction types:

​
Ethereum Transactions

Standard EVM transactions are submitted through Ethereum-compatible JSON-RPC. Confirm the exact transaction-type matrix against the target ctmd release before relying on newer Ethereum transaction types.

​
Cosmos Transactions

Cosmos SDK transactions using Protobuf-encoded messages. Can contain multiple messages in a single transaction (e.g., delegate + vote in one tx).

​
Transaction Lifecycle

​
1. Submission

Transaction is submitted via JSON-RPC (eth_sendRawTransaction) or Cosmos SDK.

​
2. Validation (CheckTx)

  • Signature verification
  • Fee and balance checks
  • Nonce validation
  • Gas limit verification

​
3. Mempool

Valid transactions enter the mempool and are broadcast to validators. c8ntinuum supports nonce gap queuing — transactions with future nonces are queued locally and promoted automatically.

​
4. Execution (DeliverTx)

  • EVM bytecode execution with gas metering
  • State changes committed to the Cosmos SDK store
  • Receipt generation with bloom filters and logs

​
5. Finality

After a transaction is included in a committed block, c8ntinuum has 1-block finality under standard CometBFT. Expected block time is 4s.

​
Transaction Ordering

Transactions are ordered by effective tip:
  • Ethereum: min(gas_tip_cap, gas_fee_cap - base_fee)
  • Cosmos: (fee_amount / gas_limit) - base_fee
Higher tips = higher priority, regardless of transaction type.

​
Receipts

c8ntinuum generates Ethereum-compatible transaction receipts with standard fields: transactionHash, blockHash, blockNumber, from, to, gasUsed, effectiveGasPrice, contractAddress, logs, logsBloom, status