From: Erik Aronesty <erik@q32.com>
To: Jonas Nick <jonasd.nick@gmail.com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] Re: Hash-Based Signatures for Bitcoin's Post-Quantum Future
Date: Fri, 19 Dec 2025 17:14:05 -0800 [thread overview]
Message-ID: <CAJowKgL-VBTgbacpbPStGMqe6u6Y7wB6fWNiGy28zWfkCODp=A@mail.gmail.com> (raw)
In-Reply-To: <b6df02a0-8d69-4882-a13c-411bc90adfa1@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2019 bytes --]
this scheme has no mitm attack or replay attack because of the use of
covenants to secure each step in the chain
The best part about starting with something like this is that we can have a
safe quantum vault, too useful covenants that are broadly helpful for other
vaulting schemes, while we develop a proper library that is both performant
and efficient for quantum signatures.
secp256k1 has been optimized to the point where timing attacks are
challenging, and I wouldn't want to use some sort of quantum library that
hasn't had that level of optimization.
simple commit reveal schemes use hashes that are well known to be quantum
resistant. I consider that a lot safer at first step forward. especially
because we can take that step sooner than later without too much discussion
over implementation since the underlying covenants have been well studied.
(txhash and ctv)
we can't say that about any signature schemes.
On Fri, Dec 19, 2025, 3:34 AM Jonas Nick <jonasd.nick@gmail.com> wrote:
> This appears to be a variant of a commit-reveal scheme, a design that has
> been
> discussed a few times on this mailing list. Commit-reveal schemes come with
> their own set of trade-offs.
>
> --
> 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/b6df02a0-8d69-4882-a13c-411bc90adfa1%40gmail.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/CAJowKgL-VBTgbacpbPStGMqe6u6Y7wB6fWNiGy28zWfkCODp%3DA%40mail.gmail.com.
[-- Attachment #2: Type: text/html, Size: 3060 bytes --]
next prev parent reply other threads:[~2025-12-20 12:04 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
2025-12-18 18:45 ` Erik Aronesty
2025-12-19 8:36 ` Jonas Nick
2025-12-20 1:14 ` Erik Aronesty [this message]
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='CAJowKgL-VBTgbacpbPStGMqe6u6Y7wB6fWNiGy28zWfkCODp=A@mail.gmail.com' \
--to=erik@q32.com \
--cc=bitcoindev@googlegroups.com \
--cc=jonasd.nick@gmail.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