DIG CLI tools

The DIG Network ships a small suite of command-line tools. Each one owns a distinct job in the publish → serve → read journey, and each has a short, first-class name so it is quick to type:

• digs — the store CLI. Scaffold, preview, and publish content to the DIG Network.
• dign — the node CLI. Run a headless server that hosts content and answers reads.
• digd — the DNS helper. Makes http://<storeId>.dig/ addresses resolve on your machine.

You do not need all three. Pick the tool for what you want to do:

I want to…	Tool	Start here
Publish a site, app, or files to DIG	digs	Install the store CLI
Serve content and run a node	dign	Run a DIG node
Open .dig addresses in a browser	digd	DIG and your DNS

digs — the store CLI

digs is the first-class shorthand for dig-store, the tool that turns a folder into a verifiable, on-chain-anchored DIG capsule and publishes it. digs <args> and dig-store <args> are the same program — identical commands, flags, and --json output — so use whichever you prefer.

Typical flow:

digs new my-app        # scaffold a project from a template — free, no wallet
digs dev               # local preview over the real chia:// read path — free
digs doctor            # pre-publish preflight
digs deploy            # publish (the step that spends DIG)

Deeper docs: installing the CLI · quickstart · full command reference

dign — the node CLI

dign is the first-class shorthand for dig-node, the DIG Network's content server. A node 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 as a background service. dign and dig-node are the same program — the same subcommands (including the service verbs install / start / stop / status / serve), flags, --json output, and exit codes.

You do not need a node to read DIG content — a consumer alone works fine. You run a node to serve, and when one is present the local reader uses it automatically.

dign open chia://<storeId>/   # open an address to confirm serving works
dign status --json            # scriptable health signal

Deeper docs: run a DIG node · manage the service · configure

digd — the DNS helper

digd is the first-class shorthand for dig-dns, a split-DNS resolver that makes .dig addresses (http://<storeId>.dig/) work in an ordinary browser. It claims only the .dig top-level domain and leaves every other name on your system resolving exactly as before — it never becomes your default resolver, never edits /etc/hosts, and never intercepts TLS.

digd doctor            # report which .dig resolution path is live

Deeper docs: DIG and your DNS · point a consumer at a node

Installing the tools

The DIG Installer is the one-stop route: it sets up dig-node, dig-dns, and the chia:// scheme handler, and places all three short aliases — digs, dign, and digd — on your PATH as real installed binaries. Each behaves identically to its full-named primary (dig-store, dig-node, dig-dns).

Prefer to install just one tool?

• Store CLI only — grab the raw dig-store binary or build from source: installing the CLI. The .deb and installer routes also place digs on your PATH.
• Node only — the apt repository installs dig-node on Ubuntu/Debian. The short aliases dign and digd are specific to the DIG Installer route; with the apt or native OS packages, use the full dig-node / dig-dns names.

The short aliases come with the DIG Installer

dign and digd are placed on your PATH by the DIG Installer route only. The apt and native OS packages carry the full-named dig-node and dig-dns binaries instead. digs also ships with the store CLI's own install methods.