Run a DIG node
Serve content provably and provider-blind — you only ever touch indistinguishable ciphertext keyed by hashes, can attest faithful serving with execution proofs, and the client verifies everything against the chain, so trust never rests on your node.
A dig-node is the DIG Network's content server — the supply side of the network. It hosts capsules, keeps a local .dig cache, and exposes the dig RPC so anything that reads DIG content can read it from you. It runs headless (no browser, no UI) as a background service — a seedbox for the content you publish or want to help serve.
It is the counterpart to the consumers — the DIG Browser and the browser extension — which fetch ciphertext + proofs, verify against the on-chain root, decrypt locally, and render. You do not need a dig-node to read DIG content: a consumer alone works fine, falling back to the public reference node at rpc.dig.net. You run a dig-node to serve — and when one is present on the same machine, the consumer reads from it (local, offline-friendly, and contributing to the network) and they share one .dig cache.
- dig-node = serves content + exposes the dig RPC. Headless background service.
- DIG Browser / extension = consume content (verify + decrypt locally). No local node required.
When both are installed, the browser/extension read from your local dig-node; otherwise they read from rpc.dig.net. Either way every byte is verified client-side against the chain — the source is never trusted.
Install it
| Your machine | Use |
|---|---|
| Ubuntu / Debian | The native apt repository — apt install dig-node digstore, auto-enabled as a systemd service. |
| Windows / macOS / Linux (any) | The cross-platform universal installer — one curl | sh (or download) for every OS. |
Both install the same dig-node service plus the digstore CLI. apt is the Debian-native path (signed, apt upgrade-able); the universal installer covers everything else.
apt (Ubuntu / Debian) — recommended on Debian-family systems
The native path: a signed apt repository at apt.dig.net. It installs dig-node as a managed systemd service and keeps it updated with apt upgrade.
→ Install on Ubuntu/Debian via apt
Universal installer (any OS)
The cross-platform path — Windows, macOS, and any Linux. It detects your OS, installs the dig-node service (Windows service / systemd / launchd) and the digstore CLI, and needs no package manager:
curl -fsSL https://dig.net/install.sh | sh
This is the same self-contained dig-installer shipped on the Releases page — download and run it directly if you prefer not to pipe to a shell, or on Windows.
The hosted installers (apt.dig.net, dig.net/install.sh) are still being provisioned. Until they're live, build from source or grab a binary from the dig-node Releases. The commands here are the real, intended ones.
Just want to read content?
You don't need a node. Get the DIG Browser ↗ and open any chia:// address — it consumes from your local dig-node if you have one, else from rpc.dig.net. See The chia:// protocol.
Related
- Install on Ubuntu/Debian via apt — the Debian-native path + systemd service management
- Install anywhere — the universal installer — Windows / macOS / any Linux +
dig.local - Point a consumer at your node — local-first reads + the shared
.digcache - Configure dig-node — ports, listeners, cache cap, upstream
- Self-host a remote origin —
digstore serve+ dig:// clone/pull/push - Manage your node — the control.* admin RPCs + the My Node UI
- Using the public network RPC — the dig RPC your node speaks, and operating a node on the network
- Installing the CLI —
digstoreon its own (publishing, not serving)
Go deeper: the protocol
- "blind host & decoys" → The dig RPC blind serving model · Node conformance
- "attest faithful serving" → Inclusion vs execution proofs
- "dig:// clone/pull/push" → The §21/§22 remote protocol
- Everything → Protocol deep-dive · Concepts & glossary