flashbots/mev-geth
stale
significant_divergence
Selected Prefer this fork if your goal is MEV-focused Ethereum infrastructure and you need the added bundle APIs. Prefer upstream if you want current geth maintenance, broad compatibility, and lower operational risk.
scroll-tech/go-ethereum
active
significant_divergence
Choose this fork if you are working on Scroll and want execution-client behavior tailored to its rollup architecture. Do not choose it if you need the broadest upstream geth compatibility or the latest upstream-only changes with minimal fork-specific divergence.
taikoxyz/taiko-geth
active
significant_divergence
Choose this fork if you need a Taiko execution engine with Taiko-specific APIs, genesis, and consensus behavior. Choose upstream go-ethereum if you want a broadly compatible Ethereum client or expect to follow mainline geth closely.
ethereumpow/go-ethereum
stale
significant_divergence
Choose this fork only if you need ETHW/PoW-specific behavior and are willing to accept substantial drift from upstream. If you want current Ethereum client maintenance, broader compatibility, or active security and protocol fixes, upstream `go-ethereum` is the better base.
cheapETH/go-ethereum
stale
significant_divergence
Choose this fork only if you specifically need its old customized behavior or workflow assets. For anything that must track modern Ethereum protocol changes or current geth fixes, upstream is the safer choice.
ubiq/go-ubiq
stale
significant_divergence
Choose this fork if you need Ubiq network compatibility and accept a stale, heavily customized codebase. Choose upstream geth if you need current Ethereum features, active maintenance, or easier long-term upgrades.
Choose this fork if you need a go-ethereum base with searcher-specific execution and API behavior. Choose upstream if you want the latest general-purpose Ethereum client features with less maintenance burden and fewer compatibility surprises.
zsfelfoldi/go-ethereum
stale
significant_divergence
Choose this fork only if you need its legacy/customized historical surface area. For production Ethereum node work, upstream is the better default because this fork is both far behind and structurally very divergent.
XinFinOrg/XDPoSChain
active
significant_divergence
Choose this fork if you need XinFin/XDC-specific functionality and are willing to accept substantial divergence from upstream geth. Prefer upstream if you need broad Ethereum compatibility, faster upstream alignment, or the full default geth API surface.
expanse-org/go-expanse
stale
significant_divergence
Prefer this fork only if you need its chain-specific networking and fork-rule customizations. If you want current geth features, security fixes, and lower maintenance cost, upstream is the safer choice.