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?
🔫 Alwin 🦌🏴
thebutterzone@iris.to
On-chain zaps via Taproot are burned, please use bc1qn5kua7a4r7xasgnd6mt4k5huv45gcm3rs545u2 L1 only, no L2 or Taproot/dependents, for me! And there should only ever be one fee: <1 sat/byte. Back in the day, I sent/received bitcoin with ZERO TX fees. PGP 750A6640C5E4961B
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)
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...
Optional Compatibility Layer for Legacy Bitcoin Addresses (Non-normative)
Who else wants deterministic legacy address derivation from x-only public keys (npub)? Mostly ChatGPT & me, may have come up with that reference implementation...
