From: "'conduition' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Hash-Based Signatures for Bitcoin's Post-Quantum Future
Date: Sun, 18 Jan 2026 17:12:36 -0800 (PST) [thread overview]
Message-ID: <58e6a5e3-8705-43f5-8187-724b8e3a62den@googlegroups.com> (raw)
In-Reply-To: <34eaa8a5-69c1-4825-8f00-ff6de755ba09@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1930 bytes --]
Hey Jonas,
I've been busy over the holidays but just got around to reading your
delving post on SHRINCS. Big +1 from me, perhaps not in the exact form you
propose - i suspect a more modular approach would make standardization
easier - But in principle this would be awesome to have as an option. It
has pitfalls, but until more size-efficient stateless schemes like SQIsign
mature, stateful HBS schemes are the smallest signatures available. Full
thoughts on delving here
<https://delvingbitcoin.org/t/shrincs-324-byte-stateful-post-quantum-signatures-with-static-backups/2158/7?u=conduition>
regards,
conduition
On Tuesday, December 16, 2025 at 3:30:58 AM UTC-5 Jonas Nick wrote:
> Hi Boris,
>
> Just to add to what Mike said: one of the most interesting questions is
> whether
> MPC considerations should inform parameter selection. As of right now, the
> generic MPC approach seems rather impractical, but that shouldn't
> discourage
> experimentation and further research. It's possible to imagine scenarios
> where
> 85-minute signing is acceptable.
>
> Moreover, stateful signature schemes like SHRINCS [0] only require a few
> hashes
> in the best case, which would make MPC-based N/N multisig significantly
> more
> tractable than with full SPHINCS+. However, since SHRINCS signatures are
> already
> small, the absolute space savings are smaller.
>
> [0]
> https://delvingbitcoin.org/t/shrincs-324-byte-stateful-post-quantum-signatures-with-static-backups/2158
>
> Jonas
>
--
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/58e6a5e3-8705-43f5-8187-724b8e3a62den%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2869 bytes --]
next prev parent reply other threads:[~2026-01-19 1:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 20:28 [bitcoindev] " 'Mikhail Kudinov' via Bitcoin Development Mailing List
2025-12-08 21:50 ` Greg Maxwell
2025-12-09 5:08 ` 'conduition' via Bitcoin Development Mailing List
2025-12-10 0:41 ` Olaoluwa Osuntokun
2025-12-09 8:06 ` [bitcoindev] " Boris Nagaev
2025-12-09 22:48 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2025-12-09 23:06 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2025-12-10 0:01 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2025-12-10 0:14 ` 'conduition' via Bitcoin Development Mailing List
2025-12-10 15:55 ` Jonas Nick
2025-12-10 0:53 ` Olaoluwa Osuntokun
2025-12-16 7:25 ` Jonas Nick
2026-01-19 1:12 ` 'conduition' via Bitcoin Development Mailing List [this message]
2025-12-18 18:45 ` Erik Aronesty
2025-12-19 8:36 ` Jonas Nick
2025-12-20 1:14 ` Erik Aronesty
2025-12-24 15:02 ` david torrealba
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=58e6a5e3-8705-43f5-8187-724b8e3a62den@googlegroups.com \
--to=bitcoindev@googlegroups.com \
--cc=conduition@proton.me \
/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