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.
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.
Frog is an open-source framework for @Farcaster_xyz developers to build high quality, performant, & lightweight Frames in just a few blocks of code.
Built as part of the @wevm_dev x @paradigm collab. Read on!
.@Farcaster_xyz’s programmable feed, enabled by Frames, is one of the most exciting things happening in web3. We felt like this deserved a world-class devtool experience.
Wagmi is quickly rising to be the #1 Web3 frontend library. The Wagmi CLI allows blazing-fast iteration on full-stack hackathon projects w/ its Foundry integration.
Excited to be open-sourcing Reth, an Ethereum execution layer in @rustlang 🦀
Reth is a new Apache/MIT-licensed full-node implementation of Ethereum by @paradigm and the community, focused on contributor-friendliness, modularity, and performance.
1. Building a performant node for power users 2. Contributing to Ethereum’s stability by improving client diversity 3. Giving back to Ethereum by contributing to the roadmap
We are building Reth to accommodate a broad user base, including stakers, hobbyists, RPC node operators, bridges, MEV searchers, and even L2s (e.g., Optimism/Arbitrum) or other Ethereum-adjacent projects (e.g., Polygon, BSC, Avalanche, Fantom etc.).
.@paradigm is building Reth, a Rust Ethereum Execution Layer.
Reth is not a fork or a rewrite of any other client implementation.
It is a new Apache/MIT-licensed full node implementation of Ethereum focused on contributor friendliness, modularity, and performance. 1/8
Reth does not include code from any existing client but stands on the shoulders of giants including Geth, Erigon and Akula.
We sponsored the project in the interest of client diversity, so we are sorry to see any other project ceasing development. It is a loss for the space. 2/8
A core goal of Reth is modularity and open-source friendliness.
Every component is built to be used as a library: well-tested, heavily documented and benchmarked.
We envision that developers will import the node's crates, mix and match, and innovate on top of them. 3/8
This time, @a_kirillo and @jneu_net and I teamed up to see if we can bring Narwhal & Bullshark, a novel mempool & consensus algorithm, to the Cosmos ecosystem 🧵 1/18
As more and more blockchain systems get deployed to production, two problems are frequently encountered:
1. Achieving consensus with high throughput and low latency paradigm.xyz/2022/07/consen… (cc @LefKok) 2. Building a distributed application on top of that consensus
Cosmos uses Tendermint (TM), a high-performance BFT consensus algorithm, and the Cosmos SDK, a toolkit which enables developers to launch their own chain on TM.