On October 24, 2026, Tether announced that 15 industry participants had committed to building and maintaining integrations with its open-source Mining Development Kit (MDK). They are pledges, not confirmation of finished integrations or operational deployments.
The 15 participants span mining hardware and services
Tether's full list names ACME Swisstech, Bitdeer, BITMAIN, Canaan Inc., Elektron Energy, EMCD, F2Pool, Foundry Digital, Heatbit Inc., Luxor Technology, MicroBT, OCEAN (Bitcoin Ocean, LLC), Proto (Block, Inc.), SpiderPool and Stratum V2.
What the toolkit actually connects
Tether introduced MDK on April 27, 2026, as a development framework for mining infrastructure. Its launch paired a JavaScript software development kit with a React user-interface library, giving developers tools for both the operational backend and the screens people use to monitor it. The two layers can run independently.
The bridge to equipment is a software module called a Worker. MDK's documentation describes Workers as translators: each handles a device family's own interface and presents its readings and commands through a common protocol. The central coordination engine, called the Kernel, communicates with Workers rather than speaking directly to each machine. Adding a device type therefore does not require rewriting that central engine.
That distinction becomes useful when a dashboard needs information from different systems. Application developers connect through the SDK and can use an optional application toolkit for dashboards, routing and other interface functions. The documentation describes a Node.js client today, with the protocol designed to accommodate other languages later. Future language support should not be confused with software already supplied.
Why a shared interface matters
The reusable part is the connection between an application and the equipment it manages. MDK's integration guide separates the Worker that understands a device from the application-facing routes that present information or commands to users. Once a compatible Worker exists, other tools using that interface can reuse it instead of creating their own device-specific connection.
Workers also extend beyond physical miners. The integration guide describes connections to mining-pool services and accounting systems. A pool connection can expose status information through the same architecture as a machine connection. That gives a monitoring application a common route to several kinds of operational information, while leaving the underlying equipment and services distinct.
This is an infrastructure story within Bitcoin mining. Readers looking for the underlying network mechanics can consult the guide to proof of work and proof of stake. MDK's practical proposition is narrower: reusable software connections for the systems operators already manage.
The release timetable still points toward testing
Tether associated version 0.11 with Lugano's Plan B Forum on October 23 and 24, 2026. Its announcement used prospective wording, leaving completion unconfirmed.
The project's roadmap provides an important qualification. It describes the 0.x series as development software with interfaces that may change, not a production release. Its October target is closely monitored testing at real sites. Production readiness is targeted for the end of December 2026, with version 1.0 intended to establish stable core interfaces and compatibility commitments.
Those stages answer different questions. A development release gives teams something to integrate and test; a production milestone establishes a different expectation of stability. The roadmap itself says feature scope is decided as development proceeds, so a target date is not a promise that every desired integration will arrive together.
Open code does not settle who controls each function
Hardware makers retain their technology and decide which functions to expose, Tether said. An integration need not unlock every capability.
There is also a separate question of control over MDK itself. Its governance documentation welcomes community contributions but leaves final decisions with the core team. The lead maintainer has final technical authority, while strategic direction and roadmap decisions remain within the project's stated leadership structure. Open source does not mean every contributor has equal decision-making power.
Operating responsibility is another boundary. The security documentation says application teams must provide user authentication on the Gateway path and put access controls around the deployment. A common interface does not automatically supply those protections. That matters when a tool can issue equipment commands as well as display readings.
The next evidence to watch is concrete: which integrations become available, which capabilities they expose, and how operators use them after testing. The announcement does not provide a delivery calendar for each participant. Broader adoption and the balance of control between operators and hardware makers remain unresolved.