The right way to prove you are Satoshi

Step 1. Don’t make basic mathematics mistakes in your blog post, as shown below. How many mistakes can you find in the quote?

Note in Satoshi’s Bitcoin paper he was able to do standard statistics just fine, but fails at the high-school level “process known as combinatorics” in his blog post.

Step 2. Post the file you claim to be signing so others can verify. (It was nowhere to be found on Wright’s blog post)

Step 3. Make your proof interactive. Have someone you don’t know write an open-source program to pull tweets from Twitter at random, and then you sign those messages with your private key in real time. This proves you did not spend the last three years finding a lucky hash collision.

If you were Satoshi, you’d probably know something about zero-knowledge proofs and how, to the contrary of what Wright says, signing lots of messages does provide better proof that it’s your private key.

Step 4. Don’t steal your supposed “proof” from the blockchain (credit jouke). The signature Wright provided is

MEUCIQDBKn1Uly8m0UyzETObUSL4wYdBfd4ejvtoQfVcNCIK4AIgZmMsXNQWHvo6KDd2Tu6euEl13VTC3ihl6XUlhcU+fM4=

which decodes in hexadecimal to

3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce

(see http://tomeko.net/online_tools/base64.php?lang=en to reproduce). And the latter is the input script for the following transaction on the blockchain:

Bitcoin Transaction 828ef3b079f9c23829c56fe86e85b4a69d9e06e5b54ea597eef5fb3ffef509fe

Here is a snapshot of that transaction, which was block 248. Inspect the input script.

Step 5. Don’t do the awkward gymnastics of going (in elementary detail) through the signature verification process.

Step 6. Don’t waste your time courting journalists.