Feedback-ID: i525146e8:Fastmail
Date: Mon, 5 Jun 2023 18:47:03 +0000
From: Peter Todd <pete@petertodd.org>
To: Robin Linus <robin@zerosync.org>,
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Message-ID: <ZH4tp5U7F658M+hn@petertodd.org>
References: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
 protocol="application/pgp-signature"; boundary="P7y0cSQvWa0lKWHq"
Content-Disposition: inline
In-Reply-To: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org>
Subject: Re: [bitcoin-dev] ZeroSync: Introducing Validity Proofs to Bitcoin
Precedence: list


--P7y0cSQvWa0lKWHq
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, May 12, 2023 at 02:12:03PM +0200, Robin Linus via bitcoin-dev wrote:
> Hi all,
>=20
> Today we are publishing a summary of our research on "ZeroSync: Introduci=
ng Validity Proofs to Bitcoin".
>=20
>=20
> Here's the preface:
>=20
> We introduce ZeroSync, the first-ever proof system addressing Bitcoin=E2=
=80=99s scalability challenges with Succinct Non-Interactive Argument of Kn=
owledge (SNARKs). ZeroSync compresses the entire Bitcoin blockchain into a =
compact proof of validity, enabling instant verification and unlocking vari=
ous innovative applications. We discuss our prototype implementation of a c=
hain state proof, utilizing the Cairo language, Utreexo, and recursive STAR=
Ks. Our work enables diverse applications, including quick bootstrapping of=
 full nodes, trustless light clients, enhanced Lightning Network privacy, a=
nd secure cross-chain bridges. Chain state proofs require no consensus chan=
ges, which is crucial as forks in Bitcoin are challenging to implement and =
achieve consensus for. Despite the existing bottleneck of prover performanc=
e, we present a range of optimization strategies and demonstrate the practi=
cality 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 S=
implicity, zkCoins also enables private and more scalable BTC transactions.=
=20
> The groundbreaking compression capabilities of SNARKs initiated a paradig=
m shift in cryptocurrency design, and ZeroSync is pioneering their applicat=
ion to Bitcoin.
>=20
>=20
> You can find the full paper here: https://zerosync.org/zerosync.pdf <http=
s://zerosync.org/zerosync.pdf>
> Happy to receive any comments and answer any questions the bitcoin dev co=
mmunity may have about the paper!

Two serious issues with this proposal:

1) You're creating an alternative implementation of the Bitcoin protocol. T=
here
is a _long_ history of such implementations failing to implement an exact c=
opy
of the consensus rules, leading to potential forks. Obviously, if only used=
 by
otherwise lite clients, there is less of a risk associated with this. But t=
he
risk is there and will expand as this tech is used for more sophisticated
things.

2) If the tech advances to the point where proof-generation is fast enough =
to
happen in real time, Bitcoin miners adopting it along with and other wideps=
read
adoption it may cause Bitcoin to lose its decentralization. At the heart,
Bitcoin's consensus is a proof of publication scheme: miners are (weakly)
forced to publish blocks by the fact that users and other miners demand blo=
cks
to both validate their coins, and mine further. Without blocks themselves b=
eing
published on a timely basis, the censorship resistance of Bitcoin fails bec=
ause
only a subset of miners actually have the necessary block data to create new
blocks with transactions in them. There's also other scenarios where these
capabilities could be abused, eg with "illegal data" being published in the
chain.

Re: #2, the Bitcoin technical community would be smart to find ways to *def=
eat*
ZKP schemes, with the goal of making it technologically infeasible to use t=
hem
for recently created blocks (eg the last few days worth).

--=20
https://petertodd.org 'peter'[:-1]@petertodd.org

--P7y0cSQvWa0lKWHq
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0RcYcKRzsEwFZ3N5Lly11TVRLzcFAmR+LaQACgkQLly11TVR
LzcnBQ//R301vIatkpLiDu0OCUAr4vr/1OFHL+sWx2YWm8Lw+SCr5BvaTbOix+iB
JeXnWaDYTjPWxXVUhJIFp9cx35Gqe62UBlrRldVPSHMW/khcHZPHqHchDQ7TlCx8
npJbc4iYgky/i0Vft/HSiromP18Ts03bm6NAyEd13GlL0llNJzr7Id47N1d+q6UU
TqcPKpzXOwyuEiBSBU2fDEONcsTKB5e2g/i9ZWoqkI1yO3lexgD/IkwTaABqZM22
0wK6cFgys6i1tHrKyvTlBO3fFku7FhZ4I0yDTdBb031a3e37i+hERhCIFc+xU+gD
pLClikev5cAETVeCpsQoKw/lBJGEWWhjKyq53bCWpCtHojMfKAFqvNDJUDgQz3tr
sFy2FFNUzskhDr/L0am0DtqFvIFac3XrX928AUmzViUlWi0O10ZzjhmUPCU8cjHh
owqnKygIyH6ubBTFaK0muZ68c+g3yQriyVtP65+CAFLzMF1amLLCP2bMsJ+M8WzA
avp67iSR9o+4T4j6CT9HHfj1EL9+vCoz342tgeda1J16hb5hKd5uSStKRGJXwJt4
VZcb8rsfi0vIT3ekouP2Fhrbk1O8K4Dd8950HZ2F2nFBhA1/JUzBFA1MdvUkqZA8
RdV6RB1gVu0oqaHTApPHF+cV5nPWob8oaOvabtbXxABB/ukrjos=
=ztbC
-----END PGP SIGNATURE-----

--P7y0cSQvWa0lKWHq--