How a volume engine works
The six components every volume engine contains, the data that crosses each boundary, and why the interesting engineering sits in the queue rather than the swap call.
Open the noteEngine notes
Ten notes, each one describing a single part of an automated trading system on Solana. Every note states what the component receives, what it must produce, how it fails under load, and what the design choice costs you somewhere else.
If you are reading the site for the first time, start with how a volume engine works, then follow the pipeline. If you are debugging something specific, the table below is the faster route.
- Notes
- Ten component sheets across three sections
- Format
- Contract in, contract out, failure mode, trade-off
- Scope
- Public Solana mechanics and general system design
- Byline
- The Engine Room Desk
Architecture
The parts a volume engine is assembled from, the interface each one exposes to its neighbours, and what breaks when a boundary is drawn in the wrong place.
Wallet fleet design
Treating many signing accounts as one addressable resource: derivation, roles, balance floors, lease semantics and the ledger that keeps the fleet reconcilable.
Open the noteScheduling and pacing
Turning a budget into a stream of timed intents: token buckets, jitter, session curves, and why a fixed interval is the one shape a scheduler should never emit.
Open the notePipeline
What happens to a single swap between the moment a scheduler emits it and the moment a validator finalises it, stage by stage, with the failure mode of each stage.
The transaction pipeline
Intent to confirmation in seven stages, the contract each stage owes the next, and the specific way each one fails when the network is busy.
Open the noteVersioned transactions and lookup tables
Why the 1232-byte packet is the real constraint, how address lookup tables buy back account slots, and what a table costs you in setup, rent and coupling.
Open the noteCompute budget and priority
Compute unit limits and unit prices as two separate levers, how the product becomes a fee, and how to set both from simulation instead of superstition.
Open the noteReliability
Retries that do not double-spend, backpressure that protects an endpoint instead of hammering it, metrics that expose the truth, and a growth path that does not break on the way up.
Retry, backoff and idempotency
Why a resend on Solana is safe and a rebuild is not, what the blockhash actually guarantees, and how to make the retry loop terminate on evidence rather than on hope.
Open the noteRate limits and backpressure
Credit accounting, concurrency caps, queue depth as the control signal, and how to shed load deliberately instead of letting an endpoint decide for you.
Open the noteObservability for an engine
The metric set that describes a run honestly: landing rate, time to confirmation, cost per successful swap, and the traces that connect a number back to a signature.
Open the noteScaling a run safely
Load testing against the constraint you will actually hit, staged ramps with defined abort criteria, and the four ceilings that stop an engine before compute does.
Open the note