path: root/01/49a754d3f6c266f885295224210d7c4597f3a4

Return-Path: <earonesty@gmail.com>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 82813C0029
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Jun 2023 19:00:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id 5B634416D2
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Jun 2023 19:00:16 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5B634416D2
Authentication-Results: smtp4.osuosl.org;
 dkim=pass (2048-bit key) header.d=q32-com.20221208.gappssmtp.com
 header.i=@q32-com.20221208.gappssmtp.com header.a=rsa-sha256
 header.s=20221208 header.b=cmjcM7py
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001,
 HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001]
 autolearn=no autolearn_force=no
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 P1R5K_qR4dQy
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Jun 2023 19:00:15 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org AFD71416D0
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com
 [IPv6:2a00:1450:4864:20::635])
 by smtp4.osuosl.org (Postfix) with ESMTPS id AFD71416D0
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon,  5 Jun 2023 19:00:14 +0000 (UTC)
Received: by mail-ej1-x635.google.com with SMTP id
 a640c23a62f3a-977d3292be0so50893466b.1
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Mon, 05 Jun 2023 12:00:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=q32-com.20221208.gappssmtp.com; s=20221208; t=1685991613; x=1688583613;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :from:to:cc:subject:date:message-id:reply-to;
 bh=+SmPDQ0ohsDJAuh+R9UGnAd0ubdnoKWC6qqZZkRtUfM=;
 b=cmjcM7pyheVM49Hwr14rcBHq9htdGyOLU5GDuhAxSinx/6bASVxIg0LRgi0cDQJ9eS
 kvq/z3q8SgJYOcnxw+SyitZztPnYMxG9lSh48PROKWCYzPoZ93hWGGWaFOqvpOriNo/S
 J0T4YAUSE1usmkIU1LNGGJ1hcxs4Vb85epDK50JqDbeFYoIuOhNNQWR/+bginztVd1S/
 TgvCDebG22+Qa3upXb28NdjMoZSS52VwI7dYkLD9IY4JFReSpswo54MR+X8ZxMAb/iPR
 ZhvqaOgphugU1AB/3vEW2ahg4bpDlFOIzvISLl+d5SjoPpBHTjccBrQbs3RW3cNUEtXi
 dJLg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1685991613; x=1688583613;
 h=to:subject:message-id:date:from:in-reply-to:references:mime-version
 :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
 bh=+SmPDQ0ohsDJAuh+R9UGnAd0ubdnoKWC6qqZZkRtUfM=;
 b=E+3dx4ExEddoRmJjsCfwfU+sho3i3uzfiv1zBbK93Ot8BeO/p1mnFH8iEAmV3mO5TP
 PsK+Ga0BRJ0LHHmPdT862yDkoxiqWDXS4m8JM4RN46whppj0YfsAW44Q3vsbnDBzSgMi
 R2V7RfQ+ZsCFRGxAcLZvVgO192NR+NjlKdusGhFBGuB0t4jKiQ6AB5eVaR+kOJOlLdMa
 AIu50Eshc8If0En59isTvXkOl1hyYeNHQKabrCtwJj3FChDHHFQ9R0grXZwCMe99Jw8o
 iZ2rvVCSeOrc0Eq0KkNA9BfWlMOqWVX9pqlVqufSnwkqeWdFMGthxa6C8YLJ/88Nbp8K
 RHsQ==
X-Gm-Message-State: AC+VfDzFWqoE6cZA015yNVr9+A5voN1nv48mESa+dUKyTmeLBz5nUmOm
 O/wSJQo/1KHUr5bwA3U0RodrCGKdzHI5XysK5IIvZAYBF3TmtQE=
X-Google-Smtp-Source: ACHHUZ58PndkmEBq6WAG4izRKJ8dt0KWCwiT/CF2TU6WzbZcCW7ZCpvZ75qH13QSR2rCInRM74CC1s+08KRVSVJGp9k=
X-Received: by 2002:a17:906:77c6:b0:977:cc87:62b5 with SMTP id
 m6-20020a17090677c600b00977cc8762b5mr4915704ejn.4.1685991612409; Mon, 05 Jun
 2023 12:00:12 -0700 (PDT)
MIME-Version: 1.0
References: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org>
In-Reply-To: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org>
From: Erik Aronesty <erik@q32.com>
Date: Mon, 5 Jun 2023 14:59:58 -0400
Message-ID: <CAJowKgKurMyvgXuFYoeyvMF3mFMmSEeA7rD4N2WCZwsPPHeAiA@mail.gmail.com>
To: Robin Linus <robin@zerosync.org>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="00000000000026ea8505fd668371"
X-Mailman-Approved-At: Mon, 05 Jun 2023 23:11:38 +0000
Subject: Re: [bitcoin-dev] ZeroSync: Introducing Validity Proofs to Bitcoin
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, 
 <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Jun 2023 19:00:16 -0000

--00000000000026ea8505fd668371
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

"The sender
could store redundant copies of the encrypted transaction data with
multiple trust-
minimized middlemen, for the recipient to download when they come back
online."

sounds like a nostr event sent to a half dozen relays


