Skip to content
YinYang

Product transparency

Whale Feed Methodology

The Whale Feed organizes large Binance Spot BTC/USDT trade events into consistent value tiers. It provides market context—not customer identity, wallet tracing, or a directional trading signal.

Author
By Connor Price, Founder and Lead Developer
Last reviewed
Last reviewed

What the Whale Feed shows

The feed derives from Binance Spot BTC/USDT aggregate-trade events. Each qualifying event records the observed execution price, BTC quantity, estimated USDT value, UTC trade timestamp, aggressor side, and the tier reached by that value.

What “buy” and “sell” mean

The ingestion worker derives side from Binance’s buyer-maker flag. A buy label means the buyer was the taker for the aggregate trade; a sell label means the seller was the taker. It describes the aggressive side of the observed execution, not a complete order, a person’s portfolio, or future intent.

Implemented whale tiers

The thresholds below come directly from ingestion/whale_tiers.py, the current source of truth. A trade is assigned the highest threshold it meets.

  • Dolphin: $100,000 USDT or more
  • Shark: $250,000 USDT or more
  • Whale: $500,000 USDT or more
  • Kraken: $1,000,000 USDT or more
  • Leviathan: $2,500,000 USDT or more
  • Behemoth: $5,000,000 USDT or more

Timestamps and aggregation

Event time comes from the Binance aggregate-trade message and is interpreted in UTC. The activity can also contribute to per-second and per-minute summaries. UI filters may narrow the feed by tier or view, and aggregation can make totals differ from a list of individually displayed events.

What users can reasonably infer

Users can observe that a qualifying amount of BTC/USDT executed on Binance Spot at a given time, price, and aggressor side, then compare that event with contemporaneous price, volume, pressure, and market structure. Repeated events can provide participation context, but the feed does not establish why an event occurred.

What the feed cannot identify

Ordinary Binance Spot aggregate-trade events do not expose a customer’s Binance identity. They also do not contain an on-chain wallet address. An exchange execution is an event in Binance’s internal order book and is not automatically linked to a blockchain deposit, withdrawal, or wallet owner.

The feed therefore does not provide wallet tracking, Binance-account identification, on-chain tracing, profitability tracking, or copy-trading support.

Display, filtering, delay, and access limits

The visible event range, filters, update timing, and history depend on the current product view and entitlement. Guests have the existing limited preview. Signed-in Free access continues, while Whale Feed availability and realtime depth are resolved by current backend plan and beta rules. Exchange or service interruptions can delay events.

Risk and interpretation limits

One large trade does not guarantee price direction. The event may be absorbed, hedged elsewhere, part of a larger execution, or followed by unrelated flow. Treat Whale Feed observations as one source of market context, not financial advice, an order instruction, or evidence of future profitability.