public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Murch <murch@murch.one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] BIP Draft Post-Quantum Address Format (bc1z) using ML-DSA-65
Date: Fri, 13 Nov 2026 14:42:35 -0800	[thread overview]
Message-ID: <274e5242-4654-4f7c-b56f-609a3f2ee132@murch.one> (raw)
In-Reply-To: <CADrHc-2AuauYHrrgS6aXmcmJWPcE1pegDHV9HdOoQac9+GCn+w@mail.gmail.com>

Hey Hans,

Thanks for taking it with humor.
In the past couple years, we had at least five PQ-output type proposals 
chucked over the fence into the BIPs repository, and probably at least 
as many that made it to the mailing list or Delving. Please feel free to 
peruse them, if you want to see why they ended up consuming review time 
without going anywhere:

• https://github.com/bitcoin/bips/pull/1830
• https://github.com/bitcoin/bips/pull/1832
• https://github.com/bitcoin/bips/pull/2147
• https://github.com/bitcoin/bips/pull/2176
• https://github.com/bitcoin/bips/pull/2194
• 
https://delvingbitcoin.org/t/new-post-quantum-bitcoin-proposal-using-winternitz-lamport-auth-chains/2525
• 
https://delvingbitcoin.org/t/p2wots-post-quantum-utxo-winternitz-signatures/2530
• …

For contrast, please look at some BIPs that actually proposed new output 
types, e.g., …:

• https://github.com/bitcoin/bips/blob/master/bip-0016.mediawiki
• https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki
• https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki
• https://github.com/bitcoin/bips/blob/master/bip-0360.mediawiki

… and the most mature BIP draft to introduce a PQC signature scheme:

• https://github.com/SHRINCS/shrincs-bip/blob/main/SHRINCS.md

Also interesting might be this discussion on PQC output types:

• https://delvingbitcoin.org/t/pqc-output-type-discussion/2749/40

Anyway, there is lots of work for people that want to dig into PQC for 
Bitcoin, but as you also recognized, it’s not a topic where you’ll start 
sharing your results after a day.

-M


On 2026-11-13 12:29, Hans Stringuer wrote:
> Hey Much,
> 
>    Thanks for the feedback. I see now that I need to do more research, 
> especially on the ongoing discussions. There are too many points I 
> should understand better and thanks for pointing them out, I will put 
> more work there before releasing anything.
>    I already thanked Claude, he helped me a lot. Just for the record I 
> do not believe that I will contribute with any breakthrough.
> 
> Cheers,
> Hans
> 
> Em sex., 13 de nov. de 2026 às 17:19, Murch <murch@murch.one> escreveu:
> 
>     Hello Hans,
> 
>     thank you for chiming in. Please note that discussion, research, and
>     development of PQC solutions for Bitcoin has been on-going for several
>     years. Please kindly catch yourself up on the status quo per the last
>     couple years of mailing list, Delving Bitcoin, in-person events, BIP
>     discussions, etc.
> 
>     On 2026-11-12 09:25, Hans Stringuer wrote:
>       > I'm sharing a draft BIP for a quantum-resistant address format for
>       > Bitcoin, developed as part of the safe-btc project
>       > (https://github.com/Zaenus/btc-safe <https://github.com/Zaenus/
>     btc-safe>).
> 
>     I’m afraid that yet another LLM-generated PQ proposal that you started
>     less than 48h ago is unlikely to be the breakthrough we have been
>     waiting for.
> 
>     Please thank Claude for its hard work.
> 
>     Cheers,
>     Murch
> 
>     -- 
>     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
>     <mailto:bitcoindev%2Bunsubscribe@googlegroups.com>.
>     To view this discussion visit https://groups.google.com/d/msgid/
>     bitcoindev/370af76f-6bcf-435d-bf88-fd4170d18537%40murch.one
>     <https://groups.google.com/d/msgid/bitcoindev/370af76f-6bcf-435d-
>     bf88-fd4170d18537%40murch.one>.
> 
> -- 
> 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 
> <mailto:bitcoindev+unsubscribe@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/ 
> bitcoindev/ 
> CADrHc-2AuauYHrrgS6aXmcmJWPcE1pegDHV9HdOoQac9%2BGCn%2Bw%40mail.gmail.com 
> <https://groups.google.com/d/msgid/bitcoindev/ 
> CADrHc-2AuauYHrrgS6aXmcmJWPcE1pegDHV9HdOoQac9%2BGCn%2Bw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
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/274e5242-4654-4f7c-b56f-609a3f2ee132%40murch.one.


      reply	other threads:[~2026-11-14  4:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 17:25 [bitcoindev] BIP Draft Post-Quantum Address Format (bc1z) using ML-DSA-65 Hans Stringuer
2026-11-13 12:18 ` [bitcoindev] " Hans Stringuer
2026-11-13 15:49 ` [bitcoindev] " Zeeshan Ali Khan
2026-11-13 17:25   ` Hans Stringuer
2026-11-13 20:16 ` Murch
2026-11-13 20:29   ` Hans Stringuer
2026-11-13 22:42     ` Murch [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=274e5242-4654-4f7c-b56f-609a3f2ee132@murch.one \
    --to=murch@murch.one \
    --cc=bitcoindev@googlegroups.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