<oembed><type>rich</type><version>1.0</version><title>Cyph3rp9nk wrote</title><author_name>Cyph3rp9nk (npub1ln…arrnt)</author_name><author_url>https://nostr.now/npub1lnms53w04qt742qnhxag5d6awy7nz6055flnmjkr6jg39hm86dlq7arrnt</author_url><provider_name>njump</provider_name><provider_url>https://nostr.now</provider_url><html>The debate that Willy Woo has reignited about quantum computing and taproot is interesting. &#xA;&#xA;While I believe that it will take many years and decades to see quantum computing as we imagine it, I do believe that taproot was a design flaw in every respect.&#xA;&#xA;As I have mentioned many times, there is widespread suspicion that taproot was approved due to pressure from Core members who had stakes in mining pools.&#xA;&#xA;But the truly amusing aspect is that taproot addresses are less secure than segwit addresses, significantly less secure, given that taproot addresses permanently display the public key.&#xA;&#xA;A state attacker, for example, could collect Taproot addresses (and other vulnerable ones such as P2PK and Bare multisig/scripts with direct pubkeys) and decrypt their private key.&#xA;&#xA;In segwit addresses (also P2PKH and P2SH/P2WSH), this is not possible, since the public key is not exposed; it is only possible at the moment of spending, which is when the public key is exposed, i.e., while it is in the mempool waiting to be confirmed.&#xA;&#xA;This reduces the window to minutes and greatly reduces exposure to attack.&#xA;&#xA;The example to follow is that of Signal and SimpleX, which improve their encryption algorithms with every step they take and prepare for quantum computing well in advance.&#xA;&#xA;Meanwhile, Bitcoin is more concerned with allowing spam and shitty protocols like Citrea.&#xA;&#xA;This has less and less of a future.&#xA;&#xA;</html></oembed>