Who a trade was with
0.9.53Marketplaces, liquidity pools and trading desks are recognised from published lists and from how addresses behave on-chain, and every label says how sure it is.
In one sentence
A trade's other side is named from published pool addresses, from addresses that trade with dozens of unrelated wallets, and from recurring marketplace fee addresses, and every derived label says what was counted and how sure it is.
Three sources
- Published. RichSwap lists its pool addresses, so its pools are named exactly.
- Derived from behaviour. An address that trades with dozens of unrelated wallets isn't a trader, it's somewhere people trade. Two shapes are recognised: two-sided (buys and sells against many different counterparties, like a market maker) and one-sided (always on the same side, against dozens of wallets, like a pool or a desk).
- Marketplace fee addresses. No marketplace publishes its fee address, so recurring fee addresses are worked out from the sales themselves: an address paid by many unrelated buyers and sellers.
Why not fingerprint the transaction
On our own trades, pool swaps turned out to be plain Taproot spends with nothing structural to match on. What identifies a venue is its address and its behaviour, which is what we record.
How labels are shown
A published pool is named. A derived label says what was counted and carries a confidence level; anything uncertain says so. Venues are exempt from the pair rules in the wash-trade flags, and their side of a trade is never treated as a signal.
Also as plain Markdown. See every methodology page.
Last updated