Bitcoin Data Sources: Bitview, BRK and Snapshot Verification
BTC On-chain Lab presents data obtained from Bitview. This page separates the upstream data provider, the application’s calculations and background references so you can inspect the provenance of a result.
Source chain
| Layer | Role | Where to inspect |
|---|---|---|
| Bitcoin ledger | Transactions and unspent outputs underlying on-chain analysis. | Source indexing implementation. |
| Bitcoin Research Kit (BRK) | Open-source indexing and analytical tooling used by Bitview. | BRK repository and documentation. |
| Bitview | Hosted source of cohort dates, URPD snapshots and supporting series. | Bitview interface and API. |
| BTC On-chain Lab | Validation, two-snapshot comparison, chart aggregation and presentation. | This application and its methodology. |
Primary links
The dashboard provides links to the exact source snapshots used in a comparison. Their dates and cohort IDs matter more than the browser’s fetch time. Availability and upstream schemas can change; this page does not promise a provider service level or future API compatibility.
Verify a dated observation
First note the selected UTC day and comparison day, then the cohort and price step. Inspect the upstream snapshots through the source controls in the dashboard or the sourceSnapshots links in exported JSON. Confirm the response names the intended day and native bucket scheme.
Sum the raw BTC rows and compare with the supplied total. For a two-date difference, subtract earlier balances from selected balances using matching ranges. If you select percent, use selected-day cohort supply for both dates. A filtered table subtotal is intentionally smaller in scope than a full-source export.
Background references are not extra data feeds
These references explain common terminology. The site does not consume a Glassnode data feed or claim that its definitions, price series and cohorts are identical. In particular, BRK’s 150-day age split must not be silently replaced with another provider’s definition.
Ownership, corrections and limits
pdong maintains BTC On-chain Lab; upstream data and tooling have their own maintainers. Application checks catch malformed or inconsistent responses but do not independently certify source accuracy. Missing observations, price-oracle differences and incomplete snapshots can affect interpretation.
When reporting a discrepancy, preserve the exact URL, source dates and exported inputs so it can be reproduced. Comparing providers requires aligning scope and methodology first. The dashboard and educational pages provide research context, not personal financial advice.