Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [IPv6:2605:bc80:3010::137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 3892BC002C for ; Sat, 9 Apr 2022 21:41:09 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 1463041BD0 for ; Sat, 9 Apr 2022 21:41:09 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: smtp4.osuosl.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eLiqBiWK-D1C for ; Sat, 9 Apr 2022 21:41:07 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) by smtp4.osuosl.org (Postfix) with ESMTPS id 8607A41BA9 for ; Sat, 9 Apr 2022 21:41:07 +0000 (UTC) Received: by mail-lf1-x12b.google.com with SMTP id bu29so20609457lfb.0 for ; Sat, 09 Apr 2022 14:41:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j0yK0wnOcQkH49h7HYrYuCIM0ptjVu+CNA3d+s5AOAw=; b=HF26fv0nkrsBywBQBIn3Cgby36JDvVCOEvJEP7Bt5UoEw41EHublzG/PMYYr9qkXkS 3M5rXg7mCyskLtNMSBxvGAUVNPwd2O0vOovONHBIF/CB35QzlYosknPj39CgbVrzZHAd poNW/E8uTajjMf8XOqBZ42uCX51R63kTdgQJef5HNjFzC8/9DLx4cgkN8EA6zhEkvAEt 9nv+xRVEQjrkrI2DyM7fsElK8J+7aLpfJcbYMCrABVTInDowE2dq4Aokbfl46Gm+RZpQ NwH5yPvyfoAR1Z3jkH839f/2n4/yEp0F3DIqHe/Y+6txde1PnNr5L4MBjYL6gC35Z4Lk BfPA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=j0yK0wnOcQkH49h7HYrYuCIM0ptjVu+CNA3d+s5AOAw=; b=zyhXgVKrhmatrnd41jUUh1eH098RyoAeKFVUeKqa7HqQwVL7vzVOWcZ5JJDzL5Fu6o zeivxcDXpW/lar7j5jgkaZaoZN2VIQ2U/7Zk7yKGAfX+Umt6ZLwJuH0XlcjBciOAlFEI yDreYtDDhzCBdXGbqSEMy0nBAdwrMm2Xj1TlrvZ28ytfueJWMilKffcusz7tCZ+3RvPB rchKkm41xJqzwHpPwREhwMft/fNR1eKpxSoxPjbfx5q4x7/e7AfYPZA8sluvoFQYM19Y Vp/dLTqF7T7jqr5/NRMUu/kK3ObX8DcRhMP2ny5B4Jxrge5kK4ldtxr2kvNEkKxi606U I68Q== X-Gm-Message-State: AOAM531uCmS9AuY+NfMUcb/5nsZWrGUy6pdjr6BH9k6HUr3gLqcIqCIC imjiFMI4UWmOxjP4TGASBZu1zXmzTMqqXfSAaS8= X-Google-Smtp-Source: ABdhPJwOppqOm3jTlZIBWO8sHco4A1zXS4uylwDDYTTwXtdqaheN9N/53+U+PUiPMz6OZsIzEVxwMIKBwiNYKEN1nrQ= X-Received: by 2002:a19:5e07:0:b0:44a:48f8:b495 with SMTP id s7-20020a195e07000000b0044a48f8b495mr17222688lfb.512.1649540465038; Sat, 09 Apr 2022 14:41:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Lloyd Fournier Date: Sun, 10 Apr 2022 07:40:38 +1000 Message-ID: To: Christopher Allen , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000761b2105dc3f9143" X-Mailman-Approved-At: Sat, 09 Apr 2022 21:47:53 +0000 Subject: Re: [bitcoin-dev] Simple step one for quantum X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Apr 2022 21:41:09 -0000 --000000000000761b2105dc3f9143 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 > > >> > =E2=80=94 Christopher Allen _____________________________________________= __ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > --000000000000761b2105dc3f9143 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey all,

A good first step might be to = express this as a research problem on bitcoinproblems.org!=C2=A0I've had in mind creating a problem pag= e on how to design a PQ TR commitment in each key so that if QC were to bec= ome a reality we could softfork to enable that spend (and disable normal ke= y path spends):=C2=A0https://github.com/bitcoin-problems/bitcoin-p= roblems.github.io/issues/4

Becoming the author= /maintainer of this problem is as simple as making a PR to the repo. The pr= oblem doesn't have to be focused on a TR solution but could be a genera= l description of the problem with that and others as a potential solution d= irection.

Cheers,

LL

On Sat, 9 Apr 2022 at 18:39, Christopher Allen via bitcoin-dev <bitcoin-dev@lists.linuxfo= undation.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:=C2=A0



<= div dir=3D"auto">
=E2=80=94 Christopher Allen _______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000761b2105dc3f9143--