akula VS lighthouse

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.

Lighthouse — an Ethereum consensus client (written in Rust);

Daily Goerli: A whole lot more detail on the lighthouse db corruption issue I posted about previously. There's a warning that's been quite frequent on my erigon nodes for a while that doesn't seem to have any impact on its performance. I asked if it should be downgraded to INFO here.

According to lighthouse team, the root cause was beacon node waited too long before requesting the payload header. All details here : https://github.com/sigp/lighthouse/issues/4312

Update LH to 4.0.2-rc.0 More info here https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0

Which is not true... full nodes are consuming a lot of CPU now... hot-fix was released, but didn't solve the problem completely: https://github.com/sigp/lighthouse/releases/tag/v4.0.2-rc.0 ... more hot-fixes will be needed

https://github.com/sigp/lighthouse 142 contributors