In my previous post in this series, we went over zkSync and the zkEVM. Let’s go over StarkWare’s ZK rollup solution, which uses STARKs instead of SNARKs.
Last updated Feb 09 2022
All of my articles, threads, etc. will be aggregated here for easy navigation. Feel free to bookmark this page as it will be updated as new content comes out!
(This page has a lot of Twitter embeds and it may take a moment to load everything.)
This is part one of a multi-part series diving deeper into the blockchain applications of zero knowledge proofs. There’s been a lot of hype in this space recently, but not a lot of meaningful technical discussion, so this series of articles will explore the applications under the hood. Let’s get started!
zkSync, developed by Matter Labs, was created in 2018 by Alex Gluchowski. zkSync’s end goal is to create a fully trustless L2 with L1 guarantees, such as reorg protection and fund security. In addition to simply being secure, it is also developing tooling to provide support for zero-knowledge based smart contracts.
Scaling the execution layer via rollups, validiums, and volitions is only one half of a two-part solution. In order for a truly scalable and decentralized blockchain to exist, the data computed and stored on-chain must reside somewhere without high storage or computing requirements. Ten years from now, when significantly more people, institutions, and daily users interact with the blockchain in some way, more efficient state and data storage is required. Separating the monolith requires existing monolithic nodes to fragment into specialized task-specific nodes.
Right now, an Ethereum full node’s size is growing at an average rate of 78% per year.
Trying out a longer form article this time to allow a deeper dive into some areas of blockchain research. There are a lot of articles on zero knowledge proofs, and a lot of research papers on SNARKs or STARKs, but very little bridging the intermediate gap.
If you haven’t read my introduction to zero knowledge proofs Twitter thread, I strongly recommend it before going further, as a lot of this article builds on top of it.