# All about Polygon zkEVM and zkEVM Rollup By [msfew](https://paragraph.com/@msfew) · 2022-09-06 --- The future path of Ethereum is tailored to Rollup, and the most promising solution is zk Rollup, which uses zero-knowledge proof technology. The common perception is that [zk Rollup requires several years of development before it can really get into the production](https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e), due to [the huge development difficulty of building zkEVM](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8). In order for developers to seamlessly port and deploy EVM smart contracts to zk Rollup, development teams need to build and optimize the performance of EVM-compatible zkEVM. Implementing zkEVM has been a priority for the Ethereum Foundation and other zk Rollup teams such as Polygon. In the long term, the implementation of zkEVM will not only address [aspects of the consensus bottleneck in the Ethereum mainnet](https://mp.weixin.qq.com/s/sl3JewEsVNZ7bhSAgd8z1g) such as: * I/O: via statelessness and enshrined zkEVMs * Storage: via statelessness and enshrined zkEVMs * Compute: via enshrined zkEVMs With zkEVM as a core component, it is possible to build a truly perfect universal Rollup network. Polygon has recently brought such an [alpha version of zk Rollup](https://blog.polygon.technology/the-future-is-now-for-ethereum-scaling-introducing-polygon-zkevm) with zkEVM, which compares favorably with solutions such as Scroll, StarkNet, zkSync, Sin7Y, and others. The existence of these zkEVMs is a huge leap forward for Polygon and the Ethereum ecosystem, and means that a new and better Rollup user experience is on the horizon. ![](https://storage.googleapis.com/papyrus_images/b0258c137f3ea9afbeec2f4bffbe39a9969659f8999bcbdbf3b25919e7de3dae.png) 0\. zkEVM --------- a) Intro to zkEVM ----------------- Before we can understand how zkEVM Rollup innovates Ethereum user experience, we need to understand the concept of zkEVM. If you want to learn more about zk, zkVM and zkEVM, feel free to read [our previous research article](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8). The concept of zkEVM can be broken down into two parts: * zk: Zero-knowledge proof technology, which can prove the validity of a batch of tx through a succinct proof, to achieve computational trustworthiness and thus achieve scaling. * EVM: the smart contract execution environment of the Ethereum ecosystem. It is the existence of EVM that makes Ethereum capable of running smart contracts and becoming a global computing network (compared to Bitcoin, which is probably only counted as a calculator), and it also gives rise to the concepts of [EVM compatible, EVM equivalent, EVM superset](https://twitter.com/toghrulmaharram/status/1518270138876891138). Then zkEVM is a zk virtual machine that is EVM-compatible at least at the programming language level. When a smart contract is run in zkEVM, it generates a zk proof, which proves the validity of the running state transition and guarantees that the computation is trustworthy. The verifier only needs to verify the proof (minimal cost) and does not need to re-execute it (significant redundancy). ![](https://storage.googleapis.com/papyrus_images/2ebb0e973e25cea5ac066fdc3146fb675fb502862b4d1114d8a9861b82fc70dd.png) b) Meaning of zkEVM ------------------- ![](https://storage.googleapis.com/papyrus_images/33787577171ad52fdb1305abd838db1a52c432a95a61fe5a97866f254f87b778.png) zkEVM is of great importance at all levels: * For Rollup scaling: zkEVM can generate proofs for tx batch for fast verification on the mainnet, enabling computational trust with the security of the mainnet in a fully trustworthy manner without multiple rounds of complex consensus. * For DApp developers: Developers can use zkEVM to give zk superpowers to any smart contract without learning any zk-related hardcore knowledge or new languages other than Solidity or maybe Vyper. * For zkEVM developers: Instead of writing different circuits for the smart contracts on the network, they can simply maintain zkEVM. * For Layer3 builders: You can try to build Layer3 Verifier in zkEVM, so that Layer3 batch transactions can be proven “off-rollup” and packaged into a single tx on the main network (L3: 1000 tx → L2: 10 tx → L1: 1 tx), enabling App-rollup. * For Ethereum: the existence of multiple zkEVM schemes will eventually become important public goods, helping Ethereum to achieve the next stage of Enshrined zkEVM and zk everything Roadmap. c) zkEVM Solution and their Progress ------------------------------------ The zk Rollup project has been very active lately. StarkNet announced a future token offering, Aztec released a privacy DeFi, zkSync released a countdown to the mainnet launch, Scroll released a Pre-Alpha version of zkEVM, and Polygon open-sourced their source code…… The Ethereum ecosystem is an arms race between zk and zkEVM projects. And as we said in our [previous zkVM vs zkEVM article](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8), zkEVM’s solutions are slightly different and have their own advantages. First, there is a difference in the general direction of the technology, which is basically divided into two directions: ![](https://storage.googleapis.com/papyrus_images/8a552ca79ac6431f02beeb4409b0a850f94c50f3b164ba543e9c76047e5a4c17.png) There are different players in both directions: * Native based: Polygon, AppliedZKP, Scroll, Taiko. Of course the last three are developing in the same repo and can be considered as basically the same solution (if only talking about zkEVM). * Compiler-based: StarkNet, zkSync, OlaVM, etc. This is the track with the most players, but it actually varies a lot from project to project. According to [Vitalik’s classification comparison method](https://vitalik.eth.limo/general/2022/08/04/zkevm.html), they are classified as follows: ![](https://storage.googleapis.com/papyrus_images/bb5089393517bc637e1851eccb95e1aadc44629e41df1e4a60856d21e3253839.png) * Type 1: Fully enshrined zkEVM fully adapted to Ethereum L1. e.g. AppliedZKP. * Type 2: Fully EVM-equivalent zkEVM, with slightly different internal structure. Such as the future Scroll and Hermez. * Type 2.5: EVM-equivalent zkEVMs with only different gas costs (which may lead to minor compatibility differences). e.g. Scroll and Hermez with precompiles for complex operations. * Type 3: zkEVMs that are almost EVM equivalent. e.g. Scroll and Hermez at this stage. * Type 4: EVM-compatible zkEVM at the language level, with different features and developer toolings, and developers cannot write bytecode directly. e.g. zkSync and StarkNet. There are actually a lot of variables in the choice of options. Only a certain amount of focus can be assigned to each aspect, forming it another trilemma: * Performance (zk Prover, verifier, overall overhead, hardware acceleration) * Compatibility (DApp developers, infrastructure, development tools, miners) * Development Difficulty (maintenance difficulty, development progress, system complexity, engineering implementation complexity) The [differences](https://twitter.com/aliatiia_/status/1422655305540902913) between typical solutions are: * StarkNet: implementation of a completely new zkVM (CairoVM), good performance, not too difficult to develop on, but not enough compatibility (requires Warp tranpiler to achieve EVM ability), the best part is that an ecosystem with innovations such as [storage proof](https://twitter.com/henrlihenrli/status/1559173089971146753) and [fractal scaling](https://twitter.com/henrlihenrli/status/1559173135789830144) has been forming. * zkSync: zkEVM at IR level (the LLVM-IR part). Good compatibility (language level), medium performance and development effort, [more flexible](https://twitter.com/cronokirby/status/1550750051873562624). The highlight is the ability to support languages other than Solidity via LLVM after compiler iterations. * Hermez and Scroll: both are considered zkEVM at the Bytecode level (does not means have to be an exact reuse of EVM Bytecode, but the differences of them are subtle). Compatibility is excellent, performance is sacrificed (the original EVM is not zk-friendly, and there are many performance challenges to overcome after “circuitization”). Development is difficult. The best part is that the architecture is secure and most native. 1\. Polygon zkEVM Rollup ------------------------ The core component of Polygon Hermez’s open source zkEVM Rollup network is zkEVM. Its overall technical solution compares favorably with other solutions and is essentially the same as described in our previous article. a) Polygon zkEVM Rollup Architecture ------------------------------------ The overall architecture of the Polygon zkEVM Rollup is as follows: ![](https://storage.googleapis.com/papyrus_images/ee76fc8a0414bdc5f7eef5e8130cd7806c4d8dcc4ed0b7d5df69a003453710f2.png) The core of the architecture is the zkEVM itself. The zkEVM executes the L2 tx, and the off-chain proof network generates a proof of validity for the execution of the tx in the zkEVM, with the final state transition and proof being submitted to the Ethereum mainnet. The key components of Polygon zkEVM Rollup are: PoE consensus algorithm, zkNode, zkProver, Proof Builder for STARK and SNARK, and Rollup cross-chain bridge: * [PoE consensus algorithm](https://ethresear.ch/t/proof-of-efficiency-a-new-consensus-mechanism-for-zkrollups/11988): for security, efficiency, and decentralization enhancement, the PoE algorithm replaces Hermez 1.0’s PoD algorithm. PoE can be combined with PoS to ensure decentralization and efficiency of producing blocks in Polygon zkEVM Rollup. Any miner running a zkNode can become a Sequencer, and any miner running a zkNode and zkProver can become an Aggregator. The gas fee for the miner’s right to produce block will be denominated using $MATIC. ![](https://storage.googleapis.com/papyrus_images/3104c7f822b038156e7d19d807a5b570da8adef297ecc331ead7565d6bf2eb22.png) * zkNode: zkNode is the software that any miner who wants to participate in the Polygon zkEVM Rollup network needs to run. zkNode does tx synchronization, sorting, and verification. Otherwise, if you just want to know the status of the network, rather than participate, you only need to run a read-only node, not a zkNode. * zkProver: zkProver is the software that any miner who wants to participate in the Polygon zkEVM Rollup network as an Aggregator needs to run. As the name implies, zkProver is a prover that generates zk proofs. Essentially, zkEVM is a polynomial representation of state transitions, and zkProver contains a Main SM Executor and several Secondary State Machines to generate proofs for the state transitions. ![](https://storage.googleapis.com/papyrus_images/ba8f0dfa7bdef1ccb98581b6e632215963303452bfb8f47eed41d86e21f84339.png) STARK and SNARK Proof Builder: The two Proof Builders generate proofs for two different types of zero-knowledge proof techniques, STARK and SNARK. STARK (PIL STARK) generates proofs for the polynomial constraints on state transition batches, while SNARK (SnarkJS) generates constant size proofs for the construction of STARK proofs, which can be published on the mainnet at a lower cost. ![](https://storage.googleapis.com/papyrus_images/3de762e8be478ec786ef8e6ab2e308d042e8be6632fd5b2263b99fcf3e20a83c.png) Rollup cross-chain bridge: Polygon zkEVM Rollup is a traditional Burn/Mint cross-chain bridge, but can also be used as a bridge to other L2s. ![](https://storage.googleapis.com/papyrus_images/0339a33c0f76b0276766ac39c551b2cb4f1337956cc3bc7a4897eea10d5b7101.png) b) Polygon zkEVM Rollup Design ------------------------------ The core idea behind Polygon zkEVM Rollup’s design is: * Decentralized (anyone can rebuild the entire Rollup state through DA, without any censorship or centralized control) * No access (anyone can participate in the network, as Sequencer or Aggregator) * Security (Inherits the security of Ethereum, helping to verify Rollup state updates and proofs through the Ethereum network) ![](https://storage.googleapis.com/papyrus_images/74267ef9ee6dc99374c781624096c2031b07efb2b7a78a1a436e5af3c061a4f0.png) * Performance and efficiency (performance improvement through PoE, off-chain computing, UTXO mode settlement of cross-chain bridge contracts, and various cryptographic optimization schemes) c) Polygon zkEVM Rollup Advantages ---------------------------------- There are a number of advantages that really make Polygon’s solution stand out. First, the collaboration between Polygon’s development teams is a natural synergy. Polygon’s zk universe includes Polygon Hermez (the main development team of Polygon zkEVM), Polygon Zero, Polygon Miden, and Polygon Nightfall, as well as many other teams in the modular blockchain fields. Although the three zk teams have slightly different orientations, they are all top teams in the zkVM space and can collaborate and help each other directly on technical solutions and architecture. For example, [Polygon Hermez chose the 64-bit small field STARK proof generation as suggested by Polygon Zero](https://youtu.be/T2fH1NlHnAc?t=516). ![](https://storage.googleapis.com/papyrus_images/165bbd791bea0e4cd1296dc507947d54bf87c23a0bd3fb194e7208c94358debb.png) In addition, the Polygon zkEVM Rollup has a number of innovations in zk technology. For example, the creation of two DSL zkASMs and PIL, which can be used to interpret EVM byte codes and encode polynomial commitments; the combination of STARK and SNARK, which exploits the Scalable of STARK and Succinct of SNARK to make the proofs faster overall while ultimately consuming less space on the mainnet; [optimization](https://twitter.com/Ingo_zk/status/1550121968904507393)\-wise, which uses [the very efficient Goldilocks](https://blog.polygon.technology/introducing-plonky2/) as the base field, parallel computation of the Keccek circuit is implemented, and a Poseidon-hash Merkle tree is used as the data structure for the system’s storage. Both Polygon Hermez and Scroll have made great efforts in their own ways to prove the equivalence of generative decentralization and EVM. To achieve EVM equivalence, it is necessary to write the EVM opcode as a zk circuit, which Polygon interprets via [zkASM and then executes in zkExecutor](https://twitter.com/toghrulmaharram/status/1549863723556282370) ([Geth is essentially also interpretation](https://twitter.com/dlubarov/status/1550491404345950216), while Scroll is directly available [to the Geth client’s Execution Trace generates proofs](https://twitter.com/yezhang1998/status/1549808592936906752)). There is practically no difference in compatibility between the two (runtime’s [terpretation](https://twitter.com/dlubarov/status/1550506366527086594) or [transpilation have no impact on adaptability](https://twitter.com/dlubarov/status/1550491438470668290)), [in contrast](https://twitter.com/toghrulmaharram/status/1550065886064779265), Polygon’s solution is more prover-friendly and efficient in addition EVM compatibility. In contrast, Scroll focuses on fully reusing Geth’s security model, [making it easier to audit](https://twitter.com/aliatiia_/status/1549999427791765504). ![](https://storage.googleapis.com/papyrus_images/65dd96034ee90ed873d31e8901fc375131056203ad3163c2035a0ce51ee9af82.png) I think Polygon Hermez’s zkEVM solution hits the sweet spot between native EVM support and performance. Not only does it avoid the complexity of developing the underlying EVM by interpreting it with zkASM, but it also makes performance less of an issue with zkEVM by innovating and optimizing it from different angles. 2\. zkEVM Rollup’s Strength --------------------------- a) Layer 1 vs Rollup -------------------- Users have been suffering from Layer 1 gas for a long time, and in [our previous MEV study](https://foresightventures.medium.com/foresight-ventures-mev-definition-difference-decrease-33923783c793), the model of an ideal network was discussed. **In an** [**ideal network**](https://twitter.com/0xmisaka/status/1511370037306834954): * **anyone can send transactions (no censorship)** * **no spam** * **very low fees** Also in the context of Crypto and blockchain, the network needs to be decentralized and scalable in performance. This is the trilemma of an ideal blockchain network: * low fees with no spam * decentralized with no permission and no censorship * scalable with general computation The monolithic blockchain of Layer 1 cannot do all these things at the same time, but Rollup achieves the ultimate performance, decentralization, and low fees by centralizing block producing and decentralizing verification. This is also our conclusion in the [Rollup article](https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e). b) Optimistic Rollup vs zk Rollup --------------------------------- In the long term and with realistic theoretical performance limits, zk Rollup is [more scalable than OP Rollup](https://foresightventures.medium.com/foresight-ventures-unified-to-divided-modular-blockchain-and-data-availability-layer-459b35673381), with [stronger security assumptions](https://vitalik.ca/general/2020/08/20/trust.html). ![](https://storage.googleapis.com/papyrus_images/f58a2038f9562bc8987a574863f8ecf9b8c7dc413e445ac552fd5efbcfc9f743.png) Optimistic Rollup has a challenge period that makes it take a long time for a tx to be truly finalized, while zk Rollup’s proofs, once generated and verified, directly finalize the tx. The OP of Rollup is like Layer 1’s PoW and the longest chain principle, and zk is like PoS and its associated consensus. For Layer 1, both PoW and PoS mechanisms are possible, but the performance-oriented Rollup requires a stronger guaranteed (by pledge or cryptography) zk mechanism in the endgame. This is what we concluded in [Modular Blockchain article](https://foresightventures.medium.com/foresight-ventures-unified-to-divided-modular-blockchain-and-data-availability-layer-459b35673381). c) zk Rollup vs zkEVM Rollup ---------------------------- If zk Rollup, then why is Optimistic Rollup the more popular one now? Because currently zk Rollups in production mode do not have general-purpose computational power, such as Loopring, and are only at the stage of single operation like transaction, so developers cannot deploy and deploy smart contracts to Rollup. The emergence of a zkEVM Rollup can foster an ecosystem of smart contracts like the Optimistic Rollup, which is far more flexible than the normal zk Rollup transaction network, and more secure and user-friendly than the Optimistic Rollup. 3\. UX of zkEVM Rollup ---------------------- a) The Right Time, Place and People ----------------------------------- The emergence of zkEVM Rollup is the right time and the right place: * Timing: Layer 1 scaling has hit a bottleneck, and Optimistic Rollup has explored the development path to Rollup. * Place: The security and social consensus provided by Ethereum provided the perfect ground for the establishment of zkEVM Rollup. * People: The EVM ecosystem dominates blockchain development, and numerous zk development teams are contributing to the zkEVM solution. So what exactly is the experience enhancement of zkEVM Rollup for users? First of all, we need to define the users, which I think includes both developers and regular users: b) UX for Developers -------------------- * zkEVM ⇒ No need to learn a new language or even write a new contract to develop a DApp: Solidity is the number one language in the blockchain contract world, with countless resources and great ecosystem, and is the most suitable language for blockchain scenarios, the combination of these two advantages is far better than Move or Rust etc. * Rollup ⇒ Unlock more application scenarios: Using the Ethereum mainnet for applications such as payments or games is not suitable due to performance and cost issues. zkEVM Rollup allows more apps to be implemented as DApps. c) UX of Users -------------- * zk ⇒ Stronger security than PoS networks and faster finality than OP Rollup: Some PoS networks rely on staking for security, but their small capitalization creates weak security guarantees. zk’s cryptography guarantees absolute security through mathematics. OP Rollup’s challenge period prevents a tx from being confirmed for a certain period of time, while zk Rollup’s proof of a tx confirms the tx once it is generated. * EVM ⇒ Exactly the same usage process and infrastructure: Except for the need to switch networks within the wallet and application, all user usage processes will be exactly the same as on the main network, with no additional learning costs, just use the application as before. * Rollup ⇒ OP and zk Rollup both offer L2 instant finality: in terms of user experience, the transaction is executed before the user is even aware of it. So the user does not have to wait for 10 seconds or 10 minutes to send the next transaction. In terms of application usage, users can carry out on-chain activities, high-frequency transactions or on-chain games, etc. in a more hassle-free way. d) UX of Polygon zkEVM Rollup ----------------------------- In the future, the experience of users and developers on zkEVM Rollup will be infinitely similar to that of the main net, and will be even faster and smoother with the advantages of low gas and fast confirmation. ![](https://storage.googleapis.com/papyrus_images/2643e8fe87a0dee6121222f39754ced6c04a4bbc5c58206a7accdc33529b035f.png) In Polygon zkEVM Rollup’s plan, [ETH will always be the gas fee token for Rollup, and MATIC will be the token for staking](https://twitter.com/sandeepnailwal/status/1550009537406574593), which is a very good decision: * Better value capture: Polygon’s experience running PoS networks has led to the conclusion that value capture from staking is better than using tokens directly as gas. * Better experience: ETH as a Rollup token allows L1 users or cross-chain bridge projects to avoid the extra Swap step in the process (most will cross ETH directly). ETH is also more orthodox as a gas. * More significant differentiation: The Polygon zkEVM Rollup will be more distinctly different from the Polygon PoS, and the difference in mechanics does require such a difference to allow users to choose a solution that suits them better. Also, what Polygon brings to zkEVM Rollup is: * A familiar “environment”: Users don’t have to worry about the underlying technical changes, everything will be very similar to Polygon PoS, except that zkEVM Rollup will be faster, safer, and more usable in every way. Developers will also be able to participate in familiar hackathon and enjoy the rich development ecosystem and community that Polygon has built up. 4\. The Future of zkEVM Rollup ------------------------------ For the future of the zkEVM Rollup solution, we will analyze the technical future, and what the end game of the solution will be. a) zkEVM Tech ------------- Vitalik has very deep insights on this topic. Among the four classifications of zkEVM he outlined, there is no real good or bad solution, just different technical trade-offs: closer to the low-level but development progress will be slower, less compatibility but development progress will be faster. In the long run, it is only a matter of time before zkEVM is engineered and optimized. All solutions have their own value. Vitalik also says that these different solutions may slowly transform over time until they find the one that fits their niche. The best future is that we have very many different flavors of zkEVM, so developers can choose the one they like, and the ethereum mainnet can go through their innovations to improve itself. The more innovation is the better the future. b) Rollup Tech -------------- The endgame of Rollup technology will be zkEVM Rollup, while Optimistic Rollup will continue to have its own place, and there will even be a hybrid of zkEVM and Optimistic Rollup (personally, I think one mechanism is sufficient). The zkEVM Rollup is better than the Optimistic Rollup in many ways. But the biggest advantage of Optimistic Rollup is that it is much simpler to build, the difference between Optimism Bedrock and Geth is only 500 lines of code, any engineer who knows Geth can easily build an Optimistic Rollup, or in the future use Optimint on Celestia and other engines, the path of OP Rollup has been fully explored. The zkEVM Rollup is much more complex, has a higher learning curve, and has no real experience or solutions that are fully implemented. c) Tech…is not the most important --------------------------------- We talked a lot about technology, but technology is certainly not the most important thing. The bottlenecks in zkEVM Rollup, Rollup, Ethereum, and even blockchain are never technical bottlenecks in engineering implementation or DA or consensus, but users. As an example from Web2 (thanks Nelson): Apple’s App Store. All developers prefer to publish their apps on the App Store, but the App Store is very unstable and often rejects apps at random. In contrast, Android’s App Market, or Amazon’s App Market is much friendlier. But why do people want to publish to the App Store? Because the App Store has a mature and stable user base! No matter how good the developer experience is on Android or Amazon, developers will still flock to a platform with users. The goal of software development is not elegant APIs, 100% Test Coverage, and the best programming language, but: solving more problems and providing more value. That means more users. d) End Game ----------- So what do we imagine a true endgame zkEVM Rollup would look like? 1. The foundation of the endgame: technology * zkEVM level: All solutions are good as long as they can be implemented, but they don’t have to be too fundamentalist. Ethereum EVM is a “legacy and obsolete” system (still a top solution, of course), although it is possible to improve and innovate more on zkEVM. Besides zkEVM needs more optimization, reducing [proving overhead](https://twitter.com/sgoldfed/status/1551607983167229954) to catch up with the Optimistic solution. * Rollup level: Ensure that the core values of the blockchain (decentralization, security) are prioritized, instead of an arms race for TPS. 2\. The core of the endgame: Social Consensus * Ecosystem level: Ideally, all applications on the Ethereum mainnet should be migrated to a Rollup. If the zkEVM Rollup itself has a good ecosystem-wise foundation, it will be very much ahead of other solutions in terms of startup. In this respect, Polygon has a huge advantage. * Developer level: EVM compatibility is not the deciding factor. It’s which zkEVM Rollup can reach the fastest developers and get them to use it as a network for development. It is never about the network conforming to the developer, but rather about the developer picking the fastest or best network overall, and then slowly adapting to that network’s development. * User Level: The mindset and social consensus of users is very important. In addition to the Reach developers, the most important factor is who is the first and most effective Reach to the users. A successful network should not become a technical geek’s ego about the superiority of a technical solution, but a real solution that creates value for users. All those zkEVM Rollups have bright future. Related Links ------------- [https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e](https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e) [https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8) [ 以太坊基金会研究团队第八次 AMA 之扩容专题 ----------------------- 本次 AMA 中开发者们回答了许多关于扩容的研发进展以及遇到的难题。 https://mp.weixin.qq.com ![](https://storage.googleapis.com/papyrus_images/115ad2eeaccb91bd7497ce79ffd5ac450c8214e7fe611ef3076cfe38748ebb94.jpg) ](https://mp.weixin.qq.com/s/sl3JewEsVNZ7bhSAgd8z1g) [ Polygon Blog | Announcements, updates, and news ----------------------------------------------- Get the latest ideas, announcements, partnerships, and Web3 news emerging from the Polygon ecosystem. https://polygon.technology ![](https://storage.googleapis.com/papyrus_images/6607ebfa0a77daa7cc76665a1cc4df542a7f48de38e95acef80d69041ef473b7.png) ](https://blog.polygon.technology/the-future-is-now-for-ethereum-scaling-introducing-polygon-zkevm/) [![]({{DOMAIN}}/editor/youtube/play.png)](https://www.youtube.com/watch?v=sokVnpaqIEc) 0a: [https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8) [![User Avatar](https://storage.googleapis.com/papyrus_images/3b35e49b45fa2f0667ab62b1c391d4efae2ef95c90175509ff984305144b52bf.jpg)](https://twitter.com/toghrulmaharram) [Toghrul Maharramov 🇺🇦](https://twitter.com/toghrulmaharram) [@toghrulmaharram](https://twitter.com/toghrulmaharram) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/toghrulmaharram/status/1518270138876891138) EVM-compatibility = Solidity/Vyper-level compatibility EVM-equivalence = EVM bytecode-level compatibility zkEVM = EVM specification-level compatibility [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 91](https://twitter.com/toghrulmaharram/status/1518270138876891138)[ 11:46 AM • Apr 24, 2022 ](https://twitter.com/toghrulmaharram/status/1518270138876891138) [https://docs.google.com/presentation/d/1XB96F9ahIlGUevpOTdi-yx\_gkrwmX4WGcCjwf3gEiYc/edit#slide=id.g13232b2e9d8\_0\_401](https://docs.google.com/presentation/d/1XB96F9ahIlGUevpOTdi-yx_gkrwmX4WGcCjwf3gEiYc/edit#slide=id.g13232b2e9d8_0_401) 0b: [ Privacy Stewards of Ethereum ---------------------------- Enhancing Ethereum through cryptographic research and collective experimentation. https://pse.dev ](https://appliedzkp.org/) [![User Avatar](https://storage.googleapis.com/papyrus_images/f5ac47444c58c5c94fcb2bbb2d81e736e9d5a474f9e9cadb534d32ad677b77eb.jpg)](https://twitter.com/0xShitTrader) [Eugene Chen](https://twitter.com/0xShitTrader) [@0xShitTrader](https://twitter.com/0xShitTrader) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xShitTrader/status/1549816145053728769) ZK EVM (approximately) creates abundant EVM blockspace with Ethereum's security guarantees, out of thin air. It works by using lots of cheap resources (off-chain proving) to reduce usage of expensive resources (on-chain proofs). Then ZK lets you inherit L1 security guarantees. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 31](https://twitter.com/0xShitTrader/status/1549816145053728769)[ 12:58 PM • Jul 20, 2022 ](https://twitter.com/0xShitTrader/status/1549816145053728769) [![User Avatar](https://storage.googleapis.com/papyrus_images/8d87d09fe24c1ceefb912eb4f6b3f08c264f518dd87fdf9864a58ff29750bf12.jpg)](https://twitter.com/yezhang1998) [Ye Zhang 📜](https://twitter.com/yezhang1998) [@yezhang1998](https://twitter.com/yezhang1998) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/yezhang1998/status/1549771898393100288) I think all teams should focus on building things and ship more features. Proper marketing should be educating people about what is zkEVM, why it's important, what's the limitation, and what can be really supported :) Help Ethereum scale is our end goal. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 33](https://twitter.com/yezhang1998/status/1549771898393100288)[ 10:03 AM • Jul 20, 2022 ](https://twitter.com/yezhang1998/status/1549771898393100288) 0c: [ The different types of ZK-EVMs ------------------------------ The core goal of all of these projects is the same: to use ZK-SNARK technology to make cryptographic proofs of execution of Ethereum-like transactions, either to make it much easier to verify the Ethereum chain itself or to build ZK-rollups that are (close to) equivalent to what Ethereum provides but are much more scalable. https://vitalik.eth.limo ![](https://storage.googleapis.com/papyrus_images/083f3248c0bcecdc509aa6d5fcdd4aea51df40277c599b86dcb1891b47981b20.png) ](https://vitalik.eth.limo/general/2022/08/04/zkevm.html) [https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8](https://foresightventures.medium.com/foresight-ventures-zk-zkvm-zkevm-and-their-future-6fb4b8b527d8) [![User Avatar](https://storage.googleapis.com/papyrus_images/146ea7b71865d96b3cf8d4f5bb978b7abaa56e5fea1455f55d9409b57b25e0d7.jpg)](https://twitter.com/0xalizk) [alizk.eth 🍉](https://twitter.com/0xalizk) [@0xalizk](https://twitter.com/0xalizk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xalizk/status/1422655305540902913) So far there has been three approaches to general compute in zk: VM from scratch (Starkware) zkEVM at the IR level (zkSync) zkEVM at the opcode level (Hermez) ![😍](https://abs-0.twimg.com/emoji/v2/72x72/1f60d.png) This will do to coordination what Berners-Lee's hypertext (www) did to communication [x.com/l2beatcom/stat…](https://t.co/lgyz4rYzYc) [![User Avatar](https://storage.googleapis.com/papyrus_images/7bd57d3baa2dfa4ae96d8a05dcc1b971863df0f486eeb6a1445f10ec7c156b71.jpg)](https://twitter.com/l2beat) [L2BEAT 💗](https://twitter.com/l2beat) [@l2beat](https://twitter.com/l2beat) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/l2beat/status/1422618146066911232) 3/ [@jbaylina](https://twitter.com/jbaylina) explains how @hermez (zk-rollup) will support EVM. Jordi talks about real support for EVM opcodes, not transpiling from Solidity/YUL ![🤯](https://abs-0.twimg.com/emoji/v2/72x72/1f92f.png) [youtube.com/watch?v=17d5DG…](https://t.co/BdR6RBQtZg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 37](https://twitter.com/0xalizk/status/1422655305540902913)[ 3:27 PM • Aug 3, 2021 ](https://twitter.com/0xalizk/status/1422655305540902913) [![User Avatar](https://storage.googleapis.com/papyrus_images/3b35e49b45fa2f0667ab62b1c391d4efae2ef95c90175509ff984305144b52bf.jpg)](https://twitter.com/toghrulmaharram) [Toghrul Maharramov 🇺🇦](https://twitter.com/toghrulmaharram) [@toghrulmaharram](https://twitter.com/toghrulmaharram) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/toghrulmaharram/status/1550065886064779265) Nope, I was arguing definitions :D Our approach is more closely aligned with Ethereum, their approach is more Prover-friendly [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 2](https://twitter.com/toghrulmaharram/status/1550065886064779265)[ 5:31 AM • Jul 21, 2022 ](https://twitter.com/toghrulmaharram/status/1550065886064779265) [![User Avatar](https://storage.googleapis.com/papyrus_images/146ea7b71865d96b3cf8d4f5bb978b7abaa56e5fea1455f55d9409b57b25e0d7.jpg)](https://twitter.com/0xalizk) [alizk.eth 🍉](https://twitter.com/0xalizk) [@0xalizk](https://twitter.com/0xalizk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xalizk/status/1498647477754474502) Zooming in the different approaches to zkEVM: \- systemic complexity: transpiler-based approaches like zkSync and Warp (Cairo->Solidity) \- encapsulated complexity: per-opcode circuits approach e.g. Hermez and EF working group [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 16](https://twitter.com/0xalizk/status/1498647477754474502)[ 7:12 AM • Mar 1, 2022 ](https://twitter.com/0xalizk/status/1498647477754474502) [![User Avatar](https://storage.googleapis.com/papyrus_images/82a814e99c8f478bb4dc29c737ea15cd6b00da803533c0db49e8fd1cc3801e8d.jpg)](https://twitter.com/LuozhuZhang) [Luozhu](https://twitter.com/LuozhuZhang) [@LuozhuZhang](https://twitter.com/LuozhuZhang) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/LuozhuZhang/status/1538166119785111552) [#zkEVM](https://twitter.com/hashtag/zkEVM) has been the holy grail of layer2 and Ethereum scaling and is at the forefront of the blockchain && ethereum There's a lot of zkp and engineering innovation here, bringing together all the most talented people in the Ethereum ecosystem [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 476](https://twitter.com/LuozhuZhang/status/1538166119785111552)[ 9:25 AM • Jun 18, 2022 ](https://twitter.com/LuozhuZhang/status/1538166119785111552) [![User Avatar](https://storage.googleapis.com/papyrus_images/146ea7b71865d96b3cf8d4f5bb978b7abaa56e5fea1455f55d9409b57b25e0d7.jpg)](https://twitter.com/0xalizk) [alizk.eth 🍉](https://twitter.com/0xalizk) [@0xalizk](https://twitter.com/0xalizk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xalizk/status/1422655305540902913) So far there has been three approaches to general compute in zk: VM from scratch (Starkware) zkEVM at the IR level (zkSync) zkEVM at the opcode level (Hermez) ![😍](https://abs-0.twimg.com/emoji/v2/72x72/1f60d.png) This will do to coordination what Berners-Lee's hypertext (www) did to communication [x.com/l2beatcom/stat…](https://t.co/lgyz4rYzYc) [![User Avatar](https://storage.googleapis.com/papyrus_images/7bd57d3baa2dfa4ae96d8a05dcc1b971863df0f486eeb6a1445f10ec7c156b71.jpg)](https://twitter.com/l2beat) [L2BEAT 💗](https://twitter.com/l2beat) [@l2beat](https://twitter.com/l2beat) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/l2beat/status/1422618146066911232) 3/ [@jbaylina](https://twitter.com/jbaylina) explains how @hermez (zk-rollup) will support EVM. Jordi talks about real support for EVM opcodes, not transpiling from Solidity/YUL ![🤯](https://abs-0.twimg.com/emoji/v2/72x72/1f92f.png) [youtube.com/watch?v=17d5DG…](https://t.co/BdR6RBQtZg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 37](https://twitter.com/0xalizk/status/1422655305540902913)[ 3:27 PM • Aug 3, 2021 ](https://twitter.com/0xalizk/status/1422655305540902913) [![User Avatar](https://storage.googleapis.com/papyrus_images/146ea7b71865d96b3cf8d4f5bb978b7abaa56e5fea1455f55d9409b57b25e0d7.jpg)](https://twitter.com/0xalizk) [alizk.eth 🍉](https://twitter.com/0xalizk) [@0xalizk](https://twitter.com/0xalizk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xalizk/status/1549999424650215430) One is not more "EVM equivalent" than another simply bc, again, equivalent dev exp can easily be replicated by wrapping when needed. 'equiv > compatibility' is a marketing concept. There r other more interesting axes to compare the 2 implementations once both r out of R&D.../3 [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 15](https://twitter.com/0xalizk/status/1549999424650215430)[ 1:07 AM • Jul 21, 2022 ](https://twitter.com/0xalizk/status/1549999424650215430) [![User Avatar](https://storage.googleapis.com/papyrus_images/a55c27c8561205e3e8cee213caf28f79e4c2c8325afb112ff3238018bf16ee56.jpg)](https://twitter.com/cronokirby) [Lúcás Meier](https://twitter.com/cronokirby) [@cronokirby](https://twitter.com/cronokirby) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/cronokirby/status/1550750051873562624) The compiler approach gives you much more control, because you're not forced to implement low level operations directly in your circuits, but can rather focus on the intent of the code. Going from the IR lets you support more languages than solidity, with similar flexibility [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 16](https://twitter.com/cronokirby/status/1550750051873562624)[ 2:49 AM • Jul 23, 2022 ](https://twitter.com/cronokirby/status/1550750051873562624) [![User Avatar](https://storage.googleapis.com/papyrus_images/87160bdddcdb97eb3750a43815dc34fd21cb566565e85d8ddf78a28dec7690ef.png)](https://twitter.com/henrlihenrli) [Henri (BTCFi arc)](https://twitter.com/henrlihenrli) [@henrlihenrli](https://twitter.com/henrlihenrli) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/henrlihenrli/status/1559173089971146753) Storage proofs (SP). It's an unsexy name for a very, very powerful StarkNet tool. #4 in our exploration of why people get excited about StarkNet. Let’s take a look. SP are like CRISPR/Cas9 for blockchain devs. ![](https://pbs.twimg.com/tweet_video_thumb/FaNLp26UUAAdHQb.jpg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 68](https://twitter.com/henrlihenrli/status/1559173089971146753)[ 8:40 AM • Aug 15, 2022 ](https://twitter.com/henrlihenrli/status/1559173089971146753) [![User Avatar](https://storage.googleapis.com/papyrus_images/87160bdddcdb97eb3750a43815dc34fd21cb566565e85d8ddf78a28dec7690ef.png)](https://twitter.com/henrlihenrli) [Henri (BTCFi arc)](https://twitter.com/henrlihenrli) [@henrlihenrli](https://twitter.com/henrlihenrli) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/henrlihenrli/status/1559173135789830144) Next up: f r a c t a l s c a l i n g [x.com/henrlihenrli/s…](https://t.co/jW6flZYyXH) [![User Avatar](https://storage.googleapis.com/papyrus_images/87160bdddcdb97eb3750a43815dc34fd21cb566565e85d8ddf78a28dec7690ef.png)](https://twitter.com/henrlihenrli) [Henri (BTCFi arc)](https://twitter.com/henrlihenrli) [@henrlihenrli](https://twitter.com/henrlihenrli) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/henrlihenrli/status/1554803641814372353) I've recently prepared a presentation called "Why people get excited about validity rollups". I tried to explain why people seem to want to build on StarkNet instead of how it works. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 8](https://twitter.com/henrlihenrli/status/1559173135789830144)[ 8:40 AM • Aug 15, 2022 ](https://twitter.com/henrlihenrli/status/1559173135789830144) 1: [https://github.com/0xPolygonHermez/zkevm-doc/blob/main/mkdocs/docs/zkEVM/Polygon-zkEVM-Archtectural-Overview.md](https://github.com/0xPolygonHermez/zkevm-doc/blob/main/mkdocs/docs/zkEVM/Polygon-zkEVM-Archtectural-Overview.md) [ Polygon Blog | Announcements, updates, and news ----------------------------------------------- Get the latest ideas, announcements, partnerships, and Web3 news emerging from the Polygon ecosystem. https://polygon.technology ![](https://storage.googleapis.com/papyrus_images/6607ebfa0a77daa7cc76665a1cc4df542a7f48de38e95acef80d69041ef473b7.png) ](https://blog.polygon.technology/zkverse-deep-dive-into-polygon-hermez-2-0/) [![]({{DOMAIN}}/editor/youtube/play.png)](https://www.youtube.com/watch?v=T2fH1NlHnAc) 1b: [![User Avatar](https://storage.googleapis.com/papyrus_images/0ac65f9cc39b856a1abb21e60a095934c3e2664527453f7e8491ff8cd13ab141.jpg)](https://twitter.com/blendino_) [Dino](https://twitter.com/blendino_) [@blendino\_](https://twitter.com/blendino_) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/blendino_/status/1544868275829571584) My take on Polygon's security spectrum and where each solution lands - from standalone chains to fully secured rollups ![](https://storage.googleapis.com/papyrus_images/51fdeef554426fa1b525308d3a140e1fd9d6af7c8f6e14ec66d72e4f3a95294f.jpg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 192](https://twitter.com/blendino_/status/1544868275829571584)[ 9:17 PM • Jul 6, 2022 ](https://twitter.com/blendino_/status/1544868275829571584) 1c: [![User Avatar](https://storage.googleapis.com/papyrus_images/49c6dac0e7fe54ebc066bdb6d6d725fd3050cd80a47740dfb53db8d4db19f8bb.jpg)](https://twitter.com/Ingo_zk) [Ingonyama](https://twitter.com/Ingo_zk) [@Ingo\_zk](https://twitter.com/Ingo_zk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/Ingo_zk/status/1550121968904507393) Goldilocks are used as the base field. 256 bit operations are highly efficient. Keccek circuits are computed in parallel. A Poseidon-hash Merkle tree is used to store the entire system ![](https://pbs.twimg.com/tweet_video_thumb/FYMjtaFUsAI4cN3.jpg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 9](https://twitter.com/Ingo_zk/status/1550121968904507393)[ 9:14 AM • Jul 21, 2022 ](https://twitter.com/Ingo_zk/status/1550121968904507393) [ Polygon Blog | Announcements, updates, and news ----------------------------------------------- Get the latest ideas, announcements, partnerships, and Web3 news emerging from the Polygon ecosystem. https://polygon.technology ![](https://storage.googleapis.com/papyrus_images/6607ebfa0a77daa7cc76665a1cc4df542a7f48de38e95acef80d69041ef473b7.png) ](https://blog.polygon.technology/introducing-plonky2/) [![User Avatar](https://storage.googleapis.com/papyrus_images/b2e4ad02fa3506ec7b264511e6e4ec8e162c4383a096a5649db5457cd7a31f50.jpg)](https://twitter.com/_bfarmer) [Brendan Farmer](https://twitter.com/_bfarmer) [@\_bfarmer](https://twitter.com/_bfarmer) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/_bfarmer/status/1549807101010010115) This isn't really fair right? Arithmetic circuits only support field arithmetic, so Scroll and Polygon must both convert opcodes into circuit form. Important thing is whether this conversion is sound wrt the opcode Seems like a distinction without a difference, just marketing. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 8](https://twitter.com/_bfarmer/status/1549807101010010115)[ 12:23 PM • Jul 20, 2022 ](https://twitter.com/_bfarmer/status/1549807101010010115) [![User Avatar](https://storage.googleapis.com/papyrus_images/3b35e49b45fa2f0667ab62b1c391d4efae2ef95c90175509ff984305144b52bf.jpg)](https://twitter.com/toghrulmaharram) [Toghrul Maharramov 🇺🇦](https://twitter.com/toghrulmaharram) [@toghrulmaharram](https://twitter.com/toghrulmaharram) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/toghrulmaharram/status/1549863723556282370) From what I understood, EVM opcodes are interpreted in zkASM ([github.com/0xPolygonHerme…](https://t.co/dpRrhvdFye)) and then executed by the zkExecutor. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 2](https://twitter.com/toghrulmaharram/status/1549863723556282370)[ 4:08 PM • Jul 20, 2022 ](https://twitter.com/toghrulmaharram/status/1549863723556282370) [![User Avatar](https://storage.googleapis.com/papyrus_images/b363ae1d42e85bfc8cd6be5bb703bc175191fac20cb12bd087278ae7b04a241f.jpg)](https://twitter.com/dlubarov) [Daniel Lubarov](https://twitter.com/dlubarov) [@dlubarov](https://twitter.com/dlubarov) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/dlubarov/status/1550491404345950216) I wouldn't call it translation - there's just a function that implements each instruction, as with Geth and most interpreters. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 9](https://twitter.com/dlubarov/status/1550491404345950216)[ 9:42 AM • Jul 22, 2022 ](https://twitter.com/dlubarov/status/1550491404345950216) [![User Avatar](https://storage.googleapis.com/papyrus_images/8d87d09fe24c1ceefb912eb4f6b3f08c264f518dd87fdf9864a58ff29750bf12.jpg)](https://twitter.com/yezhang1998) [Ye Zhang 📜](https://twitter.com/yezhang1998) [@yezhang1998](https://twitter.com/yezhang1998) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/yezhang1998/status/1549808592936906752) Also, we take the execution trace directly from Geth and can easily generate proof any mainnet block. Again, I might be biased, so I will use some other references from Optimism: [x.com/kelvinfichter/…](https://t.co/tAlWls0oBP) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 3](https://twitter.com/yezhang1998/status/1549808592936906752)[ 12:28 PM • Jul 20, 2022 ](https://twitter.com/yezhang1998/status/1549808592936906752) [![User Avatar](https://storage.googleapis.com/papyrus_images/b363ae1d42e85bfc8cd6be5bb703bc175191fac20cb12bd087278ae7b04a241f.jpg)](https://twitter.com/dlubarov) [Daniel Lubarov](https://twitter.com/dlubarov) [@dlubarov](https://twitter.com/dlubarov) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/dlubarov/status/1550506366527086594) Those zkASM instructions are baked in the system though, just as opAdd is baked into Geth's binary. If we consider that translation then any interpreter does translation. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 20](https://twitter.com/dlubarov/status/1550506366527086594)[ 10:41 AM • Jul 22, 2022 ](https://twitter.com/dlubarov/status/1550506366527086594) [![User Avatar](https://storage.googleapis.com/papyrus_images/b363ae1d42e85bfc8cd6be5bb703bc175191fac20cb12bd087278ae7b04a241f.jpg)](https://twitter.com/dlubarov) [Daniel Lubarov](https://twitter.com/dlubarov) [@dlubarov](https://twitter.com/dlubarov) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/dlubarov/status/1550491438470668290) Even if it was translating, translation at runtime generally has no bearing on compatibility. See x86 (microcode), HotSpot (JIT), VMWare (dynamic binary translation), etc. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 16](https://twitter.com/dlubarov/status/1550491438470668290)[ 9:42 AM • Jul 22, 2022 ](https://twitter.com/dlubarov/status/1550491438470668290) [![User Avatar](https://storage.googleapis.com/papyrus_images/3b35e49b45fa2f0667ab62b1c391d4efae2ef95c90175509ff984305144b52bf.jpg)](https://twitter.com/toghrulmaharram) [Toghrul Maharramov 🇺🇦](https://twitter.com/toghrulmaharram) [@toghrulmaharram](https://twitter.com/toghrulmaharram) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/toghrulmaharram/status/1550065886064779265) Nope, I was arguing definitions :D Our approach is more closely aligned with Ethereum, their approach is more Prover-friendly [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 2](https://twitter.com/toghrulmaharram/status/1550065886064779265)[ 5:31 AM • Jul 21, 2022 ](https://twitter.com/toghrulmaharram/status/1550065886064779265) [![User Avatar](https://storage.googleapis.com/papyrus_images/146ea7b71865d96b3cf8d4f5bb978b7abaa56e5fea1455f55d9409b57b25e0d7.jpg)](https://twitter.com/0xalizk) [alizk.eth 🍉](https://twitter.com/0xalizk) [@0xalizk](https://twitter.com/0xalizk) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/0xalizk/status/1549999427791765504) By Maintainability here I mean how clean and encapsulated the implementation is, how easily auditable, how easily changeable, etc .. software engineering issues. That's where one implementation prove superior to the other. /fin [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 21](https://twitter.com/0xalizk/status/1549999427791765504)[ 1:07 AM • Jul 21, 2022 ](https://twitter.com/0xalizk/status/1549999427791765504) [![User Avatar](https://storage.googleapis.com/papyrus_images/af17bd449ad349529246c1af8ef6dbfa839397411f3afa8a58835b943b616996.jpg)](https://twitter.com/mt_1466) [MT](https://twitter.com/mt_1466) [@mt\_1466](https://twitter.com/mt_1466) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/mt_1466/status/1550490476201082880) 2/ Polygon consists of a flagship proof-of-stake [#PoS](https://twitter.com/hashtag/PoS) sidechain called Matic POS. However, it also consists of a framework known as the Polygon SDK that allows developers to build and connect [#L2](https://twitter.com/hashtag/L2) scaling solutions such as Optimistic Rollups, zk-rollups, and its zkEVM. [@100y\_eth](https://twitter.com/100y_eth) ![](https://storage.googleapis.com/papyrus_images/34d0e563a91e53c78ecd56b5ecd4db3bd86e5ec674f28159383451dba2161db7.jpg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 6](https://twitter.com/mt_1466/status/1550490476201082880)[ 9:38 AM • Jul 22, 2022 ](https://twitter.com/mt_1466/status/1550490476201082880) [![]({{DOMAIN}}/editor/youtube/play.png)](https://www.youtube.com/watch?v=T2fH1NlHnAc) 2a: [https://foresightventures.medium.com/foresight-ventures-mev-definition-difference-decrease-33923783c793](https://foresightventures.medium.com/foresight-ventures-mev-definition-difference-decrease-33923783c793) [https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e](https://foresightventures.medium.com/foresight-ventures-almost-everything-about-rollup-95319ef0675e) 2b: [https://foresightventures.medium.com/foresight-ventures-unified-to-divided-modular-blockchain-and-data-availability-layer-459b35673381](https://foresightventures.medium.com/foresight-ventures-unified-to-divided-modular-blockchain-and-data-availability-layer-459b35673381) [https://vitalik.ca/general/2020/08/20/trust.html](https://vitalik.ca/general/2020/08/20/trust.html) 3d: [![User Avatar](https://storage.googleapis.com/papyrus_images/8ee67083c3bde5d1a62c582d16e1839bab249654d94210edd9458d1da407416f.jpg)](https://twitter.com/sandeepnailwal) [Sandeep | CEO, Polygon Foundation (※,※)](https://twitter.com/sandeepnailwal) [@sandeepnailwal](https://twitter.com/sandeepnailwal) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/sandeepnailwal/status/1550009537406574593) Sir value accrual due to staking >>>> gas fees. If a network generates $100mn in txn fees and assume 5% is a good rate of return, then people would be willing to stake $2bn worth of assets to get the right to earn that txn fee. Doesnt matter which currency txn fees is coming in [![User Avatar](https://storage.googleapis.com/papyrus_images/8ee67083c3bde5d1a62c582d16e1839bab249654d94210edd9458d1da407416f.jpg)](https://twitter.com/sandeepnailwal) [Sandeep | CEO, Polygon Foundation (※,※)](https://twitter.com/sandeepnailwal) [@sandeepnailwal](https://twitter.com/sandeepnailwal) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/sandeepnailwal/status/1550008344991203329) Haha, i think most in crypto dont understand that gas fees(high velocity use case) doesnt add that much value to an asset. Purpose of staking is to provide security/reliability/uptime in return of txn fees. The more txn fees/usage in the network, more ppl stake hence more demand [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 33](https://twitter.com/sandeepnailwal/status/1550009537406574593)[ 1:47 AM • Jul 21, 2022 ](https://twitter.com/sandeepnailwal/status/1550009537406574593) [![User Avatar](https://storage.googleapis.com/papyrus_images/7214c8e21973b58c94ae83c6dfe5b5748f1cd6a54e7c50c6285b6528e0c5e407.jpg)](https://twitter.com/sreeramkannan) [Sreeram Kannan](https://twitter.com/sreeramkannan) [@sreeramkannan](https://twitter.com/sreeramkannan) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/sreeramkannan/status/1551439980991377410) The problem in alt-L1 has never been the lack of innovation. The problem has been that such innovation cannot leverage the existing large trust networks and thus each has to solve a new multi-sided bootstrapping problem. [![User Avatar](https://storage.googleapis.com/papyrus_images/f9d1aad18543cac5eb501b6972050143df6c8feaf711c7741de25f4791145ce4.jpg)](https://twitter.com/dystopiabreaker) [⚡️🌙](https://twitter.com/dystopiabreaker) [@dystopiabreaker](https://twitter.com/dystopiabreaker) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/dystopiabreaker/status/1551335449473347584) tell me you don't know what l1 teams are doing without saying you don't know what l1 teams are doing [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 79](https://twitter.com/sreeramkannan/status/1551439980991377410)[ 12:31 AM • Jul 25, 2022 ](https://twitter.com/sreeramkannan/status/1551439980991377410) 4a: [ The different types of ZK-EVMs ------------------------------ The core goal of all of these projects is the same: to use ZK-SNARK technology to make cryptographic proofs of execution of Ethereum-like transactions, either to make it much easier to verify the Ethereum chain itself or to build ZK-rollups that are (close to) equivalent to what Ethereum provides but are much more scalable. https://vitalik.eth.limo ![](https://storage.googleapis.com/papyrus_images/083f3248c0bcecdc509aa6d5fcdd4aea51df40277c599b86dcb1891b47981b20.png) ](https://vitalik.eth.limo/general/2022/08/04/zkevm.html) 4b: [![User Avatar](https://storage.googleapis.com/papyrus_images/9b4841d8150904fda36de46030ec8a972e926cccf94bc84e17b2a6aa0315a6ba.jpg)](https://twitter.com/VitalikButerin) [vitalik.eth](https://twitter.com/VitalikButerin) [@VitalikButerin](https://twitter.com/VitalikButerin) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/VitalikButerin/status/1553342590786813952) Hybrid idea: optimistic + ZK, governance only adjudicates bugs between the two 1\. Publish block 2\. Wait 24h for fraud challenges. 3a. If no challenge, publish ZK SNARK, finalize. 3b. If there is a challenge, decide based on 2-of-3 of (challenge game, ZK SNARK, governance) [![User Avatar](https://storage.googleapis.com/papyrus_images/b4ee5971ae32a8a2e0ddc93eaf9238a740e7c45a75b99a17aa4a8b3bde5cc288.jpg)](https://twitter.com/kelvinfichter) [smartcontracts.eth](https://twitter.com/kelvinfichter) [@kelvinfichter](https://twitter.com/kelvinfichter) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/kelvinfichter/status/1553323194500763649) But there's no reason why Bedrock can't use a ZK proof System instead ![👀](https://abs-0.twimg.com/emoji/v2/72x72/1f440.png)![👀](https://abs-0.twimg.com/emoji/v2/72x72/1f440.png). We think Optimistic Rollups currently have massive advantages over their ZK counterparts, but Bedrock has been designed to make a seamless transition between Optimistic and ZK possible. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 1,879](https://twitter.com/VitalikButerin/status/1553342590786813952)[ 6:31 AM • Jul 30, 2022 ](https://twitter.com/VitalikButerin/status/1553342590786813952) 4c: [ Professional Programming: The First 10 Years -------------------------------------------- Last month, April 2022, marked the 10 year anniversary of my start as a professional programmer. I started programming earlier than that, but hadn't been paid a salary. As a teenager I built websites and IRC bots and wrote tiny Python scripts. Then I stopped and played guitar for a few years. https://thorstenball.com ](https://thorstenball.com/blog/2022/05/17/professional-programming-the-first-10-years/) 4d: [![User Avatar](https://storage.googleapis.com/papyrus_images/0d70fe615160db4588218d63d7996101d21a0e1820fd0e102128a1babbf8fd84.jpg)](https://twitter.com/itamarl) [itamar](https://twitter.com/itamarl) [@itamarl](https://twitter.com/itamarl) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/itamarl/status/1552616078068838401) My unpopular take on EVM equivalence: L2 focusing blindly on EVM equivalence are shooting themselves in the foot ![🧵](https://abs-0.twimg.com/emoji/v2/72x72/1f9f5.png) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 279](https://twitter.com/itamarl/status/1552616078068838401)[ 6:24 AM • Jul 28, 2022 ](https://twitter.com/itamarl/status/1552616078068838401) [![User Avatar](https://storage.googleapis.com/papyrus_images/d0bdd63152738b2063e1fa79141ab9b2c21a0e22bc3b579ec51522cc64ba5d8c.jpg)](https://twitter.com/sgoldfed) [Steven Goldfeder](https://twitter.com/sgoldfed) [@sgoldfed](https://twitter.com/sgoldfed) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/sgoldfed/status/1551607983167229954) This is a common misconception (and to the extent that it’s true, it applies to ORU too). In all Rollups, constant overhead costs can be amortized (more txs, lower per tx cost). But there’s also a linear per tx proving cost (and in some zk designs it’s superlinear) [![User Avatar](https://storage.googleapis.com/papyrus_images/1ce34b35fd7165e3777980a0cf09d2fc2802b60d74cf6e50738d6b6e0af53d75.jpg)](https://twitter.com/rayzhueth) [Ray Zhu](https://twitter.com/rayzhueth) [@rayzhueth](https://twitter.com/rayzhueth) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/rayzhueth/status/1551381868787904512) On Ethereum, an increase in demand leads to higher fees. In zk rollups, an increase in demand leads to lower fees. This is why zk rollups solve Ethereum scalability. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 41](https://twitter.com/sgoldfed/status/1551607983167229954)[ 11:39 AM • Jul 25, 2022 ](https://twitter.com/sgoldfed/status/1551607983167229954) [![User Avatar](https://storage.googleapis.com/papyrus_images/0b2b5c6b37d2a716197d6a2f3f9899c97af5ff54bb85d51353f5e95a07ad7803.png)](https://twitter.com/EdFelten) [Ed Felten](https://twitter.com/EdFelten) [@EdFelten](https://twitter.com/EdFelten) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/EdFelten/status/1555163841469841411) The Arbitrum Nitro node does 1742851 sha256 hashes/sec on my laptop. So optimistic is >20,000x faster/cheaper than zk for these operations. [![User Avatar](https://storage.googleapis.com/papyrus_images/98f4af000479563bbe59a7da8f119e1427976c6c01d1e7152b9bf22a86136cc5.jpg)](https://twitter.com/sebastienladuca) [Sebastien La Duca](https://twitter.com/sebastienladuca) [@sebastienladuca](https://twitter.com/sebastienladuca) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/sebastienladuca/status/1554833632618983425) plonky2 is insane. Just used it to write a STARK doing 84 sha256 hashes/sec on a macbook from 2019. And it's far from optimized. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 70](https://twitter.com/EdFelten/status/1555163841469841411)[ 7:08 AM • Aug 4, 2022 ](https://twitter.com/EdFelten/status/1555163841469841411) [![User Avatar](https://storage.googleapis.com/papyrus_images/fe28da91e65c7a6d771b47c4ba8866fe9cc7bfaa5ade0bd1fdad88a6c0a707b9.jpg)](https://twitter.com/MihailoBjelic) [Mihailo Bjelic](https://twitter.com/MihailoBjelic) [@MihailoBjelic](https://twitter.com/MihailoBjelic) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/MihailoBjelic/status/1554994843851554816) And what if an L2 has both the best ecosystem development and superior technology? Asking for a friend. ![🙃](https://abs-0.twimg.com/emoji/v2/72x72/1f643.png) [![User Avatar](https://storage.googleapis.com/papyrus_images/5ac29cba4b266d09d11b0a2e892a16415ba62b2a0f7d62862b968ed11be37781.jpg)](https://twitter.com/pseudotheos) [pseudo 🇺🇦](https://twitter.com/pseudotheos) [@pseudotheos](https://twitter.com/pseudotheos) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/pseudotheos/status/1554937456050544641) The best tech doesn't always win. The L2 with the best ecosystem development will likely come out ahead, regardless of technical superiority. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 103](https://twitter.com/MihailoBjelic/status/1554994843851554816)[ 7:57 PM • Aug 3, 2022 ](https://twitter.com/MihailoBjelic/status/1554994843851554816) [![User Avatar](https://storage.googleapis.com/papyrus_images/5ac29cba4b266d09d11b0a2e892a16415ba62b2a0f7d62862b968ed11be37781.jpg)](https://twitter.com/pseudotheos) [pseudo 🇺🇦](https://twitter.com/pseudotheos) [@pseudotheos](https://twitter.com/pseudotheos) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/pseudotheos/status/1554937456050544641) The best tech doesn't always win. The L2 with the best ecosystem development will likely come out ahead, regardless of technical superiority. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 128](https://twitter.com/pseudotheos/status/1554937456050544641)[ 4:09 PM • Aug 3, 2022 ](https://twitter.com/pseudotheos/status/1554937456050544641) Others: [ Nearly-zero cost attack scenario on Optimistic Rollup ----------------------------------------------------- TL;DR: Optimistic rollup relies on absolute censorship-resistance of L1 for its security. While L1 provides some decent economic incentives against mass censorship, it is easy to construct a scenario in which censorship of a particular single transaction is strongly rewarded, while non-censoring behavior is strongly penalized for a prolonged period of time. https://ethresear.ch ![](https://storage.googleapis.com/papyrus_images/ec5c5091f327fc5bba77649a771a3043bbcf2e031d786512fb3d08ee7a883eaa.png) ](https://ethresear.ch/t/nearly-zero-cost-attack-scenario-on-optimistic-rollup/6336/3) [ A pre-consensus mechanism to secure instant finality and long interval in zkRollup ---------------------------------------------------------------------------------- 1) TL;DR : This post proposes a pre-consensus mechanism to secure instant finality and reduce verification gas cost, without compromising instant fund exit in zkRollup. 2) Background & Motivation : zkRollup can achieve instant finality by adopting a short enough commitment interval (like 10 min). https://ethresear.ch ![](https://storage.googleapis.com/papyrus_images/ec5c5091f327fc5bba77649a771a3043bbcf2e031d786512fb3d08ee7a883eaa.png) ](https://ethresear.ch/t/a-pre-consensus-mechanism-to-secure-instant-finality-and-long-interval-in-zkrollup/8749) [![User Avatar](https://storage.googleapis.com/papyrus_images/8d87d09fe24c1ceefb912eb4f6b3f08c264f518dd87fdf9864a58ff29750bf12.jpg)](https://twitter.com/yezhang1998) [Ye Zhang 📜](https://twitter.com/yezhang1998) [@yezhang1998](https://twitter.com/yezhang1998) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/yezhang1998/status/1553785807521325057) Btw, there is a fundamental difference between arithmetic circuit (zkEVM, zkMIPS, etc) and prover ASIC "circuit". The former is "application" and the latter is backend proof generation. In most cases, prover ASIC can be used to support all applications. ASICs won't be trashed. ![](https://storage.googleapis.com/papyrus_images/9fe9ebd13d3d4d37af92ebc289538c32e4f16ce1dabaffc5f754472a97664e41.jpg) [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 3](https://twitter.com/yezhang1998/status/1553785807521325057)[ 11:52 AM • Jul 31, 2022 ](https://twitter.com/yezhang1998/status/1553785807521325057) [![User Avatar](https://storage.googleapis.com/papyrus_images/b4ee5971ae32a8a2e0ddc93eaf9238a740e7c45a75b99a17aa4a8b3bde5cc288.jpg)](https://twitter.com/kelvinfichter) [smartcontracts.eth](https://twitter.com/kelvinfichter) [@kelvinfichter](https://twitter.com/kelvinfichter) [![Twitter Logo](https://paragraph.com/editor/twitter/logo.png)](https://twitter.com/kelvinfichter/status/1553323160564404225) For a rollup to be truly secure and decentralized, it needs to have a proof mechanism (fault proofs or sometimes "fraud proofs") WITHOUT any kind of upgrade keys that can update the proof without a long delay. [![Like Icon](https://paragraph.com/editor/twitter/heart.png) 39](https://twitter.com/kelvinfichter/status/1553323160564404225)[ 5:14 AM • Jul 30, 2022 ](https://twitter.com/kelvinfichter/status/1553323160564404225) --- *Originally published on [msfew](https://paragraph.com/@msfew/all-about-polygon-zkevm-and-zkevm-rollup)*