Delivery-date: Wed, 28 Aug 2024 08:36:02 -0700
Sender: bitcoindev@googlegroups.com
Date: Wed, 28 Aug 2024 08:33:58 -0700 (PDT)
From: Weiji Guo <weiji.g@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <63186352-b441-4548-b7fa-8ff0d5f6fc97n@googlegroups.com>
In-Reply-To: <8d3084bc-aece-48ba-a08d-01b53392b64dn@googlegroups.com>
References: <93611162-6029-4308-98b5-3c95b30a2ac9n@googlegroups.com>
 <22162f02-9362-4d1c-b0ce-3cf8dd01bd93n@googlegroups.com>
 <8d3084bc-aece-48ba-a08d-01b53392b64dn@googlegroups.com>
Subject: [bitcoindev] Re: OP_ZKP updates
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_560690_1591753725.1724859238505"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_560690_1591753725.1724859238505
Content-Type: multipart/alternative; 
	boundary="----=_Part_560691_649305405.1724859238505"

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

I believe I have found the solution to the open issue mentioned in the=20
earlier email. It is just recursive=20
verification. Instead of publishing each application circuit's verification=
=20
key on-chain, we should have=20
only one circuit that OP_ZKP will verify, which is a recursive verifier.=20

Interested readers are welcome to visit the GitHub org dedicated for=20
OP_ZKP: https://github.com/opzkp

So far I have just put up the high level ideas=20
here: https://github.com/opzkp/tea-horse. There are nothing
else yet. But we will add stuff as we move on.

Regards,
Weiji

On Tuesday, July 23, 2024 at 8:40:08=E2=80=AFAM UTC+8 Weiji Guo wrote:

> 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/63186352-b441-4548-b7fa-8ff0d5f6fc97n%40googlegroups.com.

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

I believe I have found the solution to the open issue mentioned in the earl=
ier email. It is just recursive=C2=A0<div>verification. Instead of publishi=
ng each application circuit's verification key on-chain, we should have=C2=
=A0</div><div>only one circuit that OP_ZKP will verify, which is a recursiv=
e verifier.=C2=A0</div><div><br /></div><div>Interested readers are welcome=
 to visit the GitHub org dedicated for OP_ZKP:=C2=A0https://github.com/opzk=
p</div><div><br /></div><div>So far I have just put up the high level ideas=
 here:=C2=A0https://github.com/opzkp/tea-horse. There are nothing</div><div=
>else yet. But we will add stuff as we move on.</div><div><br /></div><div>=
Regards,</div><div>Weiji<br /><div><br /></div></div><div class=3D"gmail_qu=
ote"><div dir=3D"auto" class=3D"gmail_attr">On Tuesday, July 23, 2024 at 8:=
40:08=E2=80=AFAM UTC+8 Weiji Guo wrote:<br/></div><blockquote class=3D"gmai=
l_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204,=
 204); padding-left: 1ex;">Yes, that&#39;s true. With Dory we will have to =
work on some pairing-friendly curve. Not secp256k1.<div><br><div></div></di=
v><div><div><div dir=3D"auto">On Tuesday, July 23, 2024 at 3:01:59=E2=80=AF=
AM UTC+8 Weikeng Chen wrote:<br></div></div></div><div><div><blockquote sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div><div><div>I need to point out that Dory requires pairing,=
 and therefore it cannot work with secp256k1?</div><div>Please circle back.=
</div></div></div></blockquote></div></div><div><div><blockquote style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex"><div><div dir=3D"auto">On Monday, July 22, 2024 at 9:16:18=E2=80=AFAM=
 UTC-5 Weiji Guo wrote:<br></div></div></blockquote></div></div><div><div><=
blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex"><div><blockquote style=3D"margin:0px 0px 0px 0.8=
ex;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></=
blockquote></div></blockquote></div></div><div><div><blockquote style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div><blockquote style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
<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></blockquo=
te></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/63186352-b441-4548-b7fa-8ff0d5f6fc97n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/63186352-b441-4548-b7fa-8ff0d5f6fc97n%40googlegroups.com</a>.=
<br />

------=_Part_560691_649305405.1724859238505--

------=_Part_560690_1591753725.1724859238505--