About the Order Flow Desk
One subject, treated seriously: the commercial arrangements that sit between a signed Solana transaction and the counterparty that ends up trading against it.
What this desk covers
Order Flow writes about execution arrangements on Solana. That means the businesses on the path rather than the arithmetic of a swap: who builds a quote and how they are paid, whether a fill came from a pool or from a counterparty that could have refused, what an order flow auction sells and to whom, what a private submission path changes, and what each of those costs the trader.
The scope deliberately excludes the introductory layer. There is no page here explaining what slippage is or how a constant-product curve produces price impact, because that material is abundant and because repeating it would crowd out the part that is not covered well anywhere: the arrangements.
Who it is written for
Three kinds of reader. Traders who already understand execution mechanics and have started noticing that the same trade behaves differently depending on which interface they used. Desk operators who run repeated sequences and need a configuration they can defend rather than one they inherited from a default. Analysts who need the vocabulary to be precise, because a conversation about order flow collapses immediately if internalisation, auction and routing are used loosely.
The material assumes comfort with basis points, distributions and the idea that a cost can be embedded rather than itemised. It does not assume any prior knowledge of market microstructure terminology, and where a term from traditional markets is imported, it is defined on first use.
How the work is produced
Each piece follows the same discipline. Name the arrangement. State who is paid and out of what. State what the trader gives up. Then describe how a reader could check any part of it themselves. Where a check is not possible, that is said plainly rather than covered with a confident-sounding metric.
Sources are public documentation and the transaction record. Protocol behaviour comes from the Solana and validator client documentation. Service behaviour comes from the service own published material, usually its developer documentation rather than its product pages, because an API surface describes what a system actually controls. Nothing here is based on private conversations, and nothing is based on data we cannot point at.
Numbers on this site
There are exactly two categories, and every number belongs to one of them. Protocol constants are facts anyone can verify: the base fee of 5,000 lamports per signature, the roughly 400 millisecond slot target, the nine decimals on SOL. Illustrative arithmetic is everything else, and it is labelled as illustrative every single time, with its inputs stated so a reader who disagrees can substitute their own and redo the calculation.
What you will not find is measured market data presented as ours. This desk does not run a trading operation, does not sample fills at scale, and therefore has no basis for publishing fill statistics, price improvement percentages or latency figures. Where such numbers would be the natural thing to publish, the page says instead what you would need to measure and how.
On naming services
Named routers, relays, block engines and auction operators appear where their mechanisms are documented publicly. They are described, not ranked. There is no scoring, no recommendation and no best-of list anywhere on this site, for a simple reason: ranking execution services requires comparing outcomes against counterfactuals, and the counterfactual does not exist. Structure can be described honestly. Superiority cannot.
What you will not find here
- Rankings, scores, star ratings or recommendations of execution services.
- Fill statistics, price improvement figures or latency measurements attributed to this desk.
- Testimonials, reader counts or review aggregates of any kind.
- Named authors with invented biographies, credentials or photographs.
- Predictions about tokens, prices or launches.
- Claims that any arrangement removes execution risk rather than reducing a specific part of it.
Corrections
This subject changes through company announcements rather than protocol upgrades, which means a factually correct page can become wrong without anything visible happening on chain. When that occurs, the page is corrected in place and the change is described rather than quietly applied. If you can point at documentation that contradicts something published here, the contact page explains how to send it.
Independence
The desk links to one commercial execution product in article footers and in the header button. That link is placed by us, it is not sold, and it does not influence what any article says. No named service pays for coverage, no ranking exists to be bought, and nothing on this site is written in exchange for anything. If that ever changes, the change will be stated here before it appears anywhere else.