{"id":79287,"date":"2025-02-10T07:16:06","date_gmt":"2025-02-10T07:16:06","guid":{"rendered":"https:\/\/www.zeeve.io\/blog\/"},"modified":"2025-02-10T07:39:56","modified_gmt":"2025-02-10T07:39:56","slug":"are-decentralized-zksync-provers-really-better-for-all-elastic-chains","status":"publish","type":"post","link":"https:\/\/www.zeeve.io\/blog\/are-decentralized-zksync-provers-really-better-for-all-elastic-chains","title":{"rendered":"Are Decentralized ZKsync Provers Really Better for All Elastic Chains?"},"content":{"rendered":"
Blockchains<\/a> have evolved faster since 2022, when it became easy to launch modular rollups using popular open-source frameworks. However, the issue of scalability<\/a> and security still lingers, which is why modular, layer-2 solutions like ZKSync Elastic Chains<\/a> were developed to leverage ZK proofs. <\/p>\n\n\n\n As the need increases for ZK chains to become more “elastic” (adapting dynamically to transaction loads and security needs), the underlying ZK proof generation infrastructure, which is called the prover, must evolve too. But what exactly are provers? Are Decentralized ZKsync Provers for Elastic Chains really the best approach? This article breaks down the pros and cons.<\/p>\n\n\n\n A Prover is that component of a ZK chain that actually generates Zero-Knowledge proofs. The Prover aggregates multiple transactions into a batch off-chain and then computes the proof for the batch. This proof mathematically shows all the included transactions within that batch are valid and follow the rules of the blockchain (i.e., correct balance checks, no double spending) with minimal to no reveal of transaction data. <\/p>\n\n\n\n So, provers are like advanced auditors that confirm each exchange or calculation on the blockchain<\/a>. They permit validators<\/a> and clients to affirm the trustworthiness of tasks without seeing the delicate subtleties. This fastens verification as well as reinforces security.<\/p>\n\n\n\n To make sense of this critical component, here is how it assembles with other layers:<\/p>\n\n\n\n Users submit transactions to the rollup network, which are received by the Sequencer.<\/p>\n\n\n\n \u2b07\ufe0f<\/p>\n\n\n\n Sequencer Aggregates and orders transactions from users into batches.<\/p>\n\n\n\n \u2b07\ufe0f<\/p>\n\n\n\n Batched transactions are then received by Off-chain ZKVM of the Rollup for Execution and state transitions computation. <\/p>\n\n\n\n \u2b07\ufe0f<\/p>\n\n\n\n Transaction data\/commitment to the data is posted to a DA layer, if needed.<\/p>\n\n\n\n \u2b07\ufe0f<\/p>\n\n\n\n Prover takes the executed transactions and generates a zero-knowledge proof. <\/p>\n\n\n\n \u2b07\ufe0f<\/p>\n\n\n\n The proof, along with necessary data or commitments, is submitted to the Final Settlement Layer<\/p>\n\n\n\n Throughout this process, a Decentralized ZKsync Provers for Elastic Chains can offer unique advantages by distributing proof generation more broadly rather than leaving it centralized. <\/p>\n\n\n\n Let’s come back to ZKsync<\/a> now.<\/p>\n\n\n\n ZKsync has become well known by emphatically expanding transaction throughput while lowering expenses and the provers assume a vital part in this cycle. Right now, ZKsync and ZK stack<\/a> chains are run in a semi-concentrated way. This means that while the protocol benefits from the proficiency of zero-knowledge proofs<\/a>, the prover model is still controlled by a single entity or a group of entities. In ZKsync’s case, this is \u2018Matter Labs.\u2019<\/p>\n\n\n\n They currently use Boojum Prover which is based on the STARK technology that reduces hardware footprint and cost of ZK proving (also optimized for future decentralization<\/a>). Though Boojum generates STARK proofs, for the final proof submitted to Ethereum, a SNARK proof is used for its succinctness. Recursive proofs here come into play. Recursive means proof of proof. Multiple STARK proofs that are generated from batches are recursively converted into a single proof, which is then converted into SNARK for final verification on Ethereum. <\/p>\n\n\n\n This centralization, while efficient, comes with the following trade-offs:<\/p>\n\n\n\n In light of these issues, many are looking at ways to implement Decentralized ZKsync Provers for Elastic Chains as the next phase in scaling and securing ZK-based networks. After the recent ZK Stack’s prover decentralization effort, Fede Intern, a popular blockchain analyst on X, criticized ZKstack for its previous difficulty of running a prover or delegating the prover to another entity in his tweet<\/a>.<\/p>\n\n\n\n So, what does decentralizing ZKsync provers mean? In essence, <\/strong>Decentralized ZKsync Provers for Elastic Chains involves distributing the proof generation process across a network of independent nodes rather than relying on a single entity or a small group of centralized networks. One way to decentralize is to set up a network where multiple independent nodes are responsible for generating proofs. Each node can work on different parts of the overall computation, and together, they contribute to the final verification process.<\/p>\n\n\n\n Below are the two ways possible in 2025 to decentralize proving for ZKsync Elastic Chains<\/a>. <\/p>\n\n\n\n 1. ZK Stack x Lagrange <\/strong><\/p>\n\n\n\n Recently ZKsync and Lagrange partnered for the first ever decentralized implementation of ZKsync prover. <\/p>\n\n\n\n @zksync<\/a> ecosystem gets the first decentralized prover successfully executed… with @lagrangedev<\/a>!<\/a><\/figure>\n\n\n\n
What Are ZK Provers?<\/h2>\n\n\n\n
How are ZKsync Elastic Chain Provers Managed Right Now?<\/h2>\n\n\n\n
\n
Decentralized ZKsync Provers: What Are the Ways in 2025?<\/h2>\n\n\n\n
Lagrange Prover Network has successfully integrated a decentralized version of\u00a0ZKsync\u2019s ZK stack prover.
And it's a huge deal. Why? It's basically the first case of decentralized\u2026 pic.twitter.com\/dG3KKhoMyJ<\/a><\/p>— Ihor\ud83d\udd25.eth (@0xIhor) January 15, 2025<\/a><\/blockquote>