Skip to content
Satnam SatoshiIn service of humanityFind your place ↗
Menu

Sikh Bitcoin · Advanced · Lesson 7 of 21

Difficulty, hashrate and noisy observations

Separate a protocol target from an inferred network measurement.

About 14 minutes with practice. You only need something to take notes with. No real wallet details or payments are part of this lesson.

Course contents · Lesson 7 of 21
  1. Read the whitepaper as an argument
  2. Hashes and Merkle commitments
  3. UTXOs, change and accounting
  4. Scripts describe spending conditions
  5. Signatures and what they authorize
  6. Block headers and the chain of work
  7. Difficulty, hashrate and noisy observations
  8. Issuance, fees and incentives
  9. Mempools and policy are not consensus
  10. Fee changes: RBF and CPFP
  11. SegWit and transaction weight
  12. Taproot and Schnorr: useful, not magical
  13. HD wallets and derivation paths
  14. PSBT: separate construction from signing
  15. Descriptors make a wallet policy portable
  16. Full nodes, pruning and verification
  17. Reorganizations and lightweight evidence
  18. Lightning channels and HTLCs
  19. Lightning liquidity has direction
  20. Soft forks, proposals and human coordination
  21. Capstone: trace a payment end to end

What you will learn

  • Explain the purpose of difficulty adjustment.
  • Recognize uncertainty in short-term hashrate estimates.

A target controls the search

Proof of work compares a header hash against a target. A more demanding target makes success less likely per attempt. Bitcoin adjusts difficulty at defined intervals based on observed timing under its rules. This mechanism aims to regulate average block production; it does not schedule individual blocks or guarantee that mining revenue remains constant.

Hashrate is not printed in each block

A block proves that a successful candidate was found, not how many unsuccessful attempts preceded it. Network hashrate charts therefore estimate activity from difficulty and observed blocks over a window. Short windows are noisy. A sudden estimated jump does not automatically establish that a particular new mining facility came online.

Match the claim to the measurement

Suppose a newsroom sees several quick blocks and wants a headline declaring a permanent hashrate increase. Ask about the window, estimator, uncertainty and comparison period. Distinguish protocol data from interpretation. A serious technical conversation can support proof of work while acknowledging statistical noise and changing economics. Do not present a point estimate as an exact count of machines or a forecast of future security.

Practice on paper

Two charts use the same chain data but one averages a day and the other a month. Why might their current hashrate estimates differ?

Reveal the worked answer

They use different observation windows. Random block timing affects short windows more strongly, while a longer window smooths recent changes. Neither chart directly counts every unsuccessful hash attempt.

Check your understanding

Choose an answer in your head or on paper, then reveal the explanation. Retry whenever you like. Answers are not submitted or scored; completion marks are your own learning notes.

1. Does difficulty adjustment promise a block at an exact time?

  • Yes
  • No
Reveal answer 1

No. It concerns expected production over time.

2. Does a block reveal the total number of failed attempts?

  • Yes
  • No
Reveal answer 2

No. Hashrate is inferred from observations and assumptions.

Take this with you

Treat estimated hashrate as an estimate with a window.

Your learning, at your pace

Read every lesson freely. Optional progress tracking needs JavaScript and browser storage; it does not require an account or wallet.