Fake volume leaves marks in the trades: one wallet buying and selling the same token in a transaction, wallets that end the day where they started, two wallets taking opposite sides of the same size in the same block, and a handful of signers doing most of the volume. This dataset measures each of those for every token traded on a Robinhood Chain DEX, one row per token per day, from the chain's decoded DEX trades across Uniswap v2, v3 and v4, Pons, PancakeSwap, Aerodrome-style and other venues. Each signal has its own volume, USD figure and share, and five flags turn them into yes or no with thresholds written in the column descriptions.
Most buyers start by filtering Flags_Raised >= 2 and sorting by Volume_USD, then read Flagged_Volume_Share to see how much of the reported volume is left once those trades are taken out. The flags are signals, not proof: a market maker that quotes both sides can trip Round_Trip, and a busy public router shows up as Top_Entry_Contract with thousands of signers. Read the signer counts next to the shares.
Use cases
Fake volume checks before listing or ranking a Robinhood Chain token
Screening Pons and Uniswap tokens for self-trades and round-trip wallets
Finding market-maker bot clusters behind one private contract
Discounting reported volume by its flagged share in backtests
Table
37 columns · free sample for the table
robinhood_wash_trade_flags
37 columns
One row per token per UTC day on Robinhood Chain DEXs: self trades, round-trip wallets, mirror trades, bot wallets, concentration and flags.
robinhood/robinhood-wash-trading/robinhood_wash_trade_flags<YYYY-MM-DD>.parquetone file per UTC day
Send this dataset’s full schema to an assistant and ask it anything. It reads the plain-text brief ↗ first, so the answer comes from the real column list rather than a guess.
Opens a new chat with the question filled in. Nothing about you is sent to Bitquery, and the assistant sees only the public brief.
Delivery
Parquet files in a Requester Pays S3 bucket or a Cloudflare R2 bucket, chosen at checkout. On S3 you download with your own AWS account and AWS bills the transfer; on R2 you download with a read-only API key and pay no egress. Layout:
# robinhood_wash_trade_flags: one file per UTC day
robinhood/robinhood-wash-trading/robinhood_wash_trade_flags<YYYY-MM-DD>.parquet
Download a free sampleNo email needed.
Pay nowName, work email and licence check.
Pay the invoiceBy card or bank transfer.
Download from S3 or R2The team prepares the export and emails the bucket path, plus a read-only API key for R2 orders.
Need new data after your purchase?
Kafka Streams sends new Robinhood Chain data in real time, so your copy can stay current after the files end. It is sold on an Enterprise plan.
One Parquet table, robinhood_wash_trade_flags, with 37 columns: one row per token per UTC day with trades, volume, traders, self-trade, round-trip, mirror-trade and bot measures, the top-wallet concentration, the main entry contract, flagged volume and five flags.
How big is it?
One row per token per day that traded. Robinhood Chain DEXs printed about 1.9 million trades on 10 November 2026; the number of distinct tokens a day sets the row count, and the delivery manifest gives exact rows and bytes.
How do I check whether a token's volume is fake?
Filter robinhood_wash_trade_flags on Token_Address and read Flagged_Volume_Share by day. Then look at which signal drives it: Self_Trade_Volume_Share, Round_Trip_Volume_Share or Mirror_Volume_Share. Top5_Wallet_Volume_Share and Bot_Volume_Share tell you whether a few wallets make the market.
How are the flags defined?
A self trade is one signer buying and selling the token in one transaction. A round-trip wallet bought and sold amounts within 5% of each other that day. A mirror trade is an opposite trade by another signer in the same block within 1% in size. A bot wallet made 100 or more trades of the token that day. Every flag needs at least 20 trades; the thresholds are in each column's description.
How are the numbers produced and checked?
Each measure is computed from the chain's decoded DEX trades, one row per token side of a trade, successful transactions only. A trade's direction comes from which side the DEX contract was on, which split every AMM row cleanly in a test hour on 16 November 2026. Flagged volume counts each trade once even when it trips several signals.
What limits should I know about?
Wallets are transaction signers. One operator with many signers shows up as many wallets, so concentration can read low; the entry-contract columns help there. Market makers and arbitrage bots can trip the round-trip and bot flags without any wash intent. USD is 0 when neither side of a trade has a USD price.
What is left out?
Failed trades and transactions, NFT trades, and venues that are not decoded as DEX trades on Robinhood Chain. Funding links between wallets are not used: two signers funded from one wallet are not joined.
Why Robinhood Chain?
Every Robinhood Chain DEX trade carries its signer, transaction, block and log position, so self trades inside one transaction and same-block mirror trades can be found exactly. Robinhood Chain makes about 10 blocks a second, so the same-block window is tight.
How do I load it?
With DuckDB: SELECT Token_Symbol, Volume_USD, Flagged_Volume_Share FROM read_parquet('robinhood_wash_trade_flags/*.parquet') WHERE Flags_Raised >= 2 ORDER BY Volume_USD DESC LIMIT 50. With pandas: pd.read_parquet('robinhood_wash_trade_flags/').
How current is the data and how is it delivered?
A purchase covers whole UTC days up to the day before delivery. Files are one Parquet file per day, ZSTD compressed, delivered to a Requester Pays S3 bucket; download costs are billed to your AWS account.