Welcome to London! This is an exciting time for the Ethereum ecosystem, and the pace will only pick up further as we approach Altair and the Merge in the months ahead. The Beacon Chain now has 6.5+ million Ether staked, and 200K+ active validators online across five clients, and the network is now burning Ether as part of the changes made with the London update. As always, there’s much more progress being made by EF-supported projects and teams that help to improve our Ethereum experience. This roundup series is an opportunity to highlight their efforts to grow and improve Ethereum as a whole.
Included in this edition are updates from many teams highlighted in the previous Supported Teams update, and more. Enjoy!
Ecosystem Support Program
Authored by ESP Team
Road to Devcon
We’re collaborating with the Devcon team on a round of small grants and other support for community event organizers. Organizers of virtual and in-person events can apply directly for grants of $500-1500 to cover costs like space or equipment rental, swag, snacks or other incidentals. Learn more and apply here.
Lee esta página en español; 用中文阅读本页.
We also recently published our Q1 Allocation Update, with details of 47 grants awarded in Q1 totaling $5,341,000.
Beyond the content that makes it into Danny Ryan’s Finalized series, the research team has continued into areas including stateless research, proofs of custody for EVM execution, sharding specs and prototypes, and other scaling/security research. Most of their progress can be found on posts on ethresear.ch. Additionally, find a few of their recent posts and other content below:
Authored by Sam Richards
To make our work more accessible and to foster more community collaboration, our team publishes an overview of our quarterly roadmap goals. See last quarter’s roadmap here: #2849.
Greetings fellow Ethereans! Happy L2 summer 😎 (or winter for our friends in the southern hemisphere)! Hope you’re enjoying your time in this space – we know we are! As always, our vision with ethereum.org is to create the best portal for Ethereum’s growing community, and to serve as the front door to Ethereum for the millions of new visitors each month.
In Q3 our ethereum.org product focus will be to keep pace with all the incredible progress in the space so that our broader community can stay informed on developments on Ethereum network upgrades, Layer 2 projects, developer tooling, user applications and more. Thank you to the hundreds of folks who have contributed content so far ❤️ Learn how to get involved
CLR funding round for Eth2 projects
New funding mechanisms for public goods offer massive potential for the Ethereum ecosystem and the world beyond crypto. While not directly related to ethereum.org, our team is part of the Ethereum Foundation, which is one of the largest funders of grants and public goods within the ecosystem. We want to increase the cultural momentum around ecosystem funding for public goods as well as experiment with mechanisms in which support is allocated to the ecosystem. We’ll continue our work from Q2 with teams in the space, aiming to launch a CLR.fund round for Eth2 projects on an L2 mainnet by the end of Q3. This work will also allow our team to stay on top of the latest tools, technologies, and best practices involved with dapp development, from testing and deployment tools to identity solutions and Layer 2 technologies. We plan to to bring these first-hand insights back into our developer resources. Learn more, follow along & get involved
Thanks to our >1,400 volunteer translators over the past couple years, ethereum.org now supports 35 languages! Yet as the website has grown & is constantly updated to keep pace with the developments in the space, many of our languages have fallen somewhat out of date. We’ll be making a push in Q3 to update 20+ of our translations to more recent versions of our website content. With our new Translation Program Lead, @lukassim, we also plan to improve our supporting documentation & improve use of our translation tools to improve consistency and quality throughout the translation process. Learn how to get involved
As you can see from all our goals above, our success is driven by our open source community of collaborators. Contributors come in many shapes & sizes – translators, developers, copywriters, designers, experts & amateurs. We want to continue to educate & empower folks who are curious to get involved in the Ethereum ecosystem & our ethereum.org community. Our new Community Lead, @minimalsm, will be leading efforts to support & empower our growing ethereum.org community. Stay tuned for the specific initiatives we plan to roll out this quarter! Have ideas? Reach out on our Discord server or here on GitHub.
How does that sound? We appreciate feedback on our roadmap. Our guiding principles are based on delivering the most value in the shortest time, so if there’s something you think we should work on, please let us know! We welcome ideas and PRs from anyone in the community. More on contributing
Ipsilon (previously Ewasm)
Authored by Alex Beregszaszi
The Ewasm team has rebranded to a new name: Ipsilon. It is a reference to the state transition function defined in the Yellow Paper. We want to signal that our work for a long time has been more broad than only Ewasm. The team’s core concern is the execution environment / engine of Ethereum (aka the EVM or any future versions or replacements of it). We provide analysis and implementation of own and third party proposals (i.e. new EIPs proposing changes to the EVM), provide tooling (evmc, evmone, fizzy), and support existing teams (e.g. Solidity, go-ethereum, Silkworm) with implementation and analysis. Most of our content is published here.
EVM Object Format (EOF)
In the previous update we have mentioned the EVM Object Format (EOF) as a new proposal. In the last three months a lot of progress has been made. The first step, EIP-3541, has been accepted into the London update — this only reserves a starting byte which can be used to introduce EOF in a future protocol update. A concrete proposal, EIP-3540, which introduces the container format and code-and-data separation has been published. Furthermore there is an explainer document giving background and a roadmap (this will be updated as we go), and we also gave a PEEPanEIP presentation (video and slides). Both EIP-3541 and EIP-3540 have been implemented in geth and evmone. Lastly, we shared a short proposal to revamp EIP-2938 using EOF and other teams considered building on EOF.
Address Space Extension (ASE)
The second big topic for us has been the address space extension, which is a requirement for the state expiry roadmap. It was first described in an Ethereum Magicians post and various discussions on the Eth R&D discord. Our specification builds on all this prior work and aims to give a coherent overview of how to implement this change. An additional document listing a comprehensive set of test cases was also released. While the core of the proposal is not too complicated, there are many implications. This discussion document is the basis of the ongoing Address Space Extension Working Group, which already had three calls (recordings: #1, #2, and #3).
On the topic of code merkleization / code chunking, we published a thorough analysis of the impact of code chunking costs. The new version of the verkle tree proposal reconsidered costs based on the results. The idea of an MCOPY instruction was prompted by the research on EVM384. We published a short writeup detailing this proposal, providing a pricing, and evaluating the benefits for regular contracts besides the use in EVM384.
EVMC 8.0.0 release
– Berlin support, new callbacks to update global account/storage accessed list.
– 9.0.0 release
– London support and block_base_fee added to transaction context
– evmc run with –bench
evmone 0.7.0 release
– Berlin support
– Optimizations in Baseline interpreter’s jumpdest analysis
– Improvements to the C++ API
– London support and BASEFEE instruction implementation
– Instruction tracing following EIP-3155 format added to Baseline interpreter
– Option to count the number of executed instructions in Baseline interpreter
– More optimizations in Baseline interpreter and in intx and ethash libraries.
– Improvements to benchmarking tools
The Formal Verification Team will post their own updates (covering Act, hevm, SMTChecker and more) here, and in recent months, some of the notes saw improvement as well.