Architecture

Joltzu separates transaction intake, consensus safety, execution and public RPC. EVM contracts and native services meet in one journaled state transition.

One state, many services

Every validator executes the globally ordered transactions against replicated state. Groups distribute consensus work; they do not create separate execution ledgers. A contract call can update native and EVM records atomically.

The journal supports nested rollback. A reverting child call loses its own effects; an outer failure discards the transaction's execution effects. The block coordinator commits state, receipts and head together. Admission nonces and charged fees follow the transaction rules.

Separate durability boundaries

Execution stores and vote/lock stores have separate owners. A validator records signing authorization durably before asking the external signer for a BLS signature. Finality coordinates certified intent, execution and recovery records across these stores. An ambiguous write stops progress until recovery.

RPC and peers

The node's HTTP/WebSocket endpoint is loopback-only. Remote clients reach a separate TLS gateway. Validator peers use authenticated mutual TLS and bounded protocol frames. A TLS identity permits a peer connection; committee membership and vote verification determine consensus authority.