technology
MDK Rallies Fresh Mining Pledges Around One Framework
By Roll · Chief of Staff · 25 Oct 2026
Crypto observers followed live updates on October 24 as fifteen mining operators, hardware makers and pools pledged to integrate with an open-source framework aimed at smoother automation across sites.
Fifteen Bitcoin mining operators, hardware makers and pools committed to building integrations for MDK, an open-source framework that gives mining equipment from different vendors one common interface.
The commitments arrived on October 24, 2026, and covered a mix of ASIC manufacturers, pools and operators that will each maintain their own connection point to the system. Hardware names in the group run from Bitmain to Canaan and MicroBT. Pools signed on include Foundry Digital, F2Pool, Luxor Technology, OCEAN, EMCD and SpiderPool. Bitdeer, Proto part of Block Inc., ACME Swisstech, Elektron Energy, Heatbit and Stratum V2 round out the list.
How it works
Each participant will build and keep an MDK Worker, a translation layer that sits between its own hardware, pool or system and the core framework. The Worker turns a company’s existing interface into a shared language that any MDK application can read. Companies decide which functions to expose and keep full control of their original technology without any need to rip and replace. Developers write an app, monitoring tool or AI agent once against MDK rather than coding separate versions for every vendor. The orchestration kernel inside MDK speaks only to the Workers through a common message set known as the MDK Protocol, never touching devices directly. Tether’s own QVAC mining agent already runs on the framework.
MDK hit version 0.11 during a Bitcoin forum held in Lugano, Switzerland, on October 23-24, 2026. A stable 1.0 release remains targeted for the end of the year. The code sits under Apache 2.0 terms, and anyone can already pull the repository, read the docs, test integrations or build new Workers. Public documentation includes a demo setup with mock hardware, a gateway and a dashboard. The project stays open to any manufacturer, pool, operator or developer who wants to join later.
Background
A large mining site often runs thousands of machines that come from several manufacturers, link to several pools and sit under several different management layers. Those layers were never designed to speak the same language, so teams spent repeated cycles rebuilding connections whenever new hardware or software entered the picture.
Why it matters
As more companies stand up and maintain their own Workers, one application gains the ability to reach a wider slice of the overall mining fleet without extra custom work. The result is less duplication and more room for automation features to scale across sites that were previously isolated from one another.
The conversation on the timeline continues to track each fresh integration as the project stretches toward its 1.0 milestone. Shibo and Bark of Doginal Dogs host daily X Spaces on the Crypto Spaces Network.