From: "'conduition' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: 3D <digi3d@protonmail.com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] [BIP Proposal] Hybrid SPHINCS+ / secp256k1 Key Derivation for Quantum-Resistant Paper Wallets
Date: Wed, 27 May 2026 00:51:55 +0000 [thread overview]
Message-ID: <8xzOqkvC9ILirjnikYtVVAW60ZqDGF9RfQi4hZ-g9gM7Ex4onLrDLT132wC2ObA8F1oixXZRGT-uE8DMc7qoVYhh9pCO2ioFT76RzbLoi08=@proton.me> (raw)
In-Reply-To: <bpSypbIuSoDinhE-Y4CrVI5LGHrJ_I79xYUzpYswA5JGkbASwibq94UozeR2jsu48vH6FZLdEBPpWHgIuVtSpUNy-tRpnGfe1hce2ti8k5w=@protonmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 3636 bytes --]
> 3’s Company HE-SD (High-Entropy Seed Distillation) algorithm
Never heard of that. Google shows no results. Doesn't seem to exist.
> (which uses SPX-QEC for cleanup)
Cleanup of what? What is SPX-QEC? Your draft doc links to this word-salad repo. I can't make sense of how this is related.
> This is intended as a practical bridge for quantum-hardened cold storage/paper wallets while post-quantum consensus migration is still in the future.
What does this even mean? There is no way to "quantum harden" a secp256k1 keypair with different entropy, despite what some snake-oil salesmen are saying. A curve point is a curve point and Shor's algorithm can factor it to find its discrete log just as well as any other point.
Mods, this appears to be an underinformed proposal at best, AI slop/spam, or even phishing at worst.
Needless to say but I'll say it anyway: Don't use this tool to generate paper wallet keys. The keygen code is unreadable gibberish to my eye. Output entropy could be compromised in a way that only the author knows, designed to steal any money deposited into the output keys. Don't click on links to websites you don't already know & trust.
DigiMancer3D, if this is not the case, please explain your proposal better and document your code.
regards,
conduition
On Tuesday, May 26th, 2026 at 6:19 PM, '3D' via Bitcoin Development Mailing List <bitcoindev@googlegroups.com> wrote:
> Hi all,
> I'd like to propose a new wallet-layer BIP for a practical hybrid post-quantum key derivation scheme.
>
> **Title:** Hybrid SPHINCS+ / secp256k1 Key Derivation for Quantum-Resistant Bitcoin Wallets
>
> **Summary:**
> This BIP defines a simple, immediately usable method that combines NIST-standardized SLH-DSA (SPHINCS+) with the 3’s Company HE-SD (High-Entropy Seed Distillation) algorithm (which uses SPX-QEC for cleanup) to derive ordinary secp256k1 private keys and standard Bitcoin addresses (legacy + BIP-341 Taproot).
>
> The process is fully offline, runs on low-end/air-gapped hardware (Raspberry Pi class), and produces keys that work today with Electrum, bitaddress.org, and Bitcoin Core; no consensus changes required.
>
> **Reference implementation & full code:**
> https://github.com/DigiMancer3D/bip-xxx-sphincs-hybrid
>
> **Draft BIP text:**
> https://github.com/DigiMancer3D/bip-xxx-sphincs-hybrid/blob/main/bip-xxx.mediawiki
>
> This is intended as a practical bridge for quantum-hardened cold storage/paper wallets while post-quantum consensus migration is still in the future.
>
> Happy to answer questions, incorporate feedback, and make any changes needed.
>
> Thanks,
> DigiMancer3D
>
> --
> You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
> To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/bpSypbIuSoDinhE-Y4CrVI5LGHrJ_I79xYUzpYswA5JGkbASwibq94UozeR2jsu48vH6FZLdEBPpWHgIuVtSpUNy-tRpnGfe1hce2ti8k5w%3D%40protonmail.com.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/8xzOqkvC9ILirjnikYtVVAW60ZqDGF9RfQi4hZ-g9gM7Ex4onLrDLT132wC2ObA8F1oixXZRGT-uE8DMc7qoVYhh9pCO2ioFT76RzbLoi08%3D%40proton.me.
[-- Attachment #1.1.2.1: Type: text/html, Size: 8843 bytes --]
[-- Attachment #1.2: publickey - conduition@proton.me - 0x474891AD.asc --]
[-- Type: application/pgp-keys, Size: 649 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 343 bytes --]
prev parent reply other threads:[~2026-05-27 0:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 0:17 [bitcoindev] [BIP Proposal] Hybrid SPHINCS+ / secp256k1 Key Derivation for Quantum-Resistant Paper Wallets '3D' via Bitcoin Development Mailing List
2026-05-27 0:51 ` 'conduition' via Bitcoin Development Mailing List [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8xzOqkvC9ILirjnikYtVVAW60ZqDGF9RfQi4hZ-g9gM7Ex4onLrDLT132wC2ObA8F1oixXZRGT-uE8DMc7qoVYhh9pCO2ioFT76RzbLoi08=@proton.me' \
--to=bitcoindev@googlegroups.com \
--cc=conduition@proton.me \
--cc=digi3d@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox