The Kalshi volume controversy: what platform founders should measure

What was reported, and what is disputed

On September 21, CoinDesk reported repetitive trade-size patterns in Kalshi’s Bitcoin and Ether perpetual futures. The report described unusual activity and the questions it raised. Repetition alone does not establish collusion or wash trading.

In its September 22 response, Kalshi rejected the wash-trading allegations. It attributed the patterns to market-making incentives and traders taking opportunities against quotes. Kalshi also distinguished the perpetuals controversy from its prediction-market business.

These are a report and the company’s response, not a finding of proven fraud. Do not turn a dispute about one product into a settled claim about every market on the venue.

Volume and liquidity answer different questions

Volume describes completed activity over a period. Liquidity describes the orders available now and the execution a new order might receive. A large historical number cannot tell a member what happens when they try to exit a particular position.

For a market your community intends to use, inspect the spread, available size near the current price, and the likely effect of a larger order. Recheck during important events. Screenshots of historical volume are a poor substitute for the current book.

Define the unit before comparing numbers

Prediction-market statistics can count contract notional, traded cash value, or other measures. A number is not comparable merely because it has a dollar sign. Document the definition, time window, included products, and whether both sides are counted.

Likewise, eligible builder-fee volume is not necessarily total displayed activity. The fee guide explains why a revenue model must use the fee-bearing activity of the product being offered.

Measure whether a community is becoming a business

• External participation: exclude owner testing and identify the limitations of wallet counts.
• Repeat use: check whether participants come back for another event.
• Execution: inspect actual spread and depth for the relevant market and order size.
• Economics: reconcile fee receipts, incentives, partner payouts, and operating costs.
• Support: record funding, approval, rules, and settlement questions.

On-chain records can improve inspectability, but do not make manipulation impossible or prove that wallets belong to distinct people. Publishing a methodology is more useful than declaring that one headline number proves success.

Use the community pilot scorecard to evaluate your own launch. Floatout provides the interface and operating tools. Your recurring audience and actual economics still need to be demonstrated.