About The Volume In Context Desk

Volume in Context is written by The Volume in Context Desk, an editorial byline rather than a named individual. There is no invented author, no photograph, no fabricated biography and no claimed credential. What the desk offers instead is a method you can check: every page states how a figure is assembled before it says what the figure means, and every number is either a protocol fact, a labelled illustrative pair, or something you are told how to pull yourself.

What this desk covers

One idea, worked through properly. The same volume figure means different things on a launchpad bonding curve, in a freshly seeded pool and in an established pair, and most published comparisons ignore that. Five long explainers and a glossary work that idea out in detail: the definition itself, the structural difference between curve and pool, the turnover ratio, a written comparison procedure, and a catalogue of the comparisons that break most often.

The subject is deliberately narrow. A site that covers everything about token data shallowly is less useful than one that covers a single confusion thoroughly, and this confusion is worth the space because it produces wrong answers even for careful readers using good data.

How numbers are handled

Three categories of number appear on this site, and nothing else does.

• Protocol facts. Things that are true of the systems being described, such as how a constant-product formula responds to order size, or that Solana charges a fixed base fee per signature. These are stated plainly and are checkable against primary documentation.
• Labelled illustrative pairs. Invented figures chosen by the desk to isolate one variable, always inside a block that says so. Every worked example on this site is of this kind. None of them describes a real token and none of them is observed market data.
• Figures you are told how to obtain. Where a page says to divide volume by depth, it means the depth on the token page in front of you, or the reserve balances you read from an explorer. The desk does not publish a measurement and ask you to trust it.

What never appears: fabricated statistics, invented review counts, star ratings, testimonials, case studies with made-up outcomes, or backdated publication dates. If a claim would need data the desk does not have, the claim does not get written.

The stance the site takes

Produced volume is not the same thing as demand. That sentence is the editorial position of this site and it is applied consistently, including in the places where it would be commercially convenient not to apply it. Volume records that trades occurred and how large they were. Round trips add to it while leaving net position unchanged, and no indexer nets them out. Getting from flow to a statement about demand requires evidence about position changes and about who holds what afterwards, which is a different investigation with different sources.

This is not a claim that volume is worthless or that anyone producing it is doing something improper. Placing swaps is ordinary activity that pays real fees and settles like any other trade. The point is narrower and firmer: the metric does not carry the weight people put on it, in any venue, and no amount of additional volume data changes that.

What is out of scope

No price views or forecasts. No token ratings, rankings or reviews. No recommendation to buy, sell or hold anything. No claims about what a figure predicts. No coverage of specific live tokens, because that would require presenting observed data the desk is not positioned to verify, and unverified specifics are exactly what this site argues against.

The site also does not audit the tools it references. Where a page points at a commercial console, it does so to describe what such a tool exposes, because the settings on the production side are the same variables the reading side is trying to infer. That is a description, not an endorsement, and no page here asserts anything about results.

Sourcing

External links go to primary documentation roots rather than to secondary summaries: the Solana documentation, the Solana program documentation, the public explorer, and the documentation published by the pool programs being described. Where a mechanism is described, the description is written so that it can be checked against those sources rather than taken on trust.

The desk does not link to sources it has not read, does not cite figures it cannot point at, and does not use a citation as decoration for a claim the citation does not actually support.

Corrections

Mistakes get corrected rather than defended. If a mechanism is described wrongly, a formula is stated incorrectly, or an illustrative example contains an arithmetic error, write to the desk and it will be fixed. Corrections to substance are made in place and the page's modification date reflects the change.

The most useful corrections are specific: which page, which paragraph, and what the correct version is. Requests to cover a particular confusion are also welcome, and the criterion for taking one on is whether it can be explained mechanically rather than asserted.

Contact details are on the contact page. The site's data practices, which are short because there are almost none, are on the privacy page. The vocabulary used across the site is defined in the glossary.