Skip to main content

Manage your node

Once a dig-node is running, you operate it through a small set of admin RPCs — separate from the public dig RPC read methods — and, if you use the DIG Browser, through the My Node UI that drives those same RPCs.

The control.* admin RPCs​

The control.* namespace exposes operator actions that are not part of the public read surface (they require local/admin authority), for example:

  • status — health, version, uptime, and the resolved listeners.
  • cache — inspect the .dig cache (capsules held), and prune/evict.
  • peers / upstream — the upstream the node blind-fetches from and any peer state.

These are admin-scoped: a remote reader hitting the public dig RPC can never call them.

The DIG Browser My Node UI​

The DIG Browser ships a My Node view that controls a local dig-node over the control.* RPCs — see its status, watch the shared cache, and manage the service without the command line. → Point a consumer at your node