reth VS fee-feed

Reth is Paradigm's new modular and blazing-fast implementation of Ethereum. The Reth team has already been using Kurtosis to spin up interop devnets and find bugs (source and bug fix).

A dev building Paradigm's new EL client Reth was able to go from 0 to a full interop devnet in a few hours using the eth2-package and used it to find and fix a bug - all in <24hrs of using Kurtosis.

In this post we will prepare a custom version of Armbian for the Orange Pi 5, prepare the board's storage and run the Reth Ethereum execution client in archive mode.

you can just download it free on github https://github.com/paradigmxyz/reth

We are working on pruning, full node and snapshots, you can track this here: - https://github.com/paradigmxyz/reth/issues/2629 - https://github.com/paradigmxyz/reth/issues/3428

Here is the dockerfile. No Docker Compose provided for a "stack" configured. PRs welcome!

Here's an example of an open issue preventing us from using reth types more broadly in our code: https://github.com/paradigmxyz/reth/issues/853

Ću da pitam vitalika jel ima sitniš 😅 (šalu na stranu čoveka nisam upoznao) Ovo sam ja napisao: https://github.com/bluealloy/revm A radim i na ovome: https://github.com/paradigmxyz/reth

EIP-1559 was a surprise to me in a good way. We had spent so much time imagining what it would look like, probably expecting it to be a bit rough around the edges at first. The adoption numbers at the beginning were not high (still lots of type 0/1 transactions) but the basefee was working like a charm. Props to watchtheburn.com and perema's fee feed, which I used to track the early deployment!