This is fascinating - I have been quantitatively tracking TikTok trends and Indian songs consistently top the charts on TikTok by view counts. This will displace many Indian TikTok users and either a new platform will spring up, or Indians will get slightly better at using VPNs (just like internet users in China).
They can, the idea is that they can mine more efficiently by storing the scrambled version rather than storing it unscrambled and re-scrambling when they need to generate a mining proof.
You could use hashpipe (https://github.com/jbenet/hashpipe), from Juan Benet (the author of IPFS). It simply checks that the input to the command matches a given hash, so you can do `curl <url> | hashpipe <hash> | sh`, and if the output of the curl command is different than expected it won't be passed in to `sh`.
* The founder is Zooko Wilcox-O'Hearn, creator of Zooko's triangle, the BLAKE2 hash function, Tahoe-LAFS, and former employee at MojoNation (an early attempt at cryptocurrency/P2P filesharing where another employee, Beam Cohen, went on to create Bittorrent). He knows a thing or two about decentralization/P2P.
* This project is NOT a trivial Bitcoin clone with only a new proof-of-work swapped in. The Zero Knowledge Proofs they use to keep transactions private is state of the art crypto. Also their PoW is actually memory-hard (many currencies have used PoW functions which they thought would be memory-hard and ASIC-proof, such as Litecoin with Scrypt, but it turned out not to be the case).
* Their "Founders Reward" is less like a premine and more like startup vested equity (it pays out to them gradually over 4 years to incentive themselves not to pump and dump).
* The team is extremely helpful in the Zcash Slack and are a relief after dealing with the pedantic, difficult Bitcoin developers.
co is similar to watt, but the main difference is that it only works with Promises. It requires that you convert callback functions to return Promises before you can call them, and it does not let you wrap generators with a callback API.
I wrote a module that provides something similar to this using ES6 generators (which are already widely supported), but also supports callbacks in addition to promises. This way, you can make calls to existing APIs without having to wrap them to return Promises.
> maybe Satoshi sold his private keys to this guy to avoid problems in the future?
That's the best theory I've heard so far. That would explain why he chose a weak verification message (the Sartre quote, instead of a message that proves the signature to be recent). The real Satoshi would have chosen a different proof, but Wright doesn't know any better.
The signature in Wright's post is just pulled straight from a transaction on the blockchain. Convert the base64 signature from his post (MEUCIQDBKn1Uly8m0UyzETObUSL4wYdBfd4ejvtoQfVcNCIK4AIgZmMsXNQWHvo6KDd2Tu6euEl13VTC3ihl6XUlhcU+fM4=) to hex (3045022100c12a7d54972f26d14cb311339b5122f8c187417dde1e8efb6841f55c34220ae0022066632c5cd4161efa3a2837764eee9eb84975dd54c2de2865e9752585c53e7cce), and you get the signature found in this transaction input: https://blockchain.info/tx/828ef3b079f9c23829c56fe86e85b4a69...
Note that the base64 string at the top of his post isn't a signature, just a cleartext message: " Wright, it is not the same as if I sign Craig Wright, Satoshi.\n\n".
Now the only question is how he fooled Gavin. I would imagine this story will still get spread around some naive channels for a while, just like the last time Wright tried something like this.
Credit goes to jouke in #bitcoin for figuring it out.
Something still seems off to me, why does he go into such specific detail in verifying the signature? I would have assumed he would just let people figure out the verification themselves. But maybe I'm just skeptical because Satoshi having a public identity takes some of the magic away.
As pointed out by maaku, he never revealed what message the signature is supposed to be signing.
-----------------
My Original Post:
Everyone in this thread is already taking this as the truth. But remember that Wright has not publicly released any cryptographic proof, there is only a claim from BBC that he showed the signature to them and a few magazines.
This strikes me as a little strange since originally Satoshi pretty much only interacted with the community via the bitcoin mailing list. Why did he "reveal" the proof by sending it to some magazines rather than emailing the mailing list?
It really seems like the person who created Bitcoin, a trustless system based on cryptographic proof, wouldn't make everyone take his word on his identity when it could be trivially solved with one email.
It's actually possible to do this without even requiring a 3rd party for escrow. Two parties can perform a "cross-chain atomic swap", where special transactions are created that move both of the funds on both chains at once, requiring zero trust. This of course requires a custom client to create these special transactions.
I've been working on this exact thing for a while: https://github.com/mappum/mercury However, I'm still waiting for the altcoins to adopt BIP65, a Bitcoin patch that adds a new script opcode, which is necessary for cross-chain atomic swaps. Bitcoin recently adopted this change, so the altcoins should follow in the near future.