xOneRS ships five ways to run a follower besides the plain binary: a Linuxbrew formula, a Helm chart, a Stereum service file, an Eth Docker adapter and a guide for WSL2 on Windows. All of them run a follower only: none of them can enable --mine or load a validator key. All of them are files in the repository; none is published to an upstream package index yet.

For the systemd install and the binary itself, see how to run and verify xOneRS and verifying a release artifact.

How does the Homebrew formula work?

ops/packaging/homebrew/xone.rb is a Linuxbrew formula. It installs the published v0.1.0 release binary, not a source build, pinned to sha256 ade9ac7fa486026f2987f6bceb288cf9c7cadcacd34733c18768519d4b36f0f6, which equals the release's SHA256SUMS line (xone.rb). Nothing else is fetched at install time.

brew install --formula ./ops/packaging/homebrew/xone.rb
  • Linux x86_64 only. No macOS binary is published. PR #1121 (2026-11-15, closes #309) adds ci/release-macos.sh, which builds aarch64-apple-darwin on a macOS arm64 host only, and a checklist in docs/ops/macos-arm64.md; the build, signing and publishing are still to be done on such a host.
  • License GPL-3.0-or-later, as in Cargo.toml.
  • brew test runs xone --version and xone version.
  • The service runs xone --datadir <var>/xone --network apothem.

PR #1036 (merged 2026-11-15) made it so: before, the formula built from the source tarball with no checksum, fetched a Rust toolchain at install time, and named the wrong license. ci/check-formula.sh now guards the pinned sha256, the absence of downloads, the license and the test. brew audit --strict was not run, because brew is not installed on the host where the change was made.

What does the Helm chart deploy?

ops/integrations/helm/xone-follower is a follower-only chart, version 0.1.0, for Kubernetes 1.25 or later (Chart.yaml). From its values file and templates:

  • replicaCount is fixed at 1, so a signer identity can never be duplicated across pods.
  • image.repository and image.tag must be pinned; the template refuses latest.
  • network is apothem or net2040; mainnet is refused as not qualified.
  • RPC is a ClusterIP service on 8545 by default; P2P is 30303, metrics 6060.
  • A 200 GiB volume; requests of 500m CPU and 2 GiB memory, limits of 4 CPUs and 8 GiB.
  • --mine and validator-key flags are refused in the extra flags.

The chart needs an image you build or host yourself; the values name xone:0.1.0 as an example.

What do the Stereum and Eth Docker files do?

  • Stereum (ops/integrations/stereum/xone-follower.yaml): a service definition to import into Stereum. Networks: apothem (default) and net2040; mainnet is refused. Signing modes cannot be selected. The file says that publication to the upstream Stereum project is a separate step.
  • Eth Docker (ops/integrations/eth-docker/xone.yml): an adapter added to Eth Docker's COMPOSE_FILE. XDPoS has no beacon node, so the service stands alone and needs no consensus client. XONE_IMAGE must be a pinned image.

How do I run xOne on Windows?

Inside WSL2, as the Linux binary (docs/ops/wsl2.md). The datadir must be on a Linux filesystem (ext4 inside WSL), not on /mnt/c or another Windows mount: MDBX memory maps and file locks are not reliable on the Windows volume. Do not run a Windows .exe or keep the binary only on C:\. A native Windows build script, ci/release-windows.sh, came with PR #1133 (closes #538); it runs on a Windows host only, and no Windows binary is published.

Which networks can these packages run?

Apothem and net2040, the networks the support matrix lists as qualified for a follower. Mainnet is not qualified, and the Helm chart and the Stereum file refuse it (support matrix).

The collected competitor articles mention packaging by eth-docker, Stereum and Ethereum on ARM for ethrex (six months of ethrex in production, 2026-07-20). xOne's files are in its own repository and not yet published upstream.

Frequently asked questions

Can I install xOne with Homebrew on macOS?

No. The formula is Linux x86_64 only, and no macOS binary is published. A macOS arm64 release script exists (PR #1121); the build must be run on a macOS host.

Does the Homebrew formula build xOne from source?

No. It installs the published v0.1.0 binary, checked against the release's sha256, and fetches nothing else.

Can I run an xOne validator with the Helm chart?

No. The chart is follower-only: one replica, and --mine and validator-key flags are refused.

Where should the datadir be on WSL2?

On the Linux filesystem inside WSL2, not on a Windows drive such as /mnt/c.

Sources