Run a node
A provider node contributes your hardware to a mesh. It keeps a persistent identity, reconnects on its own across drops, and attributes Genesis Points to the NEAR account you name.
Desktop app
The all-in-one option: a native menu-bar app that runs your node from a single toggle and bundles the holonear CLI — no terminal or prior setup needed. An Install holonear CLI to PATH button inside the app exposes that same CLI to your shell when you want it, so it's a full alternative to the one-line installer below.
xattr -dr com.apple.quarantine /Applications/HoloNear.app). On Windows, click More info → Run anyway on the SmartScreen prompt.Install the CLI
The holonear CLI is the single entrypoint. On macOS (Apple Silicon), install the prebuilt binary with one line — it downloads and installs to ~/.holonear/bin:
curl -fsSL https://holonear-attestation-production.up.railway.app/install.sh | sh
The interim installer is served from a temporary host and isn't code-signed yet — its checksum only guards against a corrupted download, not a tampered host. Since a node runs with your keys and stake, review the script before piping it to a shell:
curl -fsSL https://holonear-attestation-production.up.railway.app/install.sh -o holonear-install.sh less holonear-install.sh # read it, then: sh holonear-install.sh
Or via npm (once published) — no toolchain needed:
npx holonear --help # run the latest CLI directly npm install -g holonear # …or install it globally
The MLX (Apple Metal) backend ships in the Apple-Silicon build; every other platform gets the pure-CPU build automatically. An NVIDIA CUDA backend also exists (single-GPU verified on real silicon; multi-GPU and Blackwell still in bring-up) and builds from source behind the cuda/cuda-device features.
Prefer Python? Once the wheels are published, pip install holonear gets you the client bindings (built with maturin from crates/holonear-client-py).
Join the pool
Point the node at a coordinator and name your NEAR account (the identity your Genesis Points and Founder # accrue to):
holonear node run \ --coordinator ws://<coordinator-host>:7070 \ --payout your-account.near \ --city "Singapore"
Common flags:
--payout— the NEAR account that receives Genesis attribution (also readsHOLONEAR_NEAR_PAYOUT).--free-mem-gb— free unified memory to advertise; the scheduler uses it to size the shard it gives you. Advertise more than the model's per-stage footprint or you won't be assigned.--city/--chip— self-declared labels for the fleet map (the chip auto-detects if omitted).--attestation—stub(default, self-signed) orself-provisionedto mint a bring-your-own-root device bundle and join at a higher trust tier.
--skip-input to onboard from a single command with no prompts — every input also has an HOLONEAR_* env fallback, so the node comes up under systemd or in a container without a TTY.Show up on the leaderboard
Contribution always accrues to your node, but the public leaderboard attributes it to a proven NEAR account. Your node proves it operates that account with a NEP-413 signature (the owner-proof) — once verified, your contribution rolls up under your account name. See Genesis Points.