From: "Nikita Karetnikov" <nikita@karetnikov.org>
To: bitcoindev@googlegroups.com
Subject: [bitcoindev] PQC: Lattice-based signatures
Date: Tue, 19 May 2026 21:33:22 +0200 [thread overview]
Message-ID: <ffa56d63-32c6-4fc3-a150-4fe62ac2e00b@app.fastmail.com> (raw)
Dear list,
I hate to contribute to the recent flood of PQC posts, but I think it’s an important issue that’s worth discussing.
In particular, what I usually see is various competing proposals without a clear winner.
So I’d like to bring everyone’s attention to this new post from Blockstream:
https://blog.blockstream.com/schnorr-but-with-vectors-lattice-based-signatures-explained/
This post is interesting because unlike a lot of PQC discussions, it actually includes a comparison table of various approaches, where lattices seem to come out ahead.
This raises a few questions.
Since lattices are not a new topic in cryptography, why has Blockstream focused their efforts on hash-based approaches so far?
Are hashes seen as a more conservative choice?
Given the problems with hashes outlined in the post, are lattices actually the current most likely candidate for a PQC implementation?
If so, should the community effort be focused on lattices instead of other proposals?
Or is the comparison table not telling the whole story?
I’d like to hear your thoughts on the topic.
Thanks,
Nikita
--
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/ffa56d63-32c6-4fc3-a150-4fe62ac2e00b%40app.fastmail.com.
next reply other threads:[~2026-05-20 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 19:33 Nikita Karetnikov [this message]
2026-05-20 3:18 ` [bitcoindev] PQC: Lattice-based signatures 'conduition' via Bitcoin Development Mailing List
2026-05-20 9:56 ` 'Mikhail Kudinov' via Bitcoin Development Mailing List
2026-05-20 10:35 ` Alex
2026-05-20 17:58 ` Isabel Foxen Duke
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=ffa56d63-32c6-4fc3-a150-4fe62ac2e00b@app.fastmail.com \
--to=nikita@karetnikov.org \
--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