Signatures: the shapes produced activity leaves behind

A signature is a property of a set of trades, never of one trade. Any single swap on Solana is unremarkable: an account authorised it, a program executed it, tokens moved. The information sits in how a few hundred of them relate to each other, which is why every file in this section works on a window rather than on an example.

Each signature below is paired with the explanation that defeats it. That pairing is not a disclaimer bolted on at the end, it is the whole method. A signature that cannot be defeated by an innocent explanation would be proof, and nothing in this section is proof.

What this section answers
What produced turnover looks like in raw transaction data, and how each pattern is measured.
What it will not do
Name a token, wallet or team, or convert a pattern into an expectation about price.
Where it hands off
Collection method lives in Evidence; competing explanations and judgement live in the Grey zone.

3 case files in this section

The shapes produced activity leaves in a transaction record: spacing that is too regular, sizes drawn from a narrow set, round trips that return their own inventory, and counterparty graphs that collapse to a handful of funders.

01Head note

Organic vs artificial volume

The difference between spontaneous and produced turnover is a distribution question, not a label. What each side looks like in raw data, and the six checks that separate them without accusing anyone.

Open the case file
02Timing

Timing and size signatures

Inter-arrival gaps and trade sizes carry more information than turnover ever does. How to read spacing, quantisation and slot alignment, and why each one has an innocent explanation.

Open the case file
03Round trips

Round trips and self-trading

A round trip returns inventory to where it started. How to detect the pattern from token balance deltas, how it differs from ordinary two-sided trading, and what it cannot prove.

Open the case file

Where the signatures section stops

Reading a shape is the easy half. The harder half is gathering the data so that someone else can check you, and deciding how firmly to state a conclusion when several explanations survive. Those two problems have their own sections.

Evidence

How to collect chain data so that a second analyst can reproduce your reading: which fields to store, which to derive, how wallet clusters are built, and where each method quietly stops working.

Open the section

Grey zone

The region where the same on-chain footprint has several honest explanations. Market making, incentive farming, treasury rebalancing and produced flow overlap here, and the correct output is a confidence level rather than a verdict.

Open the section

Glossary

Every term this desk uses, defined once and used the same way everywhere: signatures, cluster edges, confidence bands and the words that are deliberately avoided.

Open the glossary