5 ms·

Client diversity has improved in recent months, particularly consensus clients: https://clientdiversity.org/ https://clientdiversity.org/

• kkielhofner 4y ago
  For beacon that is definitely better than the last time I looked. However geth is still 75% and relevant to the topic of the merge, roughly 88% of current clients aren't ready for it[0]!!! It will be interesting to see what these numbers look like when the merge actually happens... [0] - https://ethernodes.org/merge https://ethernodes.org/merge
  • michaelsbradley 4y ago
    The maintainers of geth recently published and then flagged (as bugged) the first release that was fully Merge-ready, so it's not really possible that geth operators could be ready at this time. I believe just today the next release was published, fixing the bug in the previous one: https://github.com/ethereum/go-ethereum/releases https://github.com/ethereum/go-ethereum/releases
    • kkielhofner 4y ago
      I covered that debacle in another comment: https://news.ycombinator.com/item?id=32581419 https://news.ycombinator.com/item?id=32581419 As noted there prysm, geth, etc have had their first merge-ready releases less than 48 hours ago (with one "oops" already) I (for one) will be waiting for what I'm sure will be more bugs to shake out in the next several days.
    • pcthrowaway 4y ago
      If geth isn't ready for the merge, how were (formerly) PoW testnets upgraded to PoS already?
      • michaelsbradley 4y ago
        Because geth was ready for those test merges.