We are excited to release Reth v0.2.0-beta.1!  🎉🎉🎉

After 9 months and 22 alpha releases, Reth is starting its Beta cycle and preparing for our 1.0 “production-ready” release.

In this thread, we discuss the core features, performance, and stability of Reth Beta.

We are excited to release Reth v0.2.0-beta.1!  🎉🎉🎉

After 9 months and 22 alpha releases, Reth is starting its Beta cycle and preparing for our 1.0 “production-ready” release.

In this thread, we discuss the core features, performance, and stability of Reth Beta.

https://www.paradigm.xyz/2024/03/reth-beta

cto & research partner @paradigm. working with /rust on /ethereum. building /reth and /foundry. https://gakonst.com

Today, we publish cross-platform binaries and Docker containers for syncing a Reth Beta node. This is a breaking change, so if you ran alpha, you will need to resync.

https://github.com/paradigmxyz/reth/releases/tag/v0.2.0-beta.1

or just docker pull

Today, we publish cross-platform binaries and Docker containers for syncing a Reth Beta node. This is a breaking change, so if you ran alpha, you will need to resync.

https://github.com/paradigmxyz/reth/releases/tag/v0.2.0-beta.1

or just docker pull http://ghcr.io/paradigmxyz/reth:v0.2.0-beta.1

We are also releasing alpha 22, which contains patch fixes for the alpha series. All node operators who ran alpha are asked to upgrade; no resync needed, no breaking changes.

https://github.com/paradigmxyz/reth/releases/tag/v0.1.0-alpha.22

And `docker pull

We are also releasing alpha 22, which contains patch fixes for the alpha series. All node operators who ran alpha are asked to upgrade; no resync needed, no breaking changes.

https://github.com/paradigmxyz/reth/releases/tag/v0.1.0-alpha.22

And `docker pull http://ghcr.io/paradigmxyz/reth:v0.1.0-alpha.22`

The Reth Book is up to date and ready to answer all your questions about building, syncing, and operating a node.

Please reach out to us with areas that should be more heavily documented.

Documentation is a top priority for us.

The Reth Book is up to date and ready to answer all your questions about building, syncing, and operating a node.

Please reach out to us with areas that should be more heavily documented.

Documentation is a top priority for us.

https://paradigmxyz.github.io/reth/

So what did we do?

TL;DR:
1. Cancun-ready & OP Stack Ecotone ready
2. 100-200 MGas/s at tip, 1-2K MGas/s historical sync
3. 2TB Archive & 1TB Full nodes.
4. <50hrs sync
5. Killer RPC performance
6. Road to 1.0, audit's on.
7. Feature-complete JSON RPC
8. Broke the DB, resync!

Metrics:
* >240 contributors. Thanks for working with us. This is why we're doing this.
* Almost 3K stars on https://github.com/paradigmxyz/reth. Thanks for the support!
* Reth is found in 2-3% of Ethereum nodes. We hope this number goes up with this beta release.

We are often asked "How many TPS can Reth do?"

Reth benches to 1-2K MGas/s on backfill, and 100-200MGas/s on live frontfill (Ethereum L1 workload).

For average 100K gas/tx:
>10K TPS for historical sync.
>1K TPS for live sync.

Rollups yay!

Thanks MegaETH Labs for the numbers!

Historical sync numbers represent pure execution time during "backfills", not including senders recovery or merklization.

This is not representative of the load at tip, it is impt for bootstrapping archive nodes quickly and for catching up to the chain between node restarts.

Live sync numbers are based on recent Ethereum blocks, doing senders recovery, execution and merklization. Interestingly enough, the Merkle Patricia Trie takes >80% of time.

This means that there is still a lot of room for improvement on our performance at the tip!

Sync time for Ethereum mainnet is <50hrs, and we think we can get to <40hrs. SOTA!

Our Static Files & ETL projects got us back down to ~2TB archive node. SOTA!

Full node is at 1TB. We have another ~100GB to get rid of, Geth/NM are better here.

https://github.com/paradigmxyz/reth/pull/6444

RPC Performance is SOTA, benched using Cryo. More improvements coming. This is a point in time measurement and we are excited for all clients to get better over time, we are excited to keep pushing these numbers together.

"When prod-ready 1.0?"

By end of Q2!

Audits are underway.

Full section from the post below, as this is very important.

Here's the full post again:
https://www.paradigm.xyz/2024/03/reth-beta

The Reth team's tireless work and discipline is really inspiring. A privilege to be working together. Only possible bc of them.

S/o to EF Devops, true gurus, showing us how to do serious infrastructure security.

TY to all the bleeding edge node testers, & @achal for graphics!

Thanks to @karalabe.eth for feedback and nuance to the post, as well as @rozmej for a great discussion on tracing and logs performance. Excited for more optimizations on low hanging fruit areas of clients leveraging our benchmarks. More soon, we're just scratching the surface.

What's next?

CANCUN! The Blobs are coming!

Beta releases with more perf and OP Stack stability.

The Reth "SDK" is just getting started.

Reach out to georgios at paradigm dot xyz, we want to work with the best people.

Until then, see you on Github.

What's next?

CANCUN! The Blobs are coming!

Beta releases with more perf and OP Stack stability.

The Reth "SDK" is just getting started.

Reach out to georgios at paradigm dot xyz, we want to work with the best people.

Until then, see you on Github.

https://github.com/paradigmxyz/reth

x-posted on twitter https://twitter.com/gakonst/status/1767238715397861779

In the nine months since the alpha.1 release, we have worked tirelessly day and night to bring you a feature-complete, blazing-fast, and stable node.

Today, we are beyond excited to share our progress.