From: Christopher Allen <ChristopherA@lifewithalacrity.com>
To: Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>,
Erik Aronesty <erik@q32.com>
Subject: Re: [bitcoin-dev] Simple step one for quantum
Date: Fri, 8 Apr 2022 16:33:24 -0700 [thread overview]
Message-ID: <CACrqygDSjS0AX0NmHjJz0Uw2bVE0u5EVgYGZYt-=zh59yNuN3A@mail.gmail.com> (raw)
In-Reply-To: <CAJowKg+xgenKmyA7gHPmPV0VNF-PdAww2nAxBfS-Z7v5GcpeLA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Fri, Apr 8, 2022 at 2:36 PM Erik Aronesty via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> I'm not saying I endorse any action at all. Personally I think this is
> putting the cart like six and a half miles in front of the horse.
>
I have to agree that practical quantum-attacks are like fusion, human-level
AI, and nanotechnology — always 20 years away. In addition, several
reported approaches to quantum-attack resistance have fallen, and more will
fall in the next “20 years”.
That being said, it is interesting research. Here is the best link about
this particular approach:
https://ntruprime.cr.yp.to/software.html
Blockchain Commons can’t offer to fully fund this research, but if others
do we’d be glad to contribute a small grant.
— Christopher Allen
[-- Attachment #2: Type: text/html, Size: 2631 bytes --]
next prev parent reply other threads:[~2022-04-08 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 21:34 [bitcoin-dev] Simple step one for quantum Erik Aronesty
2022-04-08 23:33 ` Christopher Allen [this message]
2022-04-08 23:35 ` Christopher Allen
2022-04-09 21:40 ` Lloyd Fournier
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='CACrqygDSjS0AX0NmHjJz0Uw2bVE0u5EVgYGZYt-=zh59yNuN3A@mail.gmail.com' \
--to=christophera@lifewithalacrity.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=erik@q32.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