clientdiversity-org VS besu

Alessandro said it'd be a few days before he can get me a data endpoint, but once that happens I'll have clientdiversity.org updated in a day or 2

Ethereum is the most decentralized transaction ledger in the world, with thousands of nodes distributed across the world, and more client diversity than any other blockchain that I'm aware of:

https://clientdiversity.org/

The move to Proof of Stake has also made solo validation accessible to parties other than large pools.

there are guides on https://clientdiversity.org/

Large number of nodes does not equal decentralization. In Ethereum, like all other networks/countries, power tends to consolidate. All the consensus power is consolidated to 1-2 entities.link Hedera is already far more decentralized.

Apparently that’s the case, yes: https://clientdiversity.org/ though the source says „data might not be 100% accurate“, but I guess it’s sure geth dominance is down.

Execution clients only run GETH. Client diversity isn’t even great per eth foundation: https://clientdiversity.org

10+ separate companies implement the protocol in 10 completely different independent code bases https://clientdiversity.org/

As I said this is the second time I did this "report" and asked for better sources the first time as well. In the end I did my best to find reliable sources, but even back then I really wasn't sure if these numbers are correct. And if you look at https://clientdiversity.org/ there are even two data sources you can choose that really differ... so +1 to the irony of our industry...

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