akula VS besu

Back in November, Artem Vorotnikov (Akula developer) made this tweet:

On a related note, I'm also keeping tabs on Akula, because a Rust-based client is a damn sexy proposition for running a performance-sensitive node 24/7.

It certainly seems it will be remembered as a major success story for open p2p protocols on the global Internet of our time.

A great multitude of developers and enthusiasts belonging or contributing to diverse teams spread across the world: developing, debating, and collaborating for years to arrive at the big event.

And it's all been done very much in the public view:

https://weekinethereumnews.com/

https://hackmd.io/@benjaminion/eth2_news

https://github.com/ethereum/pm

https://www.youtube.com/c/EthereumFoundation/videos

Consensus Clients:

https://github.com/sigp/lighthouse#readme

https://github.com/ChainSafe/lodestar#readme

https://github.com/status-im/nimbus-eth2#readme

https://github.com/prysmaticlabs/prysm#readme

https://github.com/ConsenSys/teku#readme

Execution Clients:

https://github.com/akula-bft/akula#readme

https://github.com/hyperledger/besu#readme

https://github.com/ledgerwatch/erigon#readme

https://github.com/ethereum/go-ethereum#readme

https://github.com/NethermindEth/nethermind#readme

https://github.com/status-im/nimbus-eth1#readme

Akula. Ethereum client written in Rust, based on Erigon client architecture.

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. 😔️