francescomecca.eu/output/categories/wright.xml

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Caught in the Net (Posts about wright)</title><link>francescomecca.eu</link><description></description><atom:link href="francescomecca.eu/categories/wright.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><copyright>Contents © 2019 &lt;a href="mailto:francescomecca.eu"&gt;Francesco Mecca&lt;/a&gt; </copyright><lastBuildDate>Wed, 06 Mar 2019 09:27:55 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>Why Wright's proof is a fake</title><link>francescomecca.eu/blog/2016/5/3/satoshisignature/</link><dc:creator>Francesco Mecca</dc:creator><description>&lt;div&gt;&lt;p&gt;I explained in my previous &lt;a href="http://francescomecca.eu/pescewanda/2016/04/17/wright-nakamoto/"&gt;post&lt;/a&gt; (in italian) that the signature that Wright provided as a public proof is in fact invalid.
I want to explain briefly how you could check this claim.
The key in Wright's &lt;a href="http://www.drcraigwright.net/jean-paul-sartre-signing-significance/"&gt;post&lt;/a&gt; is this:&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;------------------------- Signature File -------------------------
MEUCIQDBKn1Uly8m0UyzETObUSL4wYdBfd4ejvtoQfVcNCIK4AIgZmMsXNQWHvo6KDd2Tu6euEl1
3VTC3ihl6XUlhcU+fM4=
------------------------- End Signature --------------------------
&lt;/pre&gt;


&lt;p&gt;Now we can use some bash utilities:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;base64, that translates encoded ASCII text;&lt;/li&gt;
&lt;li&gt;hexdump, that displays hexadecimal contents from the input;&lt;/li&gt;
&lt;li&gt;cut, used to remove the binary part of the input;&lt;/li&gt;
&lt;li&gt;tr, used to delete spaces and carriage return from the input;&lt;/li&gt;
&lt;/ul&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;base64 -d &amp;lt;&amp;lt;&amp;lt;'MEUCIQDBKn1Uly8m0UyzETObUSL4wYdBfd4ejvtoQfVcNCIK4AIgZmMsXNQWHvo6KDd2Tu6euEl13VTC3ihl6XUlhcU+fM4=' | hexdump -C| cut -b 11-60| tr -d ' \n'

3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce
&lt;/pre&gt;


&lt;p&gt;Let's analyze the command one by one:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;base64 -d&lt;/code&gt; decodes the redirected string, the output is some gibberish characters so I won't display them here;&lt;/li&gt;
&lt;li&gt;&lt;code&gt;hexdump -C&lt;/code&gt; is used with a pipe to convert to hexadecimal:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;00000000  30 45 02 21 00 c1 2a 7d  54 97 2f 26 d1 4c b3 11  |0E.!..*}T./&amp;amp;.L..|
00000010  33 9b 51 22 f8 c1 87 41  7d de 1e 8e fb 68 41 f5  |3.Q"...A}....hA.|
00000020  5c 34 22 0a e0 02 20 66  63 2c 5c d4 16 1e fa 3a  |\4"... fc,\....:|
00000030  28 37 76 4e ee 9e b8 49  75 dd 54 c2 de 28 65 e9  |(7vN...Iu.T..(e.|
00000040  75 25 85 c5 3e 7c ce                              |u%..&amp;gt;|.|
&lt;/pre&gt;


&lt;ul&gt;
&lt;li&gt;cut -b 11-60 displays only the characters from column 11 to 60:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;30 45 02 21 00 c1 2a 7d  54 97 2f 26 d1 4c b3 11  
33 9b 51 22 f8 c1 87 41  7d de 1e 8e fb 68 41 f5  
5c 34 22 0a e0 02 20 66  63 2c 5c d4 16 1e fa 3a  
28 37 76 4e ee 9e b8 49  75 dd 54 c2 de 28 65 e9  
75 25 85 c5 3e 7c ce                            
&lt;/pre&gt;


&lt;ul&gt;
&lt;li&gt;&lt;code&gt;tr -d ' \n'&lt;/code&gt; is used to delete spaces and carriage returns from the output so that is shown in one line and it gives us the final result:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce
&lt;/pre&gt;


&lt;p&gt;If you noticed, there is also another cleartext string at the beginning of Wright's post:&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;$ base64 -d &lt;span class="o"&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/span&gt;&lt;span class="s1"&gt;'IFdyaWdodCwgaXQgaXMgbm90IHRoZSBzYW1lIGFzIGlmIEkgc2lnbiBDcmFpZyBXcmlnaHQsIFNhdG9zaGkuCgo='&lt;/span&gt;
Wright, it is not the same as &lt;span class="k"&gt;if&lt;/span&gt; I sign Craig Wright, Satoshi.
&lt;/pre&gt;


&lt;p&gt;Now let's head to blockchain.info.
Blockchain.info has a little &lt;a href="https://blockchain.info/decode-tx"&gt;utility&lt;/a&gt; to get hexadecimal informations out of a transaction on the blockchain, so let's use it to get the related info about this transaction:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://blockchain.info/tx/828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe"&gt;tx/828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe&lt;/a&gt;
&lt;a href="https://blockchain.info/tx/828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe?format=hex"&gt;tx/828ef3b079f9... in hexadecimal&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;As you can see the entire output of the first bash command, that is&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce
&lt;/pre&gt;


&lt;p&gt;is contained in:&lt;/p&gt;
&lt;pre class="code literal-block"&gt;&lt;span&gt;&lt;/span&gt;"script":"483045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce01"
&lt;/pre&gt;


&lt;p&gt;except for the 48 at the beginning and the 01 at the end.&lt;/p&gt;
&lt;p&gt;That is a signature hash:
this &lt;a href="https://en.bitcoin.it/wiki/List_of_address_prefixes"&gt;page&lt;/a&gt; explains that the 48 is just a decimal prefix given to uncompressed transactions, and the 01 at the end is just a SIGHASH_ALL &lt;a href="https://bitcoin.org/en/glossary/signature-hash"&gt;code&lt;/a&gt; that flags the end of the signature.&lt;/p&gt;
&lt;h3&gt;So, is it a fake?&lt;/h3&gt;
&lt;p&gt;Yes, indeed.
At the end, I ask, why would you choose anything else than the easiest and most conclusive way to prove something?&lt;/p&gt;
&lt;p&gt;&lt;img alt='Wright "signs" the blockchain' src="francescomecca.eu/wp-content/uploads/2016/satosh.jpg"&gt;&lt;/p&gt;&lt;/div&gt;</description><category>Bitcoin</category><category>PesceWanda</category><category>satoshi nakamoto scam</category><category>scam</category><category>wright</category><guid>francescomecca.eu/blog/2016/5/3/satoshisignature/</guid><pubDate>Tue, 03 May 2016 00:00:00 GMT</pubDate></item></channel></rss>