#

p2wpkh

(3 articles)

How To Turn a Nostr Nsec Into a Hardened Non-Taproot Address In Prod

Finally with passphrase salt code! The end of the npub/nsec to p2pkh/p2wpkh derivation series?

on-chain zapslegacy address derivationno taprootp2pkhp2wpkhnsec-to-wifdo it in prodbitcoin address derivationnsec-to-p2pkhnsec-to-p2wpkhpassphrasesaltsaltingHKDF-SHA256Argon2id

Can We Turn a Nostr Public Key Into a Non-Taproot Bitcoin Address In Prod?

Yes, I've been consistently getting the same keypairs using my proposed rule for deterministic legacy address derivation from x-only public keys (npub) & nsec-to-WIF importing in Electrum (no prefix for p2pkh import & prefix "p2wpkh:" for that type)

on-chain zapslegacy address derivationno taprootp2pkhp2wpkhnsec-to-wifnpub-to-p2pkhnpub-to-p2wpkhdo it in prodbitcoin address derivation

Taproot's bigger attack vector than future QC

It's the need to practice OPSEC unique to P2TR (bc1p...) coins prior to QC threat realization. Grok vs my thesis...

bitcointaprootqcquantum computingquantum threatattack vectorattack surfacep2trp2pkhp2wpkhbc1popsecquantumpublic keyspublic key