SNARKs vs STARKs: Zcash, Mina, Dusk, Manta, Starknet and zkSync
Thread815 words284 likes
Long explainer on SNARKs and STARKs: Zcash pioneered SNARKs, Mina uses them for a 22kb chain, Dusk and Manta apply them for privacy, zkSync for scaling. STARKs, used by Starknet, avoid trusted setup but carry compute overhead.
Key claims
Mina keeps a constant proof size of about 22kb
STARKs need no trusted setup, but have higher computational overhead
zkSNARKs need a CRS from a trusted setup ceremony
0/ What are SNARKs and STARKs? 🧙♂️✨
feat. $ZEC, $MINA, $DUSK, $MANTA, #Starknet, @zkSync
(0/26) 🧵👇
1/ #SNARKs (Succinct Non-interactive ARguments of Knowledge) and #STARKs (Scalable Transparent ARguments of Knowledge) are both forms of zero-knowledge proofs, a method of verifying the validity of a statement without revealing any information about the statement itself
2/ Zero-knowledge proofs have gained significant attention in the realm of cryptography and blockchain technology due to their ability to provide privacy and security for users
3/ In crypto we especially care about what is referred to as non-interactive zero knowledge proofs (NIZKPs)
I have already posted a short thread on those, in case your new to ZKPs 👇
x.com/expctchaos/status/1607813588370227200
4/ But back to #SNARKs and #STARKs
zkSNARKs are the most well-known form of zero-knowledge proofs and were first introduced by the @zcash protocol in 2012
5/ These #zkSNARK proofs allow the @zcash network to verify transactions without compromising user privacy, as even the nodes enforcing consensus rules do not need to know the underlying data of each transaction, improving both user anonymity & tx confidentiality in the network
6/ However, as outlined in the thread on #NIZKPs above, #zkSNARK systems need a common reference string (CRS) to be generated within a trusted setup ceremony
7/ The trusted setup ceremony involves generating a CRS that consists of cryptographic parameters used to generate the NIZKPs used in the system and it can be difficult to find the the balance between security, efficiency and the size of the CRS
8/ In recent years, zkSNARK technology has been adopted by several projects such as:
9/ @MinaProtocol is a decentralized network that utilizes cryptographic proofs instead of a traditional blockchain. These proof is easily verifiable and consistently sized, leading to a significant reduction in the amount of data that each user must download.
10/ Sounds familiar? You're right.
Instead of requiring participants to verify the entire blockchain from the beginning of time, $MINA uses zk-SNARKs to fully verify the network & transactions
11/ As a result, nodes are able to store the small proof rather than the entire chain, allowing for greater scalability and accessibility (e.g. for running nodes / verifying chain)
12/ The consistent size of the proof (22kb) also ensures that @MinaProtocol remains accessible even as it accommodates a growing number of users and accumulates a large volume of transaction data
13/ $MINA offers a number of powerful features, including zero knowledge-powered smart contracts (zkApps). These smart contracts are Turing complete, meaning they have the ability to execute any computation that can be performed by a classical computer.
14/ Additionally, the native zero knowledge capability of these contracts allows for enhanced privacy and off-chain computation capabilities
15/ One powerful aspect of $MINA #zkApps is the ability to develop them using the Typescript-based SnarkyJS library. This increases the accessibility to a wider pool of developers, as it eliminates the requirement to learn a new programming language in order to start building
16/ Another exciting example of an L1 using zkSNARKs for privacy & compression is @DuskFoundation, which I already covered in the thread linked below 👇
$DUSK
x.com/expctchaos/status/1486103606201921551
17/ Looking at the #Ethereum ecosystem, a pioneer in leveraging the compression power of zkSNARKs to scale $ETH is the rollup @zksync
find out more in the thread below 👇
x.com/expctchaos/status/1570412185112940551
18/ Finally, @MantaNetwork is definitely also worth mentioning. An app-specific $DOT parachain built on substrate and powered by zkSNARKs that aims becoming the privacy hub of the #Polkadot ecosystem and enabling privacy for all #parachain assets
more 👇
x.com/expctchaos/status/1486383616447889409
19/ A thread on #zkEVM rollups is linked below 👇
x.com/expctchaos/status/1569717615282782209
20/ But now we've covered SNARKs, wtf are STARKs?
#STARK proofs are another form of zero-knowledge proofs. They were pioneered by @StarkWareLtd and are for example used by the zk-rollup #Starknet
21/ A #Starknet deep-dive can be found here 👇
x.com/expctchaos/status/1570774568599687175
22/ What makes #STARK proofs interesting you ask?
Well, STARKs offer a number of benefits, the main one being the elimination of the need for a trusted setup
23/ However, both SNARKs & STARKs come with some limitations & trade-offs. While the former require a trusted setup, it is primarily the computational overhead required to generate & verify proofs that can limit the use of STARKs
24/ But despite these challenges, zero-knowledge proofs like #SNARKs and #STARKs will likely play a critical role in securing blockchain systems and keeping data private
25/ I'm convinced #zk will be the next bullrun narrative and next week I will cover a number of zk projects in more depth, including @RAILGUN_Project that has been requested multiple times
any other wishes? 👀
26/ In any case, stay tuned for more on privacy-preserving technologies that will shape the future of crypto! 🧙♂️✨
If you liked this thread, please support by retweeting the first tweet (linked below) 🙏
x.com/expctchaos/status/1611398681890283521
27/ added a few clarifications on the need for trusted setups ✨👇
x.com/expctchaos/status/1611718176202715139