erigon

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/h

Not sure what you mean or expect, but pretending - I mean assuming - that is a question in good faith, then for EVMs, I would start with Erigon https://github.com/ledgerwatch/erigon

I believe https://github.com/erthink/libmdbx is the highest-throughput transactional KV store with a Golang binding right now. (It’s the current storage backend for https://github.com/ledgerwatch/erigon, which switches quickly to whatever wacky library is optimally performant at the moment.)

These issues partially solved in the libmdbx (a deeply revised and extended descendant of LMDB). So BoltDB and LMDB affected users may switch to libmdbx as the Erigon (Ethereum implementation) does year ago https://github.com/ledgerwatch/erigon/wiki/Criteria-for-tran... For now this is (relatively) easy since bindings for GoLang, Rust NodeJS/Deno, etc are available and the API is mostly the same in general. --- The ideas that MDBX uses to solve these issues are simple: zero-cost micro-defragmentation, coalescing short GC/freelist records, chunking too long GC/freelist records, LIFO for GC/freelist reclaiming, etc. Many of the ideas mentioned seems simple to implement in BoldDB. However the complete solution is not documented and too complicated (in accordance with the traditions inherited from LMDB ;)