Replying to @matthew_d_green
Surprisingly, an LLM does better here. Even Hauki does the right thing (though on low, it messes up letting me download it)
Relevant XKCD strikes again, this time for real. A certificate authority actually generated private keys where 4 was part of the key.
"Computers now constitute or will soon constitute adangerous threat to individual privacy "
Some of the first notions of cryptography, privacy , and computers came from someone at .... fucking IBM.
Yes, this the Feistel of Feistel network fame. These guys were not just in it for the math.
(from Steven Levy's Crypto, written in january 2001 when Crypto meant Cryptography)
Replying to @stonecoldpat0
I have. Interesting to look at it now with it being somewhat clear we have too many sensationalist "cryptography broken" claims.
Replying to @nic_carter @cremieuxrecueil
Something is a little surprising with the papers results. We'd expert diversion to be large amounts by corrupt insiders, which seems unlikely to show up as a spike in transaction volume a month later.
And apparently they don't have geolocation data for transactions, they used web traffic by country as a proxy.
Again, I want to emphasize, the socio-political constraints in Bitcoin are not invented by the authors of Shielded Bitcoin, and they are what lead to the complex design and its downsides. It looks like it’s the best you can do under the circumstances if you want to keep Bitcoin as is. It’s impressive in that sense.
I'd say it’s the idea I would have come up with too given these (absurd) constraints, but the truth is I'd have given up and found some folks to make their own blockchain.
Why does adding private payments to Bitcoin seemingly require witness encryption, the cryptographic equivalent of a jetpack? Why is that awesome, impressive, and a bad idea? And how do you make a cryptocurrency like Bitcoin or Zcash private in the first place?
To answer that, we need to cover 1) why Bitcoin is public, 2) how you fix that, 3) the socio-political complications using that solution in Bitcoin, and 4) the cryptographic jetpack workaround.










