“`html<\/p>\n
Greetings from London! This is a thrilling moment for the Ethereum ecosystem, and the momentum will only accelerate further as we near Altair [1]<\/a> [2]<\/a> and the Merge<\/a> in the upcoming months.<\/p>\n <\/p>\n The Beacon Chain currently has over 6.5 million Ether staked, with more than 200K active validators operating across five clients, and the network is now burning Ether<\/a> as part of the modifications introduced with the London upgrade.<\/p>\n <\/p>\n As always, significant advancements are being made by EF-supported initiatives and teams that contribute to enhancing our Ethereum experience. This roundup series provides a chance to showcase their endeavors aimed at expanding and refining Ethereum as a whole. Featured in this edition are updates from several teams spotlighted in the preceding Supported Teams update<\/a>, among others.<\/p>\n <\/p>\n Enjoy!<\/p>\n <\/p>\n <\/p>\n Written by ESP Team<\/em><\/p>\n <\/p>\n <\/p>\n <\/p>\n We are partnering with the Devcon team on a round of small grants and additional support for community event organizers. Organizers of both virtual and in-person events can directly apply for grants ranging from $500-1500 to cover expenses such as venue or equipment rental, promotional items, snacks, or other incidental costs. Discover more and apply here<\/a>. Lee esta p\u00e1gina en espa\u00f1ol<\/a>; \u7528\u4e2d\u6587\u9605\u8bfb\u672c\u9875<\/a>.<\/p>\n <\/p>\n We also recently revealed our Q1 Allocation Update<\/a>, detailing 47 grants awarded in Q1 amounting to $5,341,000.<\/p>\n <\/p>\n <\/p>\n Aside from the material featured in Danny Ryan\u2019s Finalized<\/span> series, the research team has continued exploring areas such as stateless research, proofs of custody for EVM execution, sharding specifications and prototypes, and various other scaling\/security research. Most of their advancements can be found in posts on ethresear.ch.<\/p>\n <\/p>\n Additionally, find a selection of their recent posts and other content below:<\/p>\n <\/p>\n Written by Sam Richards<\/em><\/p>\n <\/p>\n To enhance accessibility and encourage more community involvement, our team shares an overview of our quarterly roadmap objectives. View last quarter’s roadmap here: #2849.<\/em><\/p>\n <\/p>\n Salutations fellow Ethereans!<\/strong><\/p>\n <\/p>\n Wishing you a fantastic L2 summer \ud83d\ude0e (or winter for our counterparts in the southern hemisphere)! Hope you\u2019re enjoying your journey in this realm – we certainly are! As always, our mission with ethereum.org<\/a> is to establish the premier portal for Ethereum’s expanding community, serving as the welcoming gateway to Ethereum for millions of new visitors each month.<\/p>\n <\/p>\n <\/p>\n In Q3 our ethereum.org<\/a> product focus will be to match the astonishing progress in the field, enabling our wider community to stay updated on advancements in Ethereum network upgrades, Layer 2 initiatives, developer tools, user applications, and beyond.<\/p>\n <\/p>\n Thank you to the numerous individuals who have contributed content to date \u2764\ufe0f<\/p>\n <\/p>\n Discover how to get involved<\/a><\/p>\n <\/p>\n <\/p>\n Innovative funding methods for public goods offer tremendous potential for the Ethereum ecosystem and beyond the crypto world. Although not directly linked to ethereum.org, our team is part of the Ethereum Foundation, one of the largest funders of grants and public goods within the ecosystem. We are eager to enhance the cultural momentum surrounding ecosystem funding for public goods as well as experiment with allocation mechanisms for ecosystem support.<\/p>\n <\/p>\n We’ll continue our initiatives from Q2 with teams in the sector, aiming to introduce a CLR.fund<\/a> round for Eth2 projects on an L2 mainnet by the conclusion of Q3.<\/p>\n <\/p>\n This endeavor will also permit our team to stay abreast of the latest tools, technologies, and best practices associated with dapp development, ranging from testing and deployment tools to identity solutions and Layer 2 technologies. We plan to integrate these first-hand insights back into our developer resources<\/a>.<\/p>\n <\/p>\n Discover more, stay informed & get involved<\/a><\/p>\n <\/p>\n <\/p>\n Owing to our over 1,400 volunteer translators over recent years, ethereum.org now accommodates 35 languages<\/a>! Yet as the website has expanded & is continuously refreshed to remain aligned with developments in the space, many of our languages <\/p>\n With the addition of our new Translation Program Lead, @lukassim, we also intend to enhance our support documentation<\/a> and optimize our use of translation tools to elevate consistency and quality throughout the translation process.<\/p>\n <\/p>\n Discover how to participate<\/a><\/p>\n As evident from all the objectives outlined above, our achievements are fueled by our open-source community of contributors. Contributors come in various forms\u2014translators, developers, writers, designers, professionals, and enthusiasts. We aspire to continue educating and empowering individuals eager to engage with the Ethereum ecosystem and our ethereum.org community.<\/p>\n <\/p>\n Our new Community Lead, @minimalsm, will spearhead initiatives to support and uplift our expanding ethereum.org community. Stay tuned for the specific projects we plan to launch this quarter!<\/p>\n <\/p>\n Have suggestions? Connect with us on our Discord server<\/a> or here on GitHub.<\/p>\n <\/p>\n <\/p>\n We value input on our roadmap. Our guiding principles focus on delivering maximum value in the least amount of time, so if you have thoughts on what we should prioritize, please share! We welcome suggestions and PRs from any member of the community.<\/p>\n <\/p>\n Further details on contributing<\/a><\/p>\n <\/p>\n <\/p>\n Written by Alex Beregszaszi<\/em><\/p>\n <\/p>\n The Ewasm team has undergone a rebranding to a new name: Ipsilon.<\/strong> This name references the state transition function outlined in the Yellow Paper<\/a>. We wish to convey that our efforts have long encompassed more than just Ewasm.<\/p>\n <\/p>\n The primary focus of the team is the execution environment \/ engine of Ethereum (also known as the EVM or any forthcoming versions or alternatives). We conduct analysis and implementation of both our own and third-party proposals (i.e., new EIPs advocating changes to the EVM), provide tools (evmc<\/a>, evmone<\/a>, fizzy<\/a>), and assist existing teams (e.g., Solidity, go-ethereum, Silkworm) with implementation and analysis.<\/p>\n <\/p>\n Most of our content is available here<\/a>.<\/p>\n <\/p>\n <\/p>\n In the previous update<\/a> we mentioned the EVM Object Format (EOF) as an upcoming proposal. Significant progress has been made in the past three months. The initial step, EIP-3541<\/a>, has been integrated into the London update\u2014this only reserves a starting byte which can be utilized to incorporate EOF in a future protocol update.<\/p>\n <\/p>\n A concrete proposal, EIP-3540<\/a>, which presents the container format and code-and-data separation has been unveiled. Additionally, an explanatory document<\/a> providing background and a roadmap (which will be updated as we progress) has been issued, and we also conducted a PEEPanEIP presentation (video<\/a> and slides<\/a>).<\/p>\n <\/p>\n Both EIP-3541 and EIP-3540 have been executed in geth and evmone.<\/p>\n <\/p>\n Lastly, we presented a brief proposal to modernize EIP-2938 using EOF<\/a> and other teams exploring development on EOF<\/a>.<\/p>\n <\/p>\n <\/p>\n The second major topic on our agenda has been the address space extension, a necessity for the state expiry roadmap<\/a>.<\/p>\n <\/p>\n It was initially outlined in an Ethereum Magicians post and various discussions on the Eth R&D discord. Our specification<\/a> builds upon all existing work and strives to provide a cohesive overview of how to execute this modification. An additional document detailing a comprehensive set of test scenarios<\/a> has also been published.<\/p>\n <\/p>\n While the essence of the proposal is not overly complex, there are numerous implications<\/a>. This discussion document serves as the foundation for the ongoing Address Space Extension Working Group, which has already conducted three calls (recordings: “`html <\/p>\n <\/p>\n Regarding the subject of code merkleization \/ code chunking, we published an extensive evaluation of the implications of code chunking expenses<\/a>. The updated version of the verkle tree<\/a> proposition reassessed costs informed by these findings.<\/p>\n <\/p>\n The concept of an MCOPY<\/span> instruction<\/a> was inspired by the investigations on EVM384<\/a>. We released a brief overview<\/a> outlining this proposal, including a price estimation, and assessing the advantages for standard contracts apart from its application in EVM384.<\/p>\n <\/p>\n <\/p>\n <\/li>\n <\/li>\n<\/ul>\n <\/p>\n <\/p>\n <\/li>\n <\/li>\n<\/ul>\n <\/p>\n <\/p>\n The Formal Verification Team will share their own updates (relating to Act, hevm, SMTChecker and more) here<\/a>, and in recent months, various notes have also shown enhancements.<\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n <\/p>\n authored by Felix Lange<\/p>\n <\/p>\n In Q2, we released four updates of Geth. The team was primarily focused on executing the London fork modifications, particularly EIP-1559. Additionally, we performed extensive testing of the new snap sync, which is now activated by default in Geth.<\/p>\n <\/p>\n As is customary, ensure to retrieve the latest version<\/a> of Geth!<\/p>\n <\/p>\n <\/p>\n Authored by Holger Drewes<\/em><\/p>\n <\/p>\n In Q2, we substantially expanded our team with three new members joining to focus on the EthereumJS libraries – Andrew, Emmett, and Gabriel. Our efforts concentrated mainly on preparing EIP-1559 for release and generally ensuring our libraries were ready for the London HF. The most recent series of releases<\/a> (VM v5.5.0, Tx v3.3.0, among others) from early July now includes finalized London support encompassing all hardfork block numbers and is primed to transmit EIP-1559 style transactions over the wire.<\/p>\n <\/p>\n The update to the 1559 transaction library incorporated numerous community suggestions and feedback, and we took this opportunity to assess the usability of the library closely. As a result, we improved much of the documentation and instituted several significant usability enhancements, which should make the library more user-friendly. We also aligned with the recent broader trend of Ethereum activity shifting <\/p>\n And it’s worth mentioning this once more: although the release<\/a> itself occurred some time ago (late April), extensive live testing throughout our EthereumJS client development has led to the devp2p library finally being ready for use in production. We are excited to explore your use cases while delving deeper into the Ethereum devp2p networking stack.<\/p>\n <\/p>\n Looking ahead: we have recently combined our initial PR<\/a> on \u201cThe Merge,\u201d enabling our client some initial interaction with an Eth 2.0 PoS client via RPC. This is expected to be followed by significant additional work, which will become a primary focus for the upcoming quarter.<\/p>\n <\/p>\n <\/p>\n Authored by Thore Hildebrandt<\/em><\/p>\n <\/p>\n The Privacy & Scaling Investigations team aims to connect advanced research in zero-knowledge proofs with application development on Ethereum.<\/p>\n <\/p>\n <\/p>\n The objective of zkEVM is to execute smart contracts within a zk-rollup. Unfortunately, the EVM was not crafted to operate in a zk circuit, which presents a challenge. Initiatives like zksync approach this issue by recompiling to an alternative virtual machine. Our intention is to incorporate the entire set of EVM opcodes directly into zk circuits so that a smart contract deployed on L1 can seamlessly transition to L2 with minimal alterations. This will ensure complete compatibility with existing tools and enable us to utilize the EVM insights that the ecosystem has developed over preceding years.<\/p>\n <\/p>\n Over the last few months, we have assembled a team, resolved many of the challenging research issues, and are in the midst of designing and constructing the initial prototypes.<\/p>\n <\/p>\n We have outlined two snarks to verify the validity of EVM computations: a state proof and an EVM proof. The former safeguards the read-write consistency of the stack, memory, and storage, while the latter confirms execution integrity of opcodes.<\/p>\n <\/p>\n We have defined a method for performing common arithmetic on 256-bit words within the circuit. Basic EVM opcodes have been specified and are in the implementation phase. Test cases for observing EVM execution have been established, and we are currently developing a protocol for cross-contract message calls.<\/p>\n <\/p>\n <\/p>\n In September 2019, we initiated the Perpetual Powers of Tau<\/a> ceremony (PPOT). The purpose of PPOT is to support the zero-knowledge ecosystem, particularly zk-SNARK projects established on Ethereum, by partially alleviating the demands of trusted setup ceremonies. Numerous zk-SNARK initiatives necessitate two phases of parameter generation, and PPOT replaces the initial phase, which can be utilized by all circuits. Individual teams can select any contribution from the ceremony to develop their own phase-2 setup.<\/p>\n <\/p>\n This ceremony accommodates circuits with up to 2 ^ 28 constraints, meaning each contribution necessitates a 97G download, a single day of computation, and a 49G upload. As of this writing, we have accumulated 71 contributions, and all contribution files are available for download and can be independently verified against a public ceremony transcript<\/a>.<\/p>\n <\/p>\n Projects intending to utilize or that have utilized the ceremony consist of tornado.cash<\/a>, Semaphore<\/a>, Hermez<\/a>, MACI<\/a>, and zkopru<\/a>. The simplest way to contribute is to contact Wei Jie via Telegram @weijiek. Tune into this podcast<\/a> to hear Wei Jie discuss the ceremony.<\/p>\n <\/p>\n <\/p>\n The objective of a trusted setup is to securely generate zk-SNARK parameters. Provided that at least one party in the ceremony acts honestly and remains uncompromised, the entire setup is reliable. The computation can be divided into two phases. In the initial phase (see Perpetual Powers of Tau<\/a>), participants continuously produce powers of a secret (tau). In the second phase, participants take the output from the first phase and apply it to a specific circuit. Projects that aim to carry out a trusted setup can diminish their workload as only the (circuit-specific) second phase is required.<\/p>\n <\/p>\n Our ambition with the MPC Phase 2 UI project was to facilitate an easy, user-friendly public phase 2 trusted setup for projects without requiring them to develop their own infrastructure. We successfully conducted a ceremony for zkopru<\/a> using the first version of the UI and incorporated experiences from this process in the most recent release<\/a>. If you wish to learn more, please check out the repository<\/a> and join our Telegram channel<\/a>.<\/p>\n <\/p>\n <\/p>\n Optimistic Rollups (OR) enable enhancedlayer 2 scalability through the utilization of on-chain data accessibility and fraud proofs. Hubble enables the development of optimistic rollup chains with a consistent interface, allowing users to enter the rollup ecosystem once and seamlessly transition between chains with minimal costs, effectively eliminating the need to “exit” the low-cost rollup environment.<\/p>\n <\/p>\n Key characteristics encompass mass migrations and a worldwide account registry. Burn auctions will be implemented to decentralize the coordinator and to allocate MEV to CLR\u2019s. Transfers to fresh accounts can be executed directly from L2 without the necessity to deposit on L1. With the aid of BLS signatures, the team accomplished ~2700 tps<\/a>. The Hubble BLS wallet aspires to accommodate additional OR\u2019s like Arbitrum, Optimism, and Fuel.<\/p>\n <\/p>\n Hubble’s code is accessible on Github<\/a>. We have a stable devnet operational<\/a>, having finalized database tasks and multi-token transaction pool. The upcoming step involves refining clients, with a testnet launch aimed for the near future.<\/p>\n <\/p>\n <\/p>\n Zkopru (zk-optimistic-rollup) serves as a layer-2 scaling solution for confidential transactions through zk-SNARK and optimistic rollup technology. It facilitates private transfers and atomic swaps within the layer-2 network among ETH, ERC20, and ERC721 at a low cost. Additionally, it offers immediate withdrawals featuring pay-in-advance options and compliance compatibility through spending keys and viewing keys. Wanseob demonstrated<\/a> the system at the zk-summit. <\/p>\n <\/p>\n Blind Find<\/a> is a peer-to-peer network enabling users to locate others without disclosing their identity. After a successful search, users can verify the existence of the search path within the network through an MPC-based construction, without revealing the path itself. The v1.5<\/a> search protocol is now operational.<\/p>\n <\/p>\n For the upcoming edition of Blind Find, we are shifting our focus to develop a privacy-preserving reputation system in a peer-to-peer network, based on EigenTrust<\/a>. To find out more and engage in discussions, please join the telegram group<\/a>.<\/p>\n <\/p>\n <\/p>\n UniRep<\/a> is a confidential and non-repudiable reputation system. Users have the ability to receive both positive and negative reputation from validators and voluntarily prove they possess a minimum level of reputation without disclosing the exact amount. Additionally, users cannot decline to accept reputation from a validator. We are utilizing Unire to construct Unirep Social<\/a>: a reddit-like platform that permits users to privately amass karma.<\/p>\n <\/p>\n We have finalized the core functionalities in Unirep and Unirep Social, and have commenced building and designing the Unirep Social frontend. Future steps include establishing a website and deploying Unirep on the testnet.<\/p>\n <\/p>\n Join the telegram channel<\/a> to discover more and engage in discussions!<\/p>\n <\/p>\n <\/p>\n The initiative seeks to enhance layer 2 transaction expenses through a smart contract wallet. Smart contract wallets provide users with additional security mechanisms independent of any wallet user interface they may utilize, yet deploying (and using) them on Ethereum’s layer 1 is costly. Layer 2 solutions such as Optimism and Arbitrum significantly reduce this cost barrier, enabling additional users to take advantage of smart contract wallets. This majorly results from these being general-purpose computational solutions. DApps transitioned to layer 2 will be more efficient than those confined to layer 1 due to quicker transactions at lower costs, in addition to further gas savings for both DApps and users. We utilize BLS signatures to decrease on-chain storage, potentially increasing throughput to ~3000 tps. You can monitor the project’s current progress on Github<\/a>. The next steps involve deploying to optimistic-kovan and assessing gas costs\/estimation alongside social recovery functionality.<\/p>\n <\/p>\n <\/p>\n The objective of the project is to facilitate any community in conducting their own CLR round using clr.fund. We have paused some pending tasks<\/a> to concentrate on a clr.fund instance for cryptorelief. We encountered some scaling limits with that instance, thus redirected our focus to upgrading clr.fund’s core contracts to incorporate new x32 MACI circuits and MACI 0.9.4. Part of clr.fund-deployer\u2019s commitment is to facilitate the seamless rollout of the clr.fund application, which drove our participation in recent efforts to merge selected features from the ETH2 clr.fund instance\u2019s app into the primary clr.fund front end. <\/p>\n <\/p>\n Reputation serves as the foundation of trust. Individuals invest years in cultivating their reputation on centralized social platforms, yet they must start from scratch when they switch to a different application. InterRep seeks to render reputation transferable, thereby amplifying the compounding advantages of dependable human interactions across the internet. Explore this article<\/a> for the initial announcement. We are in the process of developing the project’s next phase.<\/p>\n <\/p>\n <\/p>\n <\/p>\n We have examined how the data footprint of a rollup can be further minimized for the airdrop scenario. We used Reddit\u2019s airdrop as a reference. Check our article<\/a> for additional details.<\/p>\n <\/p>\n <\/p>\n We are executing a series of security evaluations on EVM Optimistic rollups, starting with Optimism. The review is now complete and will be accessible shortly; in the meantime, we have published this descriptive article<\/a> about the system. The review for Arbitrum is currently underway.<\/p>\n <\/p>\n <\/p>\n Initially suggested by Vitalik Buterin in an ethresear.ch article<\/a>, frameworks constructed with MACI<\/a> complicate collusion among participants while maintaining the advantages of censorship resistance and accurate execution provided by smart contracts. Although MACI can offer collusion resistance only if the coordinator acts honestly, an untrustworthy coordinator cannot censor nor interfere with its execution. Watch Wei Jie describe how MACI functions on Youtube<\/a>. You can utilize the MACI command-line interface<\/a> to conduct a demonstration.<\/p>\n <\/p>\n The team has reached a significant milestone (version 1.0 of the smart contracts and zero-knowledge circuits), and we are finalizing comprehensive test suites. Additionally, we have begun collaborating with an auditor to challenge the security and functional assumptions of the framework. We are still closely partnering with the EF team working on an ETH2 funding round and a Covid relief funding round. Furthermore, we have initiated development on an extra feature that enables negative voting.<\/p>\n <\/p>\n Join the Telegram group<\/a> to discover more and participate in discussions.<\/p>\n <\/p>\n <\/p>\n Written by Rob Stupay<\/em><\/p>\n <\/p>\n During Q2, Remix focused on enhancing its ability to collaborate with other tools within the ecosystem.<\/p>\n <\/p>\n Discover more in our article<\/a>.<\/p>\n <\/p>\n <\/p>\n <\/p>\n Written by Grant Wuerker<\/em><\/p>\n <\/p>\n Previously, Fe development concentrated on facilitating the necessary features to compile specific demo contracts, with the most developed demo being the Uniswap V2 core contracts. In Q2 of 2021, the development focus shifted from demos to preparing for a release that can be safely utilized in production (i.e., MVP release). We intend to produce an MVP release by the year\u2019s end.<\/p>\n <\/p>\n Below are some notable development progress from Q2:<\/p>\n <\/p>\n <\/li>\n <\/p>\n <\/p>\n Written by Keri Clowes<\/em><\/p>\n <\/p>\n In Q2, the primary focus of the web3py team has been ensuring compatibility with EIP-1559 and supporting asynchronous JSON-RPC calls. Async work will continue into Q3. Documentation was also prioritized in Q2, with numerous clarifications and examples added from frequently asked questions.<\/p>\n <\/p>\n <\/p>\n Written by Piper Merriam<\/em><\/p>\n <\/p>\n The Stateless Ethereum initiative is ongoing. Over recent months, we have addressed the remaining roadmap elements required to achieve the ultimate goal of protocol-level support for stateless block execution.<\/p>\n <\/p>\n The Verkle Trie<\/span> represents a new data structure for retaining the Ethereum state that mitigates the challenges of reducing block witnesses to a manageable size. Our strategy for \u201cState Expiry\u201d provides a streamlined and straightforward approach to transition the existing hexary Patricia trie to the new Verkle trie format. This will also address the \u201cstate rent\u201d dilemma<\/em>, <\/p>\n The verkle trie transition also streamlines the method of setting fiscal limits on the dimensions of block witnesses, a task that was notably more challenging with the hexary patricia trie. The final significant component that requires resolution is how to implement \u201cAddress Space Extension\u201d commonly referred to as ASE.<\/p>\n <\/p>\n These elements encompass all that is necessary to facilitate stateless block execution within our protocol, but perhaps more crucially, they are important enhancements to our protocol that rectify numerous persistent and challenging issues.<\/p>\n <\/p>\n <\/p>\n Written by Martin Holst Swende<\/em><\/p>\n <\/p>\n The second quarter predominantly revolved around the London hardfork, the execution of EIP 1559, and cross-client evaluations. An exploitable vulnerability was discovered<\/a> within the specification that could result in maliciously inflated transactions\/blocks. Erigon has also been incorporated into the fuzzing framework.<\/p>\n <\/p>\n The Hive testing framework detected problems within the ENR compatibility between Besu and other clients, leading to ENR exchanges failing.<\/p>\n <\/p>\n <\/p>\n Written by Franziska Heintel<\/em><\/p>\n <\/p>\n In the second quarter, we launched Solidity versions 0.8.4., 0.8.5, 0.8.6, and 0.8.7:<\/p>\n <\/p>\n <\/p>\n Additionally, the optimizer documentation<\/a> section has been enriched with further content and we clarified the soliditylang.org domain umbrella and the whereabouts of binaries on the blog<\/a>.<\/p>\n <\/p>\n Several members of the Solidity team delivered presentations at EthCC. You can view their lectures on YouTube:<\/p>\n Finally, we are in search of a new team member<\/a>! Please connect with us if you are a C++ engineer interested in developing and managing the Solidity language and compiler and participating in discussions and decisions regarding language design!<\/p>\n <\/p>\n <\/p>\n Written by Thibaut Schaeffer<\/em><\/p>\n <\/p>\n This quarter, the ZoKrates team achieved advancements on all fronts.<\/p>\n <\/p>\n <\/p>\n Regarding language functionalities, ZoKrates has enhanced support for constant generics, user-defined, and low-level constants. This facilitates clearer code that operates across a variety of inputs, proof systems, and curves. The u64 type has also been introduced.<\/p>\n <\/p>\n <\/p>\n Runtime efficiency has been boosted due to less expensive conditionals and random array access as well as optimized comparison evaluations. These changes result in fewer generated constraints, thereby decreasing the costs associated with proof generation. Furthermore, an optional branch isolation feature has been added to simulate short circuiting during execution.<\/p>\n <\/p>\n <\/p>\n The standard library has received enhancements to include the SHA3 family of hash functions, along with the SNARK-friendly Poseidon hash function. Another significant enhancement is the support for recursive proof composition.<\/p>\n <\/p>\n <\/p>\n Lastly, ZoKrates now accommodates the Marlin universal SNARK as a target, which minimizes trust requirements to a sole trusted setup phase.<\/p>\n <\/p>\n For a complete overview of the modifications, please check the changelog<\/a><\/p>\n<\/div>\nEcosystem Support Program<\/h2>\n
Office hours<\/h3>\n
Path to Devcon Grants<\/h3>\n
Eth2 Research<\/h2>\n
\n<\/p>\nEthereum.org<\/h2>\n
Content updates<\/h3>\n
CLR funding round for Eth2 projects<\/h3>\n
Translation Program<\/h3>\n
\n“`have become a bit outdated. We will be making an effort in Q3 to refresh over 20 of our translations to align with the latest versions of our website content.<\/p>\n
\n<\/p>\nWhat do you think of that?<\/h3>\n
Ipsilon (formerly Ewasm)<\/h2>\n
EVM Object Format (EOF)<\/h3>\n
Address Space Extension (ASE)<\/h3>\n
\n#1<\/a>, #2<\/a>, and #3<\/a>).<\/p>\nAdditional research<\/h3>\n
EVMC<\/h3>\n
\n
\n<\/p>\n\n
\n<\/p>\n\n
evmone<\/h3>\n
\n
\n<\/p>\n\n
\n<\/p>\n\n
Formal Verification<\/h2>\n
Act<\/h3>\n
\n
hevm<\/h3>\n
\n
SMTChecker<\/h3>\n
\n
Geth<\/h2>\n
Javascript Team<\/h2>\n
\n“`to side chains and L2, and our transaction library is now more equipped to send transactions to networks such as Arbitrum, Polygon, or xDaiChain. For further information, please refer to the tx README<\/a>.<\/p>\nPrivacy & Scaling Investigations<\/h2>\n
zkEVM<\/h3>\n
Perpetual Powers of Tau<\/h3>\n
MPC Phase 2 UI<\/h3>\n
Hubble<\/h3>\n
Zkopru<\/h3>\n
\nWe have successfully completed a trusted setup<\/a> for the initiative (one of the largest ever conducted). Furthermore, we finalized an audit with Least Authority and are undergoing a second audit. Within the next couple of weeks we anticipate launching Zkopru<\/a> on the public testnet, and, if everything proceeds smoothly, also on the mainnet. Stay tuned for updates via our medium blog<\/a> and join the telegram group<\/a>.<\/p>\nBlind Find<\/h3>\n
Unirep & Unirep Social<\/h3>\n
BLS Sig Aggregation<\/h3>\n
CLR.fund for Everyone<\/h3>\n
\nOur next focus is to organize trusted ceremonies for the new x32 circuits, finalize the clr.fund subgraph, and initiate the next round of“`html
\nclr.fund. Explore the initiative on Github<\/a>.<\/p>\nInterRep<\/h3>\n
Research<\/h3>\n
Rollup Diff Compression<\/h4>\n
EVM Rollup Reviews<\/h4>\n
MACI<\/h3>\n
Remix<\/h2>\n
Snake Charmers [Python Ecosystem: PyEVM\/Trinity\/Web3.py\/Fe]<\/h2>\n
Fe-lang<\/h3>\n
\n
\n
\n<\/li>\n
\n<\/p>\n\n
\n
\n<\/li>\n
\n
\n<\/li>\n
\n
\n<\/li>\n<\/ul>\nWeb3py<\/h3>\n
Stateless Ethereum<\/h2>\n
\n“`establishing fiscal limits on the overall state size.<\/p>\nSecurity [Security \/ Consensus Evaluations]<\/h2>\n
Solidity<\/h2>\n
\n
\n<\/p>\nZoKrates<\/h2>\n
Language<\/h3>\n
Runtime<\/h3>\n
Standard Library<\/h3>\n
Targets<\/h3>\n