Re: [bitcoin-dev] Simple step one for quantum

2022-04-11 Thread Erik Aronesty via bitcoin-dev
FWICT: Streamlined NTRU Prime (sntrup) has no known patent issues. Should be fine. Regardless, a "double-wrapped bitcoin address of some kind" can be specified, coded up and the relevant module replaced whenever the dust settles. I know Bitcoin doesn't (yet) have fee "weights", but i still

Re: [bitcoin-dev] Simple step one for quantum

2022-04-11 Thread Olaoluwa Osuntokun via bitcoin-dev
The NIST Post-Quantum Cryptography competition [1] results should be published "soon": https://groups.google.com/a/list.nist.gov/g/pqc-forum/c/fvnhyQ25jUg/m/-pYN2nshBgAJ . The last reply on that thread promised results by the end of March, but since that has come and gone, I think it's safe to

Re: [bitcoin-dev] Simple step one for quantum

2022-04-09 Thread Lloyd Fournier via bitcoin-dev
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

Re: [bitcoin-dev] Simple step one for quantum

2022-04-09 Thread Christopher Allen via bitcoin-dev
On Fri, Apr 8, 2022 at 4:33 PM Christopher Allen < christoph...@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:

Re: [bitcoin-dev] Simple step one for quantum

2022-04-09 Thread Christopher Allen via bitcoin-dev
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

[bitcoin-dev] Simple step one for quantum

2022-04-08 Thread Erik Aronesty via bitcoin-dev
First step could be just implementing a similar address type (secp26k1+NTRU) and associated validation as a soft fork https://www.openssh.com/releasenotes.html#9.0 Then people can opt-in to quantum safe addresses Still should work with schnorr and other things It's a lot of work to fold this