On Fri, May 12, 2023, 9:15 AM Robin Linus via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> Hi all,
>
> Today we are publishing a summary of our research on "ZeroSync:
> Introducing Validity Proofs to Bitcoin".
>
>
> Here's the preface:
>
> *We introduce ZeroSync, the first-ever proof system addressing Bitcoin=E2=
=80=99s
> scalability challenges with Succinct Non-Interactive Argument of Knowledg=
e
> (SNARKs). ZeroSync compresses the entire Bitcoin blockchain into a compac=
t
> proof of validity, enabling instant verification and unlocking various
> innovative applications. We discuss our prototype implementation of a cha=
in
> state proof, utilizing the Cairo language, Utreexo, and recursive STARKs.
> Our work enables diverse applications, including quick bootstrapping of
> full nodes, trustless light clients, enhanced Lightning Network privacy,
> and secure cross-chain bridges. Chain state proofs require no consensus
> changes, which is crucial as forks in Bitcoin are challenging to implemen=
t
> and achieve consensus for. Despite the existing bottleneck of prover
> performance, we present a range of optimization strategies and demonstrat=
e
> the practicality of generating a complete chain state proof. *
> *Finally, we introduce zkCoins, a client-side validation protocol combine=
d
> with zeroknowledge SNARKs, drastically improving privacy and throughput o=
f
> token transactions. In combination with future Bitcoin features, such as
> Simplicity, zkCoins also enables private and more scalable BTC
> transactions. *
> *The groundbreaking compression capabilities of SNARKs initiated a
> paradigm shift in cryptocurrency design, and ZeroSync is pioneering their
> application to Bitcoin.*
>
>
> You can find the full paper here: https://zerosync.org/zerosync.pdf
> Happy to receive any comments and answer any questions the bitcoin dev
> community may have about the paper!
>
>
>
> Best regards,
> Robin Linus
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--00000000000026ea8505fd668371
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div dir=3D"auto">&quot;The sender</div><div dir=3D"auto"=
>could store redundant copies of the encrypted transaction data with multip=
le trust-</div><div dir=3D"auto">minimized middlemen, for the recipient to =
download when they come back online.&quot;</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">sounds like a nostr event sent to a half dozen relays=C2=
=A0</div><div dir=3D"auto"><br></div></div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Fri, May 12, 2023, 9:15 AM Robin Li=
nus via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation=
.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div style=3D"word-wrap:break-word;line-break:after=
-white-space"><div style=3D"color:rgb(0,0,0)"><div>Hi all,</div><div><br></=
div><div>Today we are publishing=C2=A0<span>a summary of</span><span>=C2=A0=
our research on</span>=C2=A0&quot;ZeroSync: Introducing Validity Proofs to =
Bitcoin&quot;.</div><div><br></div><div><br></div><div>Here&#39;s the prefa=
ce:</div></div><div style=3D"color:rgb(0,0,0)"><br></div><div style=3D"colo=
r:rgb(0,0,0)"><i>We introduce ZeroSync, the first-ever proof system address=
ing Bitcoin=E2=80=99s scalability challenges with Succinct Non-Interactive =
Argument of Knowledge (SNARKs). ZeroSync compresses the entire Bitcoin bloc=
kchain into a compact proof of validity, enabling instant verification and =
unlocking various innovative applications. We discuss our prototype impleme=
ntation of a chain state proof, utilizing the Cairo language, Utreexo, and =
recursive STARKs. Our work enables diverse applications, including quick bo=
otstrapping of full nodes, trustless light clients, enhanced Lightning Netw=
ork privacy, and secure cross-chain bridges. Chain state proofs require no =
consensus changes, which is crucial as forks in Bitcoin are challenging to =
implement and achieve consensus for. Despite the existing bottleneck of pro=
ver performance, we present a range of optimization strategies and demonstr=
ate the practicality of generating a complete chain state proof.=C2=A0</i><=
/div><div style=3D"color:rgb(0,0,0)"><i>Finally, we introduce zkCoins, a cl=
ient-side validation protocol combined with zeroknowledge SNARKs, drastical=
ly improving privacy and throughput of token transactions. In combination w=
ith future Bitcoin features, such as Simplicity, zkCoins also enables priva=
te and more scalable BTC transactions.=C2=A0</i></div><div style=3D"color:r=
gb(0,0,0)"><i>The groundbreaking compression capabilities of SNARKs initiat=
ed a paradigm shift in cryptocurrency design, and ZeroSync is pioneering th=
eir application to Bitcoin.</i></div><div style=3D"color:rgb(0,0,0)"><br></=
div><div style=3D"color:rgb(0,0,0)"><br></div><div style=3D"color:rgb(0,0,0=
)"><div>You can find the full paper here:=C2=A0<a href=3D"https://zerosync.=
org/zerosync.pdf" target=3D"_blank" rel=3D"noreferrer">https://zerosync.org=
/zerosync.pdf</a></div></div><div style=3D"color:rgb(0,0,0)">Happy to recei=
ve any comments and answer any questions the bitcoin dev community may have=
 about the paper!</div><div style=3D"color:rgb(0,0,0)"><div><br></div><div>=
<br></div><div><br></div><div>Best regards,</div><div>Robin Linus</div></di=
v></div>_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank" =
rel=3D"noreferrer">bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer noreferrer" target=3D"_blank">https://lists.linuxfoundati=
on.org/mailman/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--00000000000026ea8505fd668371--