Tether said on October 24 that 15 firms had committed to build and maintain integrations for its Mining Development Kit, or MDK. The announcement describes prospective participation in mining software development; it does not establish that those integrations are complete or operating at mining sites.
The distinction matters for readers assessing adoption. The available evidence covers a company announcement, project documentation, a simulated mining-site tutorial and release records. As of October 25, 2026, KST, those materials did not establish participant-specific production use.
What the 15 commitments cover
Tether’s announcement names ACME Swisstech, Bitdeer, BITMAIN, Canaan, Elektron Energy, EMCD, F2Pool, Foundry Digital, Heatbit, Luxor, MicroBT, OCEAN, Proto, SpiderPool and Stratum V2. It describes participation spanning mining operators, ASIC manufacturers and pools, without assigning each name to a category.
The stated commitment is to build and maintain integrations. The announcement does not supply individual agreements, delivery deadlines or a participant-by-participant account of completed work. Editorially, the roster indicates potential ecosystem breadth, while leaving the extent of working interoperability unestablished.
For separate infrastructure background, Tether also featured in reporting on Tenstorrent’s AI funding round. That initiative does not verify MDK adoption.
What the software and demo establish
The MDK repository README describes a modular Node.js software development kit for monitoring and controlling mining infrastructure, collecting operational data and building integrations. It also labels the project unfinished and not yet stable. Those descriptions establish its intended functions and published development status, without demonstrating production readiness.
The end-to-end tutorial illustrates how the pieces fit together locally. Its example includes Whatsminer, Ocean pool and power-meter workers, alongside a Gateway API and dashboard. The example runs workers against localhost mock servers rather than physical mining equipment.
That makes the example useful for understanding the documented integration structure. It does not demonstrate a participant-operated mining site. The README also identifies synthetic telemetry in the demo, so its displayed activity cannot serve as evidence of real mining performance.
The reviewed project documentation reports no customer-adoption figures, energy savings, revenue improvements or security results. A documented simulation and a working installation answer different questions: one explains the intended setup, while the other would require evidence from actual equipment and operations.
The version records need clarification
The repository’s release page lists v0.11.0 as latest, with an October 19, 2026, timestamp of 15:31; its timezone is unspecified. Tether’s announcement, however, says MDK would reach v0.11 at the October 23–24 Plan ₿ Forum. Separately, the README identifies v0.12.0 as the current release.
These records do not provide a consistent account of the current version or explain the forum timing. The discrepancy remains unresolved in the reviewed materials. It does not establish that the software is unusable, but it limits how confidently readers can describe its release status. Tether’s year-end 2026 target for a stable 1.0 release remains a company target.
What would demonstrate operational adoption
A useful follow-up would connect named participants to identifiable integrations, release notes and tests involving real equipment. Participant confirmation and documented production use would help distinguish a development commitment from an operating installation.
Claims about efficiency, uptime, energy use or security would require their own measured evidence. Public code and a local example make the project available for inspection; neither supplies those results. For now, the supported conclusion is narrower: Tether reports commitments, while the reviewed materials leave deployment and operational outcomes unverified.
Sources
- Tether: MDK industry-backing announcement — October 24, 2026.
- MDK repository README — undated; accessed October 25, 2026, KST.
- MDK: Run a mining site end to end — undated; accessed October 25, 2026, KST.
- MDK release records — reviewed October 25, 2026, KST.
Investment disclaimer: This article is provided for general information only and does not constitute investment, financial, legal or tax advice. Digital assets are volatile, and all investment decisions and their consequences are your own responsibility.