Michael JohnsonFifteen mining operators, ASIC manufacturers, and pools have agreed to develop and maintain integrations with the open-source Mining Development Kit (MDK), Tether announced on October 24, 2026. For the industry, this is an attempt to solve a practical problem: connecting diverse hardware and software systems through a shared layer, so applications can work with them through reusable integrations.
At the heart of the architecture are Workers: adapters that translate the interface of a particular piece of equipment, pool, or system into the MDK format. Participants retain their existing technologies and choose which functions to expose through an adapter. With this approach, an application developer needs to integrate with the shared layer rather than with each manufacturer separately.
What was announced
Tether named participants from three groups: mining-site operators, equipment manufacturers, and mining pools. The companies listed include Bitdeer, BITMAIN, Canaan, Foundry Digital, MicroBT, and OCEAN. Their stated contribution is to develop and maintain their own Workers; the announcement does not set a common schedule for adapter readiness or confirm that every adapter is already running in production.
The MDK repository describes it as a Node.js SDK for infrastructure monitoring, device and container management, telemetry collection, and application development. The architecture is divided into a core, Workers, and interface tools; the Gateway connects business logic to the core, which receives data from Workers and sends commands to them. The project also includes an MCP server.
Why mining needs a common interface
A site may run machines from different manufacturers alongside software systems that use separate protocols. Each new integration adds custom development work and makes it harder to monitor the fleet as a whole. A Worker acts as a translator between a specific system and an application: for example, a monitoring tool can use the shared layer, while an adapter converts the request into the interface of the selected equipment.
This structure can support automation whether or not an operator uses AI. A common interface first makes it possible to collect data and send permitted commands consistently; rules or agent-based applications can then be built on top of it. Tether says its QVAC mining agent is already running on MDK. This is an integration the company says it has built, not a published measurement of its effect on energy use, downtime, or mining profitability.
What developers can test now
As of October 24, the repository lists version 0.11.0 and also describes MDK as an actively developed project that is not yet considered stable. To evaluate it in practice, developers can run the demo stack from the repository: the README describes setups with the core, Workers, mock devices, the Gateway API, and an interface. In the demo, Workers use real connection and telemetry pathways but connect to local mocks, and the telemetry values are synthetic. This makes it possible to test the architecture and integration development without evaluating it on real mining hardware.
In its announcement, Tether set late 2026 as the target for releasing a stable 1.0 version. For teams evaluating MDK, a practical next step is to check whether the required Workers are available, determine which commands and data they expose, and separately test resilience on their own hardware. According to the MDK README and repository status, the public API remains under development before version 1.0, so integrations should be planned with possible changes in mind.
The announcement from 15 companies matters primarily as coordination around a shared interface: MDK’s usefulness to operators will depend on how fully participants implement and maintain their adapters. Developers can already explore the code and test architectural scenarios; the promised stable 1.0 release remains a target for the end of the year.