Tether Says 15 Companies Commit to Integrating Its MDK Bitcoin Mining Kit

Tether's MDK Draws 15 Commitments

Tether said on Saturday, October 24, that fifteen companies across the Bitcoin mining industry have committed to integrating its open-source Mining Development Kit, known as MDK, a framework that connects mining hardware, mining pools and applications through one shared technical format. The company behind the USDT stablecoin set out the commitments in its official announcement on X, describing the response as broad industry backing for what it calls the next generation of automated mining. The disclosure stops short of naming all fifteen, but Bitmain, MicroBT and Canaan appear on the hardware side, while Bitdeer, Foundry Digital and F2Pool cover hosting and pool operations. Under the arrangement, each participant develops and maintains its own conversion software, which translates the systems it calls Workers into MDK's common language. Commitments, in Tether's framing, mean each firm will ship and support that conversion layer for its own products. Farms typically run a mixed fleet, with devices from different makers reporting status in incompatible ways; a shared format removes that friction and gives a control layer one consistent view of the site. The kit's scope is deliberately narrow: it standardizes how equipment, pools and applications exchange information, leaving operators free to choose which version they run and who holds approval rights. Tether's CEO, Paolo Ardoino, has been steering operations toward AI-run mining, and MDK supplies the plumbing for that plan. The company says QVAC, its AI mining agent, is already running on top of MDK in a trial capacity, an early marker of where the kit is meant to lead. What the announcement does not provide is scale: no facility counts, no share of network hash rate and no projected savings appear anywhere in the release. Release authority over MDK stays with Tether's core team; the fifteen committing companies gain no control over the kit itself.

@tether · X post

Its official announcement on X.

View on X

Inside v0.11: Approvals, Keys and Open Questions

Version 0.11 of the kit shows both the ambition and the friction of putting an AI agent in charge of physical hardware. The reference agent asks for human approval before it reboots a device or changes a power mode, and it rejects the request outright if no operator responds within two minutes, so an unanswered command expires rather than executing on its own. That guardrail is only as strong as the identity behind it: where a site has not configured user identification, approvals are processed as coming from a shared local operator, and there is no way to tell who actually signed off. The deeper gap sits at the Worker layer, the component each vendor contributes. In v0.11, a Worker processes incoming commands without verifying the caller's private key, which means anything that can reach the machine on the network could in principle send it instructions directly. Code on the new main branch adds a mechanism that accepts only explicitly permitted keys, closing that hole for sites that upgrade. Both caveats are documented in the kit's own materials rather than raised by outside auditors. Operators decide for themselves whom to grant approval authority and which version to deploy, so the security posture ends up differing from farm to farm. QVAC's trial run on MDK sits at exactly this junction: an agent that can act on hardware needs the same approval discipline a human operator would face. Tether's disclosure is equally thin on economics: the company did not state how much hash rate the fifteen participants represent, how large their facilities are, or what efficiency gains adoption is expected to deliver. For a kit pitched as industry-wide plumbing, those are the numbers that would show whether fifteen commitments amount to a meaningful slice of the network or a list of logos. The push also lands at a soft moment for the token itself: earlier coverage tracked a five-day stretch in which the USDT market cap shed $1 billion.

The significance sits less in the fifteen names than in the standard underneath them. AI operations at mining scale need a uniform control layer, and MDK is Tether's bid to establish that layer first. QVAC in effect holds command authority over site hardware, functioning less like a dashboard and more like an AI crypto wallet with write access to physical machines. Where DeFAI projects point autonomous agents at trading, Tether points one at containers full of ASICs, where a mistaken command can idle hardware or waste power. The absent voices matter too: none of the fifteen companies has published its own confirmation, timeline or scale figure so far, so the breadth of the backing rests on Tether's account alone.