Eight references: the map of what the author had read

The whitepaper ends where it began: with a system that needs no trusted party. The conclusion is short and adds one thing worth keeping — nodes are described as voting with their CPU power, expressing acceptance of a block by working to extend it. The idea from section 4 returns as the closing sentence of the design. Then comes the shortest chapter of the document: eight references. For an investigation, this is the richest page in the paper. A bibliography is not decoration. It is a map of what the author had read, in the order he thought it mattered.

  8 references

  timestamping / hash chains ....  3
  proof-of-work as cost .........  2
  money without an issuer .......  1
  probability / applied maths ...  2

  banking, law, politics ........  0

What a bibliography leaves out is evidence of the same kind as what it includes — but weaker, and easy to over-read. An absent citation can mean the author had not read the work, had read it and thought it irrelevant, or considered it too well known to cite. We record the gap and assign it no meaning yet. The shape of the list, however, is worth stating plainly: this is the bibliography of someone solving an engineering problem, not of someone writing a manifesto. Every entry is there to support a mechanism.

Block sources (originals): bitcoin.org/bitcoin.pdf