The Anatomy of Solana Trading Volume
A volume figure is a sum of swap legs, not a measure of interest. This note takes the number apart: the atomic swap, side counting, route attribution and time windows.
01Market structureRead the note
How trading volume forms on Solana
A volume figure is not a measure of interest. It is the sum of swap legs that a particular indexer decided to count, on venues it decided to include, inside a window it chose. This desk takes that number apart — where the trade happened, which pool absorbed it, and what the print can and cannot tell you.
The console is a third-party execution product on a separate site. This desk does not run it, does not sell it, and publishes no performance claims about it.
What this desk covers
Three questions come up every time somebody looks at a Solana chart and does not trust it. Each has a research area on this site.
Where the number came from
Venue classes, route attribution, indexer conventions, and the reason an aggregator's share cannot be added to the AMM share underneath it.
What is actually behind the price
Pool reserves, bonding-curve arithmetic, depth at a given order size, and how a migration resets every one of those figures.
Whether the print is broad or narrow
Wallet distribution, timing structure, size clustering, and the grey zone where legitimate market making looks like manufactured flow.
Featured field notes
Long-form mechanism notes. Each one carries its own table, checklist or worked example, and each states plainly where the method stops working.
Where Solana Volume Comes From
Aggregators, AMMs, order books and launch curves each contribute a different kind of volume, and their shares cannot simply be added together.
05Market structureRead the note
Organic Volume vs Manufactured Volume
What each pattern looks like in raw transaction data: wallet distribution, timing regularity, size clustering, round trips — and the honest grey zone in between.
07MeasurementRead the note
Curve Liquidity vs Pool Liquidity
A bonding curve and a constant-product pool both quote a price, but their depth profiles differ in shape, in ownership and in what a single buy does to them.
03Liquidity and depthRead the note
Research areas
Market structure
How Solana venues are organised, how a trade is attributed to one of them, and why two dashboards can report two different numbers for the same token.
4 field notesLiquidity and depth
What sits behind a price on Solana: pool reserves, bonding-curve arithmetic, depth at a given size, and what changes when a token moves venue.
4 field notesMeasurement
Methods for turning raw chain data into a defensible number, and for telling a broad market from a narrow one that only looks broad.
2 field notesWhen measurement turns into execution
Measurement and execution are different jobs with different failure modes. Reading a pool tells you what an order would cost; it does not place the order, split it across venues, or keep a schedule running while you sleep. Once a reader moves from the first job to the second, the questions change: which venues does the tool actually route through, how does it handle a failed transaction, and what does the on-chain record look like afterwards.
This desk does not build or operate that software. If you want to see what a multi-venue execution surface looks like before deciding whether you need one, you can See multi-DEX volume tooling and then come back and measure the result with the method in the campaign note.
How this desk works
Mechanism before opinion
Every note starts from what the program actually does — the accounts it touches, the arithmetic it applies — and only then discusses what a reader should conclude.
MethodProtocol facts and labelled math
Numbers appear only as protocol constants, as figures from a named public source, or as arithmetic that is explicitly labelled illustrative. No survey statistics, no invented case studies.
SourcesWhat is out of scope
No price targets, no signals, no ranking of tokens, no performance claims for any tool. Where a subject is contested, the note says so instead of resolving it for you.
Scope