Node roles and their state paths

Node roles and their state paths An architecture diagram generated by Archify. Consensus · active-set participation · Sequencer Consensus active-set participation Execution · finalized payloads · Sequencer Execution finalized payloads Local state · ordered durability · Sequencer Local state ordered durability RPC + subscriptions · reads local state · Sequencer RPC + subscriptions reads local state Consensus · active-set participation · Active validator Consensus active-set participation Execution · finalized payloads · Active validator · pending: diffs; active: execute Execution finalized payloads pending: diffs; active: execute Local state · ordered durability · Active validator Local state ordered durability RPC + subscriptions · reads local state · Active validator RPC + subscriptions reads local state Diff producer · publish to block server · Sequencer Diff producer publish to block server Diff ingestion · height-ordered trusted input · Read-only replica · not consensus verification Diff ingestion height-ordered trusted input not consensus verification Local state · applied replicated state · Read-only replica Local state applied replicated state RPC + subscriptions · reads local state · Read-only replica RPC + subscriptions reads local state finalized blocks apply results state + receipts finalized blocks apply results state + receipts produce diff transport apply diffs state + receipts Sequencer Active validator Read-only replica

Execution roles require the canonical engine

  • • Sequencers and validators execute finalized payloads. A CPU build alone does not satisfy the runtime GPU gates.

Replicas follow replicated state

  • • Read-only replicas trust bootstrap and sequencer diffs; they neither vote nor execute SBF. Pending validators poll diffs only until promotion, then execute finalized payloads.