FuelLabs/fuel-core

Prefer upstream unless you specifically need this older fork's p2p/chainspec experiments or are maintaining a legacy deployment. For most adopters, the fork is too stale and too far behind to be a safe default.

Prefer this fork only if you need its custom RPC/P2P and internal rewrites and are prepared to maintain a large divergence. If you want upstream compatibility, active maintenance, and the full set of node subsystems, upstream is the safer choice.

Choose this fork only if you need its older, specialized behavior and are prepared to own long-term maintenance. For most adopters, upstream is the safer default because this fork is materially behind and likely missing newer protocol, CI, and operational fixes.

Choose this fork only if you need its custom behavior and are willing to own a large divergence from upstream. For most adopters, upstream FuelLabs/fuel-core is the safer choice because it is active, current, and much better maintained.

Prefer this fork only if you specifically need its older customizations around importer, P2P, and storage behavior. If you want current Fuel node features, upstream compatibility, or lower maintenance risk, upstream is the better choice.

Choose this fork only if you need its specific historical/custom behavior and are willing to maintain a large divergence from upstream. If you want the current Fuel-core baseline, upstream is the safer choice.

Choose this fork only if you need its custom node behavior and are prepared to own a long-term divergence. If you want a current Fuel node implementation with active upstream support and network compatibility, upstream is the better default.

Choose this fork only for historical continuity or niche refactor archaeology. For production or active development, upstream is clearly the better choice.