/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

FuelLabs/fuel-core

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:01:12.679Z

3mo ago

FuelLabs/fuel-core

FuelLabs/fuel-core is a large, active Rust full-node implementation of the Fuel v2 protocol. It has a high fork count (2864) and star count (57234), is not archived, and saw recent commits as of 2026-03-14 and 2026-03-29. The repository is structured as a Rust workspace with many crates, binaries, tests, CI, deployment, and documentation assets, which suggests it is a substantial codebase rather than a small library.

Loading tags...

Stars57,234

Forks2,864

Default branchmaster

Last pushed2026-03-29T00:34:15Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

9 of 9 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer this fork only if its removed subsystems and RPC/throughput changes are exactly what you want and you can own the maintenance burden. For most adopters, upstream is the safer choice because it is far more current and actively maintained.

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.

Fork comparison

FateMyName/fuel-core

38/100

stale

significant_divergence

Prefer this fork only if its removed subsystems and RPC/throughput changes are exactly what you want and you can own the maintenance burden. For most adopters, upstream is the safer choice because it is far more current and actively maintained.

Likely purpose

A fork for teams that wanted to harden node behavior, raise P2P limits, and simplify or remove parts of the upstream node stack rather than stay aligned with the mainline release.

Best for

Teams that intentionally want a customized Fuel node runtime; Operators prioritizing consistency and throughput tuning over upstream parity; Engineers willing to own a long-lived fork and merge burden; Users who need removed upstream subsystems to stay out of their deployment

Additional features

RPC consistency behavior that waits for a configurable number of blocks before failing
Increased P2P message limits
Gas price service optimization backported from an older release
Node/runtime cleanup that reduces analysis code and unexpected logs
Protocol or block-production hardening work such as PoA leader lock and block-production error handling
Expands API, schema, or SDK surface area for downstream integrations and generated clients.

Missing features

Upstream has continued active development through March 2026 while this fork last pushed in February 2025
Fetcher and reader components were explicitly removed
Tx status manager and transaction assembly paths appear to have been removed or heavily rewritten
Block aggregator conversion code was removed from the forked history
The fork is far behind upstream, so it likely lacks later CI, dependency, and networking updates from mainline
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.

Strengths

Could suit operators who value stricter RPC consistency over fast failure
May reduce noise and raise throughput tolerance in P2P-heavy environments
Appears to include targeted fixes rather than a broad product rewrite
May be attractive if you need a simpler, narrower node surface area

Risks

Large divergence makes rebasing or merging upstream changes expensive
Stale activity increases security and maintenance risk
Removed subsystems may break integrations that expect upstream node services
Operational behavior may differ enough to complicate debugging and support