Skip to content
bitcoinGuide
Log in

Methodology

Methodology

Bitcoin content usually goes wrong by blending rules, measurements and opinions. This is how we keep them apart.

Protocol rule
Fixed by consensus rules. Changes only if nearly everyone runs different software. Example: halving every 210,000 blocks.
Measurement
A value fetched now from a public source, with timestamp and source. Example: block height.
Estimate
Derived from measurements using assumptions. Example: hashrate and fee suggestions.
Projection
A forward calculation with explicit assumptions. Example: estimated halving date at ten minutes per block.
Opinion
Interpretation or trade-off judgement. Always labelled, never presented as fact.
Simulation
A simplified model with fictional data that demonstrates a mechanism. Never real keys or real transactions.

Live data

  • Every external request runs server-side with a timeout and limited retries.
  • Responses are validated against a schema; invalid data is rejected rather than guessed.
  • Values are cached briefly. If a refresh fails, the older value is shown labelled as cached data.
  • If something cannot be fetched, an error state is shown, never an invented number.
  • Providers are interchangeable; adding a source requires no interface change.

Live data providers

  • mempool.space

    https://mempool.space/api

    Capabilities: blocks, mempool, mining, lightning

    Documentation

  • Blockstream Esplora

    https://blockstream.info/api

    Capabilities: blocks, mempool

    Documentation

Sources