Open data

Everything measured here is downloadable. Use it, republish it, build on it — the only condition is a credit line.

Licence

Released under CC-BY-4.0. Attribution required: Data: BTC Value Check (btcvc.com)

Datasets

Bitcoin fee-rate history

Per-block fee-rate percentiles in sat/vB, 92 days of history.

1,105 rows · 7 columns · CSV · JSON

BTCVC Withdrawal Markup Index

Exchange withdrawal fees expressed as a multiple of real on-chain transfer cost, across every tracked chain and exchange.

7 rows · 7 columns · CSV · JSON

Cross-exchange withdrawal halt log

Every observed change in per-coin deposit and withdrawal availability. 8,113 pairs watched continuously.

1,252 rows · 9 columns · CSV · JSON

Feed

Withdrawal status changes are published as RSS. A halt or a reopening appears there within minutes of being confirmed.

Using it as an API

The JSON files are the API. No key, no signup, no rate limit — they are static files behind a CDN-shaped cache, so hammering them is pointless rather than forbidden. Each carries its own updated timestamp and licence.

curl -s https://btcvc.com/data/withdrawal-markup-index.json | jq '.rows[0]' # every pair where an exchange charges more than 50x network cost curl -s https://btcvc.com/data/withdrawal-markup-index.json \ | jq '.rows[] | select(.markup_multiple | tonumber > 50)'

The RSS feed is the push equivalent: subscribe once and status changes arrive without polling. That is the intended route for anyone monitoring rather than researching.

How to cite

If you use these numbers, this is the form that helps:

Data: BTC Value Check (btcvc.com), retrieved 2026-09-15. https://btcvc.com/data/

Why these exist

Exchanges and block explorers publish the current state and keep no history. These files are the history — they only exist because something has been recording them since the day we started, and they cannot be reconstructed after the fact. That is also why they are free: a dataset nobody can use is a dataset nobody cites.

Figures are collected from public endpoints and are provided as-is. Confirm anything consequential against the source before relying on it.