Public data reference

Order Book Spoofing Risk and Liquidity Context

Read the available BTC depth and venue-status observations alongside Vultax’s research on order-book spoofing.

2 tables · 10 rows · observed ExportJSONMarkdownSchemaOpen in Vultax

01 Market snapshot

Reported BTC market depth

Reported cost to move the market by 2%, alongside the corresponding BTC pair and reported turnover.

ObservedObserved 5 rowsWithin this table’s source-time freshness window; prices can change between observations.

Reported BTC market depth. CoinGecko tickers for the configured exchanges; the pack selects each venue’s highest-volume BTC USD, USDT or USDC pair.
ExchangePair+2% depth (USD)−2% depth (USD)Reported 24h volume (USD)Pair status
BinanceBTC/USDT20,531,60221,020,392571,133,192No flag reported
CoinbaseBTC/USD17,966,41720,182,384155,232,229No flag reported
KrakenXBT/USD25,605,46022,305,67868,860,363No flag reported
OKXBTC/USDT14,614,12712,498,036166,856,159No flag reported
GateBTC/USDT18,860,84429,393,753131,578,605No flag reported

Scroll to see all columns.

CoverageCoinGecko tickers for the configured exchanges; the pack selects each venue’s highest-volume BTC USD, USDT or USDC pair.

Depth and turnover are reported by the upstream source, not independently verified executable liquidity.

The upstream pack rounds amounts and may convert missing depth or volume to zero; a reported zero is not proof of no liquidity.

SourcesVultax crypto pack · CoinGecko exchange tickers

02 Market snapshot

Exchange service status

The service-status responses already collected by Vultax.

ObservedObserved 5 rowsWithin this table’s source-time freshness window; prices can change between observations.

Exchange service status. Configured exchange status endpoints; operational status does not establish feed completeness or execution access.
ExchangeIndicatorSource message
CoinbasenoneAll Systems Operational
KrakenminorPartially Degraded Service
Binancenonenormal
OKXnoneAll systems operational
Kalshinoneexchange active

CoverageConfigured exchange status endpoints; operational status does not establish feed completeness or execution access.

The upstream status messages retain the provider’s meaning; different providers use different status vocabularies.

SourcesVultax crypto pack · exchange status endpoints

Take this into the workspace

Order-book risk tools are part of the crypto workspace. Coverage depends on the available venue feeds.

Published research behind this page

Dated write-ups of the same sources. A figure in a study describes the window it was written about, not the snapshot above.

  1. Spoofing is defined by intent, which no market-data feed can observe. Here are the order-book patterns that stand in for it, and where they fail.

  2. Volume is what an exchange reports. Liquidity is what absorbs your order. The two diverge sharply, and the gap between them is measurable.

Coverage and methodology

  • Public tables mirror existing Vultax source packs. They do not include account data, private watchlists or the complete app dataset.
  • Source time, coverage and limitations apply to each table. Missing values are unavailable, not zero.
  • This public mirror provides depth and service context. It does not expose cancellation histories or establish spoofing intent.

Methodology

Related data references