Bitcoin Market Data Methodology

The data flow in plain English

Bitcoin.now requests public market observations through CCXT, keeps each venue and quote asset labelled, combines only approved comparable observations, and sends a read-only result to the page. No authenticated account method is used.

The live number, historical chart, and converter do not all represent the same thing. A live reference combines recent venue observations. A chart contains completed historical candles from a named market. A converter applies a reference rate to a user-entered amount.

• Fetch public tickers from approved exchanges.
• Normalize fields such as last, bid, ask, high, low, and change.
• Keep USD, USDT, EUR, and crypto crosses separate.
• Show unavailable when the required evidence is missing.

How the BTC/USD reference is calculated

The headline BTC/USD value uses available public BTC/USD observations from Coinbase Exchange, Kraken, and Bitstamp. These are actual U.S.-dollar markets. Binance BTC/USDT does not enter the dollar reference.

When approved observations are available, Bitcoin.now takes the median of their latest values. The same median approach is used separately for available bid, ask, high, low, and percentage-change fields. Venue components remain visible on the Bitcoin price page so readers can inspect the inputs.

Why USD and USDT stay separate

USD is bank money denominated in U.S. dollars. USDT is a token issued by a private company and designed to track the dollar. The two can trade close together, but they are not the same asset and do not have the same issuer, redemption, banking, or market risks.

Bitcoin.now labels BTC/USDT and altcoin/USDT markets as stablecoin markets. They are useful for broad coverage, but they are never silently shown with a dollar sign as though the user were looking at a direct USD order book. The USD versus USDT guide explains the difference further.

How other crypto markets are selected

Coinbase Exchange is the first source for supported USD altcoin markets. Kraken supplies selected fiat pairs and BTC crosses. Binance provides broad USDT coverage for assets whose active public markets are commonly quoted in that stablecoin.

Each asset page has preferred markets in a set order. The page uses the first available supported observation and keeps its quote asset visible. Coverage does not mean an endorsement, a safety rating, or a claim that every market is equally liquid.

• USD observations are labelled fiat spot.
• USDT observations are labelled stablecoin spot.
• BTC-denominated observations are labelled crypto crosses.

What CCXT does and does not do

CCXT gives the application one consistent way to call different exchange interfaces. Bitcoin.now uses its public ticker and OHLCV methods. The adapter helps normalize access, but the underlying exchange remains responsible for the observation it publishes.

CCXT does not turn separate venues into one universal market. It does not remove venue outages, symbol differences, delayed responses, unusual prints, or rate limits. Bitcoin.now therefore keeps venue names, market symbols, errors, and availability states in its own data model.

Understanding each displayed field

Last is the exchange’s reported latest trade or ticker value. Bid is the highest visible buying price reported by that venue. Ask is the lowest visible selling price. High and low describe the venue’s reported period, often the past 24 hours. Percentage change follows the source ticker’s period and calculation.

None of these fields guarantees a fill. An order can reach deeper levels of the book, and a market can change between the observation and a user checking another service. The venue table is a comparison, not an instruction to use a particular exchange.

Refreshes, caching, and timestamps

Live observations use a short server cache to avoid sending the same request repeatedly and to respect public exchange limits. A production worker warms its cache in the background so a first visitor does not have to wait for several exchanges.

When cached data exists but needs refreshing, the page may receive the prior labelled observation while a refresh runs. Historical ranges use longer caches because an old daily or weekly candle does not need a new network request every few seconds. Response timestamps describe the application observation time, not a promise that every venue updated in the same millisecond.

Historical chart ranges

The 24-hour range uses five-minute Coinbase Exchange BTC/USD candles. Seven days uses hourly Coinbase candles, and 30 days uses six-hour Coinbase candles. The one-year view uses daily Kraken BTC/USD candles, while the five-year view uses weekly Kraken candles.

A candle contains a timestamp, open, high, low, close, and volume when the source provides it. The chart line uses closing observations. The downloadable CSV keeps the market and source fields so a reader can tell that historical venue data is not the same as the live multi-venue reference.

Outages and fallback behavior

A failed venue is isolated so one outage does not automatically erase every other market. The BTC/USD reference still requires at least one approved USD component; its status shows whether coverage is live, partial, warming, or unavailable.

Bitcoin.now does not keep a believable hardcoded market price for outage use. If public evidence is missing, the affected number says unavailable. The educational text stays accessible because a data outage should not turn a useful guide into an error page.

Known limitations

Public endpoints can be delayed, rate-limited, unavailable, or different from an authenticated customer interface. Ticker fields are not standardized perfectly across exchanges. A venue’s latest trade may be small, and its visible bid or ask can change before another request arrives.

The reference excludes spreads, trading tiers, deposit and withdrawal costs, taxes, account access, order size, and jurisdictional restrictions. Long-tail decentralized assets may require contract-address pricing methods that are not the same as centralized order-book observations.

Read-only and reproducible by design

Bitcoin.now has no order endpoint, balance lookup, exchange login, wallet connection, deposit, withdrawal, or custody feature. API and CSV routes are marked as non-indexable data resources rather than search landing pages.

Readers can compare the visible venue components, inspect the timestamp, download historical observations, and read this method before using a number. For a real transaction, check the exact venue and account you intend to use, including its current order book and total costs.