Cointelegrah CONFIRM Craig Wright is “Legendary” Satoshi

In an article titled “Why Craig Wright Is Not Satoshi Nakamoto” a Cointelegraph article goes in to prove Dr Craig Wright is Satoshi:

https://cointelegraph.com/news/why-craig-wright-is-not-satoshi-nakamoto

“When the community has learned that Craig Wright, an entrepreneur from Australia claims he was Satoshi Nakamoto, the legendary author of Bitcoin’s whitepaper and protocol, people started taking sides on the issue. Many believe the evidence provided by Wright. The claim was made stronger by Gavin Andersen, one of the core Bitcoin developers, who commented:

“I was flown to London to meet Dr. Wright a couple of weeks ago, after an initial email conversation convinced me that there was a very good chance he was the same person I’d communicated with in 2010 and early 2011. After spending time with him I am convinced beyond a reasonable doubt: Craig Wright is Satoshi.”

Today, Cointelegraph has decided to reduce speculation to the minimum and take a look at hard facts. We have thoroughly analyzed the evidence which, as Wright alleges, proves him to be Satoshi, and here are the results of that analysis:

1. Craig took the number 9 block from Bitcoin blockchain, which was mined on January 9, 2009.

2. Then he took its coinbase transaction, i.e. the mining transaction which created 50 new bitcoins and credited it to the adress

12cbQLTFMXRnSzktFkuoG3eHoMeFtpTu3S

The hash of that transaction is

0437cd7f8525ceed2324359c2d0ba26006d92d856a9c20fa0241106ee5a597c9

3. That transaction was sent to the following address:

12cbQLTFMXRnSzktFkuoG3eHoMeFtpTu3Swhich corresponds to the following public key:

0411db93e1dcdb8a016b49840f8c53bc1eb68a382e97b1482ecad7b148a6909a5cb2e0eaddfb84ccf9744464f82e160bfa9b8b64f9d4c03f999b8643f656b412a3

4. Thus we have the public key starting with 0411.. which has to have a specific corresponding private key. The latter should only be known by the owner of that wallet – namely, Satoshi, because it’s one of the very first wallets in the Bitcoin network.

5. Now let’s find any single case of use of that private key. Obviously, that would be any transaction which spends the outputs of the wallet starting with 12cb… Check the output script here.

We can see every transaction which was sent from that wallet here.

6. Among them, Craig has picked a transaction with the following hash –

828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe.

7. In that transaction we can see that out of the 28btc worth of outputs, 10btc was sent to the following address:

1ByLSV2gLRcuqUmfdYcpPQH8Npm8cccsFg.

And 18btc worth of change was returned to the 12cb… wallet

In that transaction, we can see the following signature

3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce01

8. According to the Bitcoin protocol, this signature 3045… is derived from the algorithm specified here.

According to the algorithm, we have to take the transaction , modify it slightly (extracting the transaction body as a result), apply the hashing procedure twice and use the resulting data as an input for the signature algorithm.

9. Thus, the signature 3045… = ECDSA(sha(sha(transaction body))

It’s important to keep in mind that the transaction body is known by everyone, or, rather, it is derived from public data. Roughly, it contains the address to which sender transfers money to.

10. Then Craig follows the algorithm mentioned in stage 8 (except for the last step when the data is signed) applying it to transaction 828ef… The steps are the following:

10.1. Request the raw transaction 828e…