mleku on Nostr: so, this is how taproot works we can reveal the pubkey on receiving because the ...
so, this is how taproot works
we can reveal the pubkey on receiving because the secret is hashed by tweak. so the pubkey is on the hash of the secret, meaning even if you reverse it you have to also reverse the pubkey
so, this is the logic:
hash it at the wallet signature side to generate the secret that is used. you have to do this even if you don't want to use tapscript
so because we hashed it already, you don't have to hash the pubkey. this is theoretically correct in the sense that "the secret is not accessible" but the *spend key* would be revealed by the quantum shor algorithm reversal of the pubkey.
it's complete nonsense. the only proper security against quantum existed from the very beginning of bitcoin. hash the damn pubkey on the spend, the receiver has the pubkey, and they put that to prove they control the address because their pubkey in the spend hashes to the address.
the spend key is still the hashed secret. sure, secret is not compromised, but the spend key is compromised
THAT IS THE WHOLE FUCKING POINT OF HASHING THE PUBKEY TO AN ADDRESS
taproot was an attack on bitcoin that explicitly makes it vulnerable to quantum and large scale attacks. ALREADY if the utxo is worth around a million, so, currently about 10k bitcoin, this is a viable exercise from this level upwards you can break even using even a conventional supercomputer. the quantum computers don't have enough bits to run it but already it's break even to crack a bitcoin utxo worth over 10BTC. ALREADY
so it's not doomerism to say that taproot opens bitcoin up to vulnerabilities. if strategy or other ETF is stupid enough to use taproot, someone can swipe that utxo if it's over 10k bitcoin. ALREADY VIABLE EVEN WITHOUT BIG QBIT MACHINES.
Published at
2026-07-14 03:46:42 UTCEvent JSON
{
"id": "9fbc50691bef2ba73645ef334c9c29a26dc62381a8339ded0d1ec6bca9182ae8",
"pubkey": "4c800257a588a82849d049817c2bdaad984b25a45ad9f6dad66e47d3b47e3b2f",
"created_at": 1784000802,
"kind": 1,
"tags": [
[
"client",
"smesh",
"https://smesh.mleku.dev"
]
],
"content": "so, this is how taproot works\n\nwe can reveal the pubkey on receiving because the secret is hashed by tweak. so the pubkey is on the hash of the secret, meaning even if you reverse it you have to also reverse the pubkey\n\nso, this is the logic:\n\nhash it at the wallet signature side to generate the secret that is used. you have to do this even if you don't want to use tapscript\n\nso because we hashed it already, you don't have to hash the pubkey. this is theoretically correct in the sense that \"the secret is not accessible\" but the *spend key* would be revealed by the quantum shor algorithm reversal of the pubkey. \n\nit's complete nonsense. the only proper security against quantum existed from the very beginning of bitcoin. hash the damn pubkey on the spend, the receiver has the pubkey, and they put that to prove they control the address because their pubkey in the spend hashes to the address.\n\nthe spend key is still the hashed secret. sure, secret is not compromised, but the spend key is compromised\n\nTHAT IS THE WHOLE FUCKING POINT OF HASHING THE PUBKEY TO AN ADDRESS\n\ntaproot was an attack on bitcoin that explicitly makes it vulnerable to quantum and large scale attacks. ALREADY if the utxo is worth around a million, so, currently about 10k bitcoin, this is a viable exercise from this level upwards you can break even using even a conventional supercomputer. the quantum computers don't have enough bits to run it but already it's break even to crack a bitcoin utxo worth over 10BTC. ALREADY\n\nso it's not doomerism to say that taproot opens bitcoin up to vulnerabilities. if strategy or other ETF is stupid enough to use taproot, someone can swipe that utxo if it's over 10k bitcoin. ALREADY VIABLE EVEN WITHOUT BIG QBIT MACHINES.",
"sig": "e8480a43763e052b52149bbb91d83854b7323124aaccccd4792f42277a91f72de4e39725201698dfe1abdeb197b8a6f4ad22ebec895259f549cf2d9cf108b831"
}