Bitcoin Vision methodology

How to read a daily Bitcoin price chart

Bitcoin Vision compares dated scenarios with BTC price observations recorded after their stated cutoff. Qblock’s stored series is one daily USD sample, not an OHLC candle or a verified exchange close. This guide explains what the rows represent and the limits of a fair historical replay.

Reviewed 2026-10-01 against the current Qblock data path and linked source documentation.

One date, one stored price

Qblock’s BTC archive stores one date and numeric price per row. The updater requests USD history from CoinGecko, converts returned timestamps to UTC calendar dates, and keeps the last returned point for each date in its update window. The row does not retain the original sample timestamp, source, currency, exchange, volume, or intraday path. [CoinGecko: Historical Market Chart API]

A date label is not the same thing as an exchange close or a promise that the sample was taken at 00:00 UTC. Recent dates may be replaced when the updater fetches the overlapping window again. Treat the row as one recorded sample, with the source and collection method stated separately. [CoinGecko: Historical Market Chart API]

A daily sample is not an OHLC candle

An OHLC candle stores four values for a defined interval: open, high, low, and close. A single daily price point cannot show the day’s high or low, the order of intraday moves, or whether a particular trade could have executed at that price. Qblock’s daily-history rows also contain no volume field. [CoinGecko: OHLC Chart API]

That distinction matters when describing a wick, a breakout, or a daily close. Those claims require data with the matching resolution and fields; they cannot be recovered from one stored price per date. [CoinGecko: OHLC Chart API]

Dates show coverage, not freshness by themselves

A YYYY-MM-DD label identifies a calendar date, not a time of day; Qblock assigns the date in UTC from the source timestamp. The stored date does not record when the row was fetched. Without a verified refresh timestamp, treat the series as historical archive data rather than a live quote. A missing date is not an observation; do not read the line between neighboring samples as measured values for every intervening moment. [IETF RFC 3339: Date and Time on the Internet]

Replay separates the thesis from later observations

A fair historical replay freezes a scenario at its stated cutoff, then reveals later stored samples as the reader advances. Those observations help compare the original scenario with what was recorded afterward; they were not part of the information available at the frozen date.

A replay is a historical comparison, not proof of causality, repeatable predictive edge, or executable returns. Keep sourced facts, editorial interpretation, scenario assumptions, and observed prices distinct. A scenario is not a personalized recommendation.

Bitcoin historical timeline

Source-reported events are separate from Qblock interpretation; interpretation does not establish price causality.

  1. Bitcoin design paper circulated

    Source-reported event

    An email attributed to Satoshi Nakamoto announced the Bitcoin design paper to the Cryptography mailing list. [Cryptography mailing list: Bitcoin paper announcement, 31 Oct 2008]

    Qblock interpretation

    This is a publication milestone and a record of the proposed design. It is not a market-price observation or evidence of adoption.

  2. Bitcoin genesis block timestamp

    Source-reported event

    Bitcoin Core mainnet parameters encode the genesis block timestamp as 2009-01-03 18:15:05 UTC. [Bitcoin Core: mainnet genesis block parameters]

    Qblock interpretation

    This marks creation of Bitcoin’s mainnet genesis block. Qblock’s stored daily price archive begins later, so a historical comparison must not imply price coverage from genesis.

  3. US spot Bitcoin ETP listing approval

    Source-reported event

    The SEC stated that it approved the listing and trading of a number of spot Bitcoin exchange-traded product shares. [SEC: approval statement for spot Bitcoin ETPs, 10 Jan 2024]

    Qblock interpretation

    This is a US market-structure milestone. The approval notice alone does not explain nearby price moves or establish causality.

  4. In-kind creation and redemption permitted for crypto ETPs

    Source-reported event

    The SEC announced approvals permitting authorized participants to create and redeem crypto ETP shares in kind, including Bitcoin ETPs. [SEC: in-kind creations and redemptions for crypto ETPs, 29 Jul 2025]

    Qblock interpretation

    This changes an ETP operating feature. It does not, by itself, show net Bitcoin buying or selling or predict price direction.

Sources and definitions

Continue exploring