summaryrefslogtreecommitdiff
path: root/6f/573dd178becd61c67dfa76aeb36d092dd7423b
blob: 562ba9565f7125e8cb7d9f02fbd870e6711ee265 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
Return-Path: <robin@zerosync.org>
Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137])
 by lists.linuxfoundation.org (Postfix) with ESMTP id 0F505C002A
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 12 May 2023 12:12:08 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by smtp4.osuosl.org (Postfix) with ESMTP id DC73242ADA
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 12 May 2023 12:12:07 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org DC73242ADA
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001] autolearn=ham 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 oLjRMmgtOQDe
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 12 May 2023 12:12:06 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.8.0
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 5DEA542ABF
Received: from www382.your-server.de (www382.your-server.de [78.46.146.228])
 by smtp4.osuosl.org (Postfix) with ESMTPS id 5DEA542ABF
 for <bitcoin-dev@lists.linuxfoundation.org>;
 Fri, 12 May 2023 12:12:06 +0000 (UTC)
Received: from sslproxy06.your-server.de ([78.46.172.3])
 by www382.your-server.de with esmtpsa  (TLS1.3) tls TLS_AES_256_GCM_SHA384
 (Exim 4.94.2) (envelope-from <robin@zerosync.org>)
 id 1pxRcy-000OaR-JC
 for bitcoin-dev@lists.linuxfoundation.org; Fri, 12 May 2023 14:12:04 +0200
Received: from [2001:9e8:8a6a:ff00:8475:18df:e121:ab2e] (helo=smtpclient.apple)
 by sslproxy06.your-server.de with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92)
 (envelope-from <robin@zerosync.org>) id 1pxRcy-000NBz-0U
 for bitcoin-dev@lists.linuxfoundation.org; Fri, 12 May 2023 14:12:04 +0200
From: Robin Linus <robin@zerosync.org>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_ADB9CD6C-5BA7-4B76-A800-1BC87FAD6464"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Message-Id: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org>
Date: Fri, 12 May 2023 14:12:03 +0200
To: bitcoin-dev@lists.linuxfoundation.org
X-Mailer: Apple Mail (2.3654.120.0.1.13)
X-Authenticated-Sender: robin@zerosync.org
X-Virus-Scanned: Clear (ClamAV 0.103.8/26904/Fri May 12 09:24:30 2023)
X-Mailman-Approved-At: Fri, 12 May 2023 13:15:12 +0000
Subject: [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: Fri, 12 May 2023 12:12:08 -0000


--Apple-Mail=_ADB9CD6C-5BA7-4B76-A800-1BC87FAD6464
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

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 Knowledge (SNARKs). ZeroSync compresses the entire Bitcoin =
blockchain into a compact proof of validity, enabling instant =
verification and unlocking various innovative applications. We discuss =
our prototype implementation of a chain 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 implement and =
achieve consensus for. Despite the existing bottleneck of prover =
performance, we present a range of optimization strategies and =
demonstrate the practicality of generating a complete chain state proof.=20=

Finally, we introduce zkCoins, a client-side validation protocol =
combined with zeroknowledge SNARKs, drastically improving privacy and =
throughput of token transactions. In combination with future Bitcoin =
features, such as Simplicity, zkCoins also enables private and more =
scalable BTC transactions.=20
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 =
<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=

--Apple-Mail=_ADB9CD6C-5BA7-4B76-A800-1BC87FAD6464
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0);"><div class=3D"">Hi all,</div><div class=3D""><br =
class=3D""></div><div class=3D"">Today we are publishing&nbsp;<span =
class=3D"">a summary of</span><span class=3D"">&nbsp;our research =
on</span>&nbsp;"ZeroSync: Introducing Validity Proofs to =
Bitcoin".</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div class=3D"">Here's the preface:</div></div><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0);"><i class=3D"">We introduce ZeroSync, the =
first-ever proof system addressing Bitcoin=E2=80=99s scalability =
challenges with Succinct Non-Interactive Argument of Knowledge (SNARKs). =
ZeroSync compresses the entire Bitcoin blockchain into a compact proof =
of validity, enabling instant verification and unlocking various =
innovative applications. We discuss our prototype implementation of a =
chain 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 implement and achieve consensus for. Despite the existing =
bottleneck of prover performance, we present a range of optimization =
strategies and demonstrate the practicality of generating a complete =
chain state proof.&nbsp;</i></div><div class=3D"" style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0);"><i class=3D"">Finally, we introduce =
zkCoins, a client-side validation protocol combined with zeroknowledge =
SNARKs, drastically improving privacy and throughput of token =
transactions. In combination with future Bitcoin features, such as =
Simplicity, zkCoins also enables private and more scalable BTC =
transactions.&nbsp;</i></div><div class=3D"" style=3D"caret-color: =
rgb(0, 0, 0); color: rgb(0, 0, 0);"><i class=3D"">The groundbreaking =
compression capabilities of SNARKs initiated a paradigm shift in =
cryptocurrency design, and ZeroSync is pioneering their application to =
Bitcoin.</i></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0);"><br class=3D""></div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><br =
class=3D""></div><div class=3D"" style=3D"caret-color: rgb(0, 0, 0); =
color: rgb(0, 0, 0);"><div class=3D"">You can find the full paper =
here:&nbsp;<a href=3D"https://zerosync.org/zerosync.pdf" =
class=3D"">https://zerosync.org/zerosync.pdf</a></div></div><div =
class=3D"" style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, =
0);">Happy to receive any comments and answer any questions the bitcoin =
dev community may have about the paper!</div><div class=3D"" =
style=3D"caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><div =
class=3D""><br class=3D""></div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""></div><div class=3D"">Best regards,</div><div =
class=3D"">Robin Linus</div></div></body></html>=

--Apple-Mail=_ADB9CD6C-5BA7-4B76-A800-1BC87FAD6464--