From: Robin Linus <robin@zerosync•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] ZeroSync: Introducing Validity Proofs to Bitcoin
Date: Fri, 12 May 2023 14:12:03 +0200 [thread overview]
Message-ID: <C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1803 bytes --]
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’s 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.
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.
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
[-- Attachment #2: Type: text/html, Size: 3230 bytes --]
next reply other threads:[~2023-05-12 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 12:12 Robin Linus [this message]
2023-05-12 15:32 ` Weiji Guo
2023-05-12 16:03 ` Robin Linus
2023-06-05 18:47 ` Peter Todd
2023-06-05 18:59 ` Erik Aronesty
2023-08-28 7:49 blk0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C45891F8-2AE4-4D26-B98A-0E983935A83E@zerosync.org \
--to=robin@zerosync$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox