Glossary
Learn the MDK vocabulary for Kernel, Gateway, Workers, managers, things, and mocks
This page provides explanations for terms that new users may not be familiar with.
Stack and hardware terms
This section explains the terms you need to familiarize yourself with, using an Antminer rack as an example.
| Term | What it is | Lives at |
|---|---|---|
| Kernel (Orchestration Kernel) | The pull-only kernel that owns the device registry, routes commands, and pulls telemetry on its own cadence — it performs no aggregation itself | backend/core/kernel/ |
| Gateway | The developer-owned HTTP entry point between non-Node clients (UI) and Kernel. Required for browser and HTTP consumers; AI agents reach Kernel through the standalone MCP server instead. Not used in the in-process Antminer-rack example below | backend/core/gateway/ |
| Worker | A device-family translator. Speaks the MDK Protocol upward to Kernel and the vendor's native API downward to one device family (one miner brand, one container type, one pool API). | backend/workers/ |
| Worker Plugin | The executable device integration: mdk-contract.json plus its handler files, loaded from a package directory by WorkerRuntimeV2 | backend/workers/miners/avalon/plugin/index.js |
| Worker contract | The declarative mdk-contract.json alone, as read, validated, published, rendered, or queried | backend/workers/miners/avalon/plugin/mdk-contract.json |
| Driver class | The JavaScript class a Worker exports, one per device family (for example AvalonMiner), not one per model. Drives every device that Worker registers. | backend/workers/miners/avalon/lib/avalon.miner.js |
| Thing | Deprecated: one registered device instance on the legacy store services surface. Created by sending a registerThing command to the Worker's provisioning service, not by calling a driver-class method directly. Identified by a generated deviceId. A WorkerRuntimeV2 Worker has no Things: its device list is fixed at construction. | backend/core/mdk/lib/services/provisioning.service.js |
| MCP (Model Context Protocol) | The protocol AI agents use to discover and call tools. @tetherto/mdk-mcp runs as its own standalone process, deriving tools from a plugin's routes; the Gateway hosts no MCP itself | backend/core/mcp/ |
| HyperDHT | The peer-to-peer network HRPC rides on. Every Kernel, Worker, Gateway and client starts a HyperDHT node in every deployment shape, so each process needs outbound UDP to the bootstrap nodes | hyperdht |
| Bootstrap nodes | The well-known peers a HyperDHT node contacts on start to join the network. The public set is the default; a private DHT network supplies its own bootstrap list to each component | backend/core/mdk/README.md |
| Discovery mode | How Kernel first learns a Worker's RPC key: in-process registration, a shared directory on one machine, or a DHT topic. The transport is the same HRPC in all three | backend/workers/docs/architecture.md |
| Discovery topic | A 32-byte hex rendezvous value Kernel and Workers join in DHT mode so Kernel can find them. It is deployment configuration, not a credential: admission is the Kernel's discovery.workerKeys list | backend/core/kernel/README.md |
| READY | The Worker registry state reached once Kernel has the Worker's capability response. It means Kernel can route to the Worker's devices, not that any device answered | backend/core/kernel/README.md |
| HEALTHY, SICK, DEAD | The health states Kernel assigns from health.ping, which the Worker process answers from memory. DEAD stops command routing and nothing else. None of the three describes a device; the control plane explains where device liveness lives | backend/core/kernel/README.md |
How they compose, for an Antminer rack
The same shape repeats for every other device family (Whatsminer, container vendors, pool APIs). Scalability covers the multi-Worker view, parallel Workers, and multi-site deployments.
Hyperswarm RPC
MDK uses @hyperswarm/rpc as its runtime transport. Hyperswarm RPC (HRPC) is not an HTTP-based RPC system. It is an RPC layer
that rides on Hyperswarm peer-to-peer connectivity. The library is a simple RPC over the Hyperswarm DHT, backed by Protomux. Think of it as a peer-to-peer
remote function call system built on a DHT and an encrypted connection layer.
Mental model — Hyperswarm finds peers and establishes connections; Protomux divides the connection into named channels;
RPC defines the conversation — a caller names a method and receives a reply.
A useful analogy is a phone call between peers — Hyperswarm helps the phones find each other and connect; Protomux splits
the line into channels; RPC defines how one side asks for a method and the other side responds.
Practical implications:
- A caller must hold or discover the callee's public key before connecting; there is no HTTP URL to open in a browser
- You work with services, methods, requests, and responses — not URLs and routes
- The RPC-shaped API is identical across same-process, same-host, and distributed deployments; only the discovery mechanism changes (same-process registration, shared directory, or DHT topic)
- Peers discover and communicate without a central HTTP server
HRPC uses Noise to encrypt connections and authenticate peers by key, so these backend connections do not require TLS certificates. It does not expose an HTTP listening endpoint for each peer. HyperDHT still uses network sockets, so UDP reachability, network policy, and caller allowlists remain part of the deployment. The Gateway's HTTP interface has its own security requirements.
HRPC on the same host
MDK uses HRPC as the single transport across all deployment shapes — same-process, same-host, and distributed. Every component is addressed by its public key, not by a socket path or hostname. The Gateway, a standalone Node.js script, and a remote service all connect the same way:
createMdkClient({ kernelKey: key })The Noise handshake that HRPC performs on every connection authenticates by key, so Kernel's allowlist works identically whether the caller is on the same machine or a remote host.
This is consistent with the broader Holepunch ecosystem philosophy — everything is a peer addressed by public key. When the peer is on the same machine it routes locally over the local network interface; the application code sees no difference. The DHT node still starts and contacts its bootstrap nodes, so a same-host deployment needs that outbound reachability too.
Next steps
- You are ready to run the example in Run a mining site end to end
- Learn more about:
- Multi-process discovery across machines: Worker discovery
- Gateway implementation details, including HTTP routing and plugin registration:
backend/core/gateway/README.md - Building your own Worker for a new device family: the build walkthrough
- The install and run pattern every shipped Worker package follows:
backend/workers/docs/install-pattern.md - Per-device contract details (telemetry units, command shapes, error codes): those live in each Worker's
mdk-contract.json, e.g.backend/workers/miners/avalon/plugin/mdk-contract.json