From: Lloyd Fournier <lloyd.fourn@gmail•com>
To: Christopher Allen <ChristopherA@lifewithalacrity•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Simple step one for quantum
Date: Sun, 10 Apr 2022 07:40:38 +1000 [thread overview]
Message-ID: <CAH5Bsr1C1erecK7=dAY0r2QD48iim831uVOw3MJJ+ky-yBF+3w@mail.gmail.com> (raw)
In-Reply-To: <CACrqygA0iftnQgnn_+aXqyf_93E3V+Qa27t27YRPaYRy_Jq0QA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
Hey all,
A good first step might be to express this as a research problem on
bitcoinproblems.org! I've had in mind creating a problem page on how to
design a PQ TR commitment in each key so that if QC were to become a
reality we could softfork to enable that spend (and disable normal key path
spends):
https://github.com/bitcoin-problems/bitcoin-problems.github.io/issues/4
Becoming the author/maintainer of this problem is as simple as making a PR
to the repo. The problem doesn't have to be focused on a TR solution but
could be a general description of the problem with that and others as a
potential solution direction.
Cheers,
LL
On Sat, 9 Apr 2022 at 18:39, Christopher Allen via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>
> On Fri, Apr 8, 2022 at 4:33 PM Christopher Allen <
> ChristopherA@lifewithalacrity•com> wrote:
>
>> That being said, it is interesting research. Here is the best link about
>> this particular approach:
>>
>> https://ntruprime.cr.yp.to/software.html
>>
>
> Also I think this is the original academic paper:
>
> https://eprint.iacr.org/2021/826.pdf
>
> <https://ntruprime.cr.yp.to/software.html>
>>
> — Christopher Allen _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3391 bytes --]
next prev parent reply other threads:[~2022-04-09 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 21:34 Erik Aronesty
2022-04-08 23:33 ` Christopher Allen
2022-04-08 23:35 ` Christopher Allen
2022-04-09 21:40 ` Lloyd Fournier [this message]
2022-04-11 18:07 ` Olaoluwa Osuntokun
2022-04-11 18:17 ` Erik Aronesty
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='CAH5Bsr1C1erecK7=dAY0r2QD48iim831uVOw3MJJ+ky-yBF+3w@mail.gmail.com' \
--to=lloyd.fourn@gmail$(echo .)com \
--cc=ChristopherA@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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