Content
@
0 reply
0 recast
0 reaction
gakonst
@gakonst
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
2 replies
12 recasts
60 reactions
gakonst
@gakonst
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.
1 reply
0 recast
1 reaction
gakonst
@gakonst
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
1 reply
0 recast
1 reaction
gakonst
@gakonst
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`
1 reply
0 recast
1 reaction
gakonst
@gakonst
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/
1 reply
0 recast
1 reaction
gakonst
@gakonst
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!
1 reply
0 recast
1 reaction
