Previous Page
G.

The true position as regards the Bitcoin White Paper

559.

I agree there is no particular secret to the way in which the Bitcoin White Paper was produced. The metadata of the documents shows that it was produced in OpenOffice2.4 (see {G/7/17}). It was not produced in LaTeX.

560.

That was common ground between both parties’ experts: see {Q/5/1}. It was a conclusion based on sound foundations. Stroz Friedberg were able to recreate identical sections of the Bitcoin White Paper using OpenOffice 2.4 {Lynch 1 [120] {I/5/35}}. Even leaving aside the “aesthetic” considerations to which reference was made in cross-examination {Day17/10-14}, Mr Rosendahl was able to identify five specific features of the “innards” of the Bitcoin White Paper PDF which showed that it had been created in OpenOffice2.4 and not in LaTeX:

560.1.

The fonts included in the Bitcoin White Paper as subsets have names comprised of 16-letter string, followed by the character ‘+’ and the name of the font {see the first column of Figure 2.1 at {G/7/12}}. If the PDF had been generated using a TeX engine, the 6-letter designations would have been chosen randomly {Rosendahl1 [47] {G/7/16}}. In the Bitcoin White Paper, they are chosen in a predictable manner (e.g. BAAAAA, CAAAAA etc) {Rosendahl1 [47] {G/7/16}}. That is consistent with how fonts are labelled when converting to PDF within OpenOffice {Rosendahl1 [48] {G/7/16}}.

560.2.

All of the fonts included in the Bitcoin White Paper are TrueType fonts. That does not correspond to the output expected of any TeX engine even when TrueType fonts are used by the document. OpenOffice does, however, embed fonts in that way {Rosendahl1 [49-50] {G/7/17}}.

560.3.

The page content stream of the Bitcoin White Paper involves individual characters being written into the PDF file one-by-one {Rosendahl1 [52-53] {G/7/18} and Figure 2.5 at {G/7/18}}. That is not consistent with the document being created with pdfTeX, in which words are built from printable characters or glue (i.e. spacing to account for kerning inside words) {Rosendahl1 [53-55] {G/7/19} and Figure 2.6 at {G/7/18}}.

560.4.

The trailer of the Bitcoin White Paper contains an element “/DocCheckSum”, which is unique to OpenOffice and is not output by any other PDF producer {Rosendahl1 [60] {G/7/19}}.

560.5.

The header of the Bitcoin White Paper contains binary bytes that correspond to hexadecimal encoding (c3 a4 c3 bc c3 b6 c3 9f) that is only consistent with OpenOffice and software based on it such as libreoffice {Rosendahl1 [62-63] {G/7/22} and Figure 2.12 {G/7/23}}. The coding would be different if a TeX engine had been used {Rosendahl1 [64] and Figure 2.11 {G/7/23}}.

561.

In short, the Bitcoin White Paper was produced by Satoshi Nakamoto in OpenOffice 2.4 and exported as a PDF. In my judgment, Dr Wright’s elaborate attempt to carve an alternative narrative by forging documents in LaTeX mark him as a fraud and his claim in these proceedings as a fraudulent claim.

562.

The documents produced by Dr Wright on 16 February 2024 provided irrefutable evidence of his forgery of the White Paper LaTeX Files ahead of their disclosure to COPA and the Developers.

563.

For completeness, I return to the convoluted submissions made by Counsel for Dr Wright which I set out in [421] above. In light of the above analysis, they can be seen as a forlorn attempt to rescue something from the wreckage of the LaTeX files. I have no hesitation in rejecting all three submissions.

Next page