So what is the gas per second on various chains today?
A quick survey shows most chains at <10megagas per second, with Binance's chains leading the charge.
Reth in recent benchmarks does 100-200mgas/s, including senders recovery, execution and merklization on live syncing.
But how can we do better? 1. Vertical scaling: Make each machine faster and more efficient 2. Allow splitting workloads across multiple machines.
In our research, we present 3 vertical scaling methods that will be rolled out in Reth over 2024, which we hope will at least 10x our performance benchmark, enabling us to hit the 1+ gigagas per second mark for rollups.
We also identify ways to go beyond that in the cloud.
JIT / AOT EVM: Reduce the interpreter overhead, and run native code.
We have exciting results to show here in the next weeks.
Parallel EVM: Multi-threading to enable execution of more transactions.
We identify at least two flavors for this, which are different for historical and live sync. We are working with multiple external teams to integrate their approaches in Reth.
The state commitment takes >75% of Reth's live sync time today. Every % point in state root performance gained here matters.
This is the most complex and exciting topic, so I'll just go ahead and share the entire section of the blog here.
I think there's a TON of work to do on the state root, probably the most important problem in crypto performance.
Going beyond a single machine, there's 2 things we're doing: 1. Create great abstractions for spinning up rollups alongside the node. 2. Create great abstractions for splitting the node into multiple machines.
We want to create the Kubernetes moment for serverless crypto infra.
We have a lot of open questions:
How can Reth help with other clients' perf? How do we price the avg -> worst case perf degradation? How do we manage the tension between L1 and L2 potentially diverging?
We don't know the answers, but we want to collaborate with people on them.
We will move the needle on scaling Ethereum.
If you’re excited about contributing to breaking the 1gigagas/s barrier for EVM Rollups, reach out to georgios@paradigm.xyz.
We haven't yet the fundamental limits of what we can do.
Ethereum should reach the efficient frontier of what’s possible before arguing about how we would choose between our values once we’ve hit those limits.
Shipping faster will help Ethereum get there.
Instead of "should we do X or Y?", the answer might be "both."
We can move faster by deciding to evolve the protocol with ambition, and not ossify.
We can do better than N-of-N (5 CL + 5 EL!) clients coming to consensus before new upgrades.
We can level up ACD.
We can allocate more resources to Devops & Testing.
We started @Ithacaxyz to accelerate the frontier, & have raised $20M from @paradigm.
We’ve been collaborating with the developer community on some of crypto's hardest problems. Small teams = big impact. The future of crypto will be built together.
Over the past four years, our team shipped some of the industry’s most used open source tools like Reth & Foundry.
We believe in sustainable open source development for the good of crypto.
We think the stack is ready, and it’s now time to accelerate.
After almost two years of development and a successful audit by Sigma Prime, we are finally releasing Reth 1.0, the first “prod-ready” release of our blazing-fast Ethereum execution client. We invite RPC providers and stakers to run Reth.
To speed up execution by getting rid of the overheads of bytecode interpretation, inspired by well-established technologies like the Java or the WASM JIT.
Reth AlphaNet is a testnet rollup built on OP Stack & OP Reth.
Reth AlphaNet is aimed at experimentation of Ethereum research at the bleeding edge, and comes with 3 EIPs not available anywhere else yet. EIP-3074, EIP-71212, EIP-2537.
These EIPs are built with best-practices in mind, are optimized, and tested. We want to do more of this.
AlphaNet is also built for high performance, and we aim to break through the gigagas per second barrier with it.