How client traffic reaches the node

How client traffic reaches the node A workflow diagram generated by Archify. 01 / Local rejection 02 / HTTP request routing 03 / Transport and response branches 04 / Submission enters consensus Local error · Malformed / subscribe · Local rejection Local error Malformed / subscribe Worker · Client request · HTTP request routing Worker Client request Cache lookup · Immutable read · HTTP request routing Cache lookup Immutable read ORIGIN_WRITE · Valid request · HTTP request routing ORIGIN_WRITE Valid request Retry gate · Origin failure · HTTP request routing Retry gate Origin failure ORIGIN_LB · One read retry · HTTP request routing ORIGIN_LB One read retry ORIGIN_LB · WebSocket stream · Transport and response branches ORIGIN_LB WebSocket stream Cached response · Immutable result · Transport and response branches Cached response Immutable result Origin RPC · Validate submit · Transport and response branches Origin RPC Validate submit Return failure · Write / sticky · Transport and response branches Return failure Write / sticky Ingest / mempool · Ingest accepted · Submission enters consensus Ingest / mempool Ingest accepted Consensus + state · Later execution · Submission enters consensus Consensus + state Later execution hit miss unsafe safe read invalid upgrade failure submission Legend RPC handling Routing gate Ingest Cache / state Edge / origin

Classification governs routing

  • • Valid non-cacheable requests also use ORIGIN_WRITE first.
  • • WebSocket upgrades stream through ORIGIN_LB.
  • • Malformed JSON and subscription calls receive local errors.

Bounded retry

  • • Connection failure or HTTP 502, 503, 504, 520–524 only.
  • • Ordinary or cacheable reads must also be retrySafe.
  • • Writes and sticky methods never replay through the load balancer.

Acceptance is a separate boundary

  • • A returned transaction signature confirms ingest acceptance.
  • • Consensus and state execution happen later.
  • • This is configured topology; ORIGIN_FALLBACK is unused.