Discofork
Repository brief

base/node

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:03:53.640Z
3mo ago

base/node

base/node is the official Docker-based repository for running a Base network node. It targets users who want to self-host a node on Base, with support for mainnet and Sepolia and multiple execution clients: reth, geth, and nethermind.

GitHub
Loading tags...
Stars68,661
Forks3,228
Default branchmain
Last pushed2026-03-28T15:29:45Z
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

8 of 8 fork briefs
Selected

Prefer upstream unless you need an archival copy; this fork adds no visible capability and is materially behind on maintenance and client support.

Adopt this fork only if the Docker publish workflow is the main thing you need. For running a current Base node, upstream is the better choice because this fork is far behind and shows no substantive node-side improvements.

Choose upstream unless you specifically need this older snapshot. This fork adds no visible capability, while upstream has continued active maintenance and feature work.

Prefer upstream `base/node` unless you specifically need an old snapshot. This fork adds no visible capabilities and is significantly behind, so adopters would mainly inherit stale behavior and miss recent node/client maintenance.

Prefer upstream unless you specifically need a frozen 2024 snapshot; this fork adds no visible features and is substantially behind on maintenance and compatibility.

Prefer upstream base/node unless you specifically need a frozen 2024 snapshot; this fork adds no visible features and is materially behind on maintenance and client support.

Prefer upstream base/node unless you specifically need this older snapshot. This fork does not show added capabilities, and its age means it likely lags important node/client updates and fixes.

Prefer upstream unless you need this exact snapshot. This fork adds no visible capabilities, is materially behind current upstream maintenance, and is best treated as a stale baseline rather than a differentiated distribution.