Delivery-date: Mon, 22 Jul 2024 17:40:14 -0700
Sender: bitcoindev@googlegroups.com
Date: Mon, 22 Jul 2024 15:38:24 -0700 (PDT)
From: Weiji Guo <weiji.g@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <8d3084bc-aece-48ba-a08d-01b53392b64dn@googlegroups.com>
In-Reply-To: <22162f02-9362-4d1c-b0ce-3cf8dd01bd93n@googlegroups.com>
References: <93611162-6029-4308-98b5-3c95b30a2ac9n@googlegroups.com>
 <22162f02-9362-4d1c-b0ce-3cf8dd01bd93n@googlegroups.com>
Subject: [bitcoindev] Re: OP_ZKP updates
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_844684_530620285.1721687904434"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_844684_530620285.1721687904434
Content-Type: multipart/alternative; 
	boundary="----=_Part_844685_1200743264.1721687904434"

------=_Part_844685_1200743264.1721687904434
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes, that's true. With Dory we will have to work on some pairing-friendly=
=20
curve. Not secp256k1.

On Tuesday, July 23, 2024 at 3:01:59=E2=80=AFAM UTC+8 Weikeng Chen wrote:

I need to point out that Dory requires pairing, and therefore it cannot=20
work with secp256k1?
Please circle back.
On Monday, July 22, 2024 at 9:16:18=E2=80=AFAM UTC-5 Weiji Guo wrote:

=E2=80=94=E2=80=94=E2=80=94What-ifs=E2=80=94=E2=80=94=E2=80=94

What if the open issue cannot be resolved? We might consider Dory. It is=20

transparent, requires pairing, and has logarithmic proof size but=20
concretely larger=20

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/8d3084bc-aece-48ba-a08d-01b53392b64dn%40googlegroups.com.

------=_Part_844685_1200743264.1721687904434
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes, that's true. With Dory we will have to work on some pairing-friendly c=
urve. Not secp256k1.<div><br /><div><div dir=3D"auto">On Tuesday, July 23, =
2024 at 3:01:59=E2=80=AFAM UTC+8 Weikeng Chen wrote:<br /></div><blockquote=
 style=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 2=
04); padding-left: 1ex;"><div><div><div>I need to point out that Dory requi=
res pairing, and therefore it cannot work with secp256k1?</div><div>Please =
circle back.</div></div></div><div><div dir=3D"auto">On Monday, July 22, 20=
24 at 9:16:18=E2=80=AFAM UTC-5 Weiji Guo wrote:<br /></div><blockquote styl=
e=3D"margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); =
padding-left: 1ex;">


<p>=E2=80=94=E2=80=94=E2=80=94What-ifs=E2=80=94=E2=80=94=E2=80=94<br /></p>
<p>What if the open issue cannot be resolved? We might consider Dory. It is=
=C2=A0<br /></p>
<p>transparent, requires pairing, and has logarithmic proof size but concre=
tely larger=C2=A0</p></blockquote></div></blockquote></div></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/8d3084bc-aece-48ba-a08d-01b53392b64dn%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/8d3084bc-aece-48ba-a08d-01b53392b64dn%40googlegroups.com</a>.=
<br />

------=_Part_844685_1200743264.1721687904434--

------=_Part_844684_530620285.1721687904434--