Parity VS besu

What got me interested in learning Rust with Ethereum is Reth (Rust Ethereum Execution Layer Client). OpenEthereum was another Rust client that got deprecated earlier in 2022, which is what I think inspired Reth to be made https://github.com/openethereum/openethereum . It sounds like Reth will go live in January/February 2023 https://github.com/paradigmxyz/reth#status they put out a summary here too https://www.paradigm.xyz/2022/12/reth

OpenEthereum | Programming Language = Rust

OpenEthereum v3.2.0 is ready for Berlin.

It's still maintained https://github.com/openethereum/openethereum

For Ethereum, there is Geth, OpenEthereum, Nethermind, among others.

I'm not sure why this was linked. Parity decided to stop developing their Ethereum client and this repo has been sitting unmaintained for about 2 years now, it will almost certainly not successfully sync with mainnet.

The Parity codebase was taken over by new maintainers and turned into OpenEthereum: https://github.com/openethereum/openethereum

However, writing and maintaining an Ethereum client is an exceptional amount of work with very little benefit, the primary OpenEthereum maintainers recently announced they would stop maintaining OpenEthereum and would start pouring their energies into an upcoming client called Erigon. https://medium.com/openethereum/gnosis-joins-erigon-formerly...

Erigon is a much better client.

Also, the Ethereum Foundation doesn't own a lot of the code used in the network. For example, lots of people use OpenEthereum as their client, which is not managed by EF.

Daily Goerli: I've been testing this PR for besu for the past several days, and the stability of nimbus-besu has improved substantially. Looking forward to it getting merged into main.

Check out the Layered TX pool PR for more details and benchmarks - https://github.com/hyperledger/besu/pull/5290

you can check this spreadsheet for a comparison https://github.com/hyperledger/besu/files/11137473/Layered.Transaction.Pool.metrics.ods

Yes, it's gotten better. I don't recommend pairing with nimbus until this issue gets fixed or prysm until something is done to reduce the amount of time it takes to recover from being offline for a day or more.

Daily Goerli: On Friday, I reported a RocksDB issue that was causing besu to error and exit immediately. The bad commit has been identified and a fix has been issued. lodestar-nethermind somehow ended up on an invalid fork which isn't resolved by restarting either client. Waiting to see how each client team responds and if they need more info, but might need to do a resync.

https://github.com/hyperledger/besu 148 contributors

Download links and release notes here: https://github.com/hyperledger/besu/releases/tag/23.1.2

Now running into this error on my freshly synced Besu 23.1.0. 😔️