teku VS nimbus-eth1

You can try to upgrade it to the latest version https://github.com/ConsenSys/teku/releases/tag/23.3.1 and see if it fixes your issue, but if that doesn't work then you'll probably need to resync your clients.

I discovered a bug in Lodestar that causes it to fail to preserve queued BLS-to-execution messages on shutdown.

Teku: https://github.com/ConsenSys/teku/releases

Consensus Layer client ✅ Teku v22.11.0: https://github.com/ConsenSys/teku/releases/tag/22.11.0 ✅ Lodestar v1.2.2: https://github.com/ChainSafe/lodestar/releases/tag/v1.2.2 🟡 Lighthouse: coming soon 🟡 Nimbus: coming soon ❌ Prysm: advised to switch to other clients

create an issue here? https://github.com/ConsenSys/teku

It's all coming from besu's slow processing of blocks https://github.com/ConsenSys/teku/issues/6205

Teku v22.9.1-RC1 released today

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

https://github.com/status-im/nimbus-eth1 (yes, this is also for eth2, see "About" at top right)

I expect we will see a "merged" client in the future. Nimbus could be the closest of anyone to this vision (nimbus-eth1, nimbus-eth2). Not sure when this will happen though. Anyways, you have to remember -- these are two extremely complicated pieces of software. Just the interface between the two has been developed and tests over the last 18 months. I think there will always need to be serious encapsulation of logic for it to be maintainable.