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:35:57 -0700 [thread overview]
Message-ID: <CACrqygA0iftnQgnn_+aXqyf_93E3V+Qa27t27YRPaYRy_Jq0QA@mail.gmail.com> (raw)
In-Reply-To: <CACrqygDSjS0AX0NmHjJz0Uw2bVE0u5EVgYGZYt-=zh59yNuN3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 417 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1782 bytes --]
next prev parent reply other threads:[~2022-04-08 23:36 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 [this message]
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=CACrqygA0iftnQgnn_+aXqyf_93E3V+Qa27t27YRPaYRy_Jq0QA@mail.gmail.com \
--to=christophera@lifewithalacrity$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=erik@q32$(echo .)com \
/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