Version

Foundry

would

Bitcoin

<p>Tether said on October 24 that 15 mining companies, ASIC manufacturers and mining pools had committed to build and maintain integrations for its open-source Mining Development Kit, or MDK. The announcement gives Tether support from companies spanning machine production, mining operations and pool infrastructure, though the practical test will be whether the promised integrations are built and kept current ahead of MDK’s planned stable release.</p>
<h2 id="fifteen-mining-firms-commit-to-tether-s-mdk">Fifteen mining firms commit to Tether’s MDK</h2>
<p>According to <a href="https://tether.io/news/tethers-mdk-gains-broad-industry-backing-to-accelerate-the-next-generation-of-bitcoin-mining-automation/" rel="noopener noreferrer nofollow">Tether’s announcement</a>, the group includes Bitdeer, BITMAIN, Canaan, MicroBT, Foundry Digital, F2Pool, Luxor Technology, OCEAN, Proto and Stratum V2, among others. That lineup places several types of industry participant behind the same proposed software interface rather than limiting the effort to a single hardware vendor or pool.</p>
<p>The commitments concern MDK, which Tether describes as an <a href="https://cryptodaily.co.uk/glossary/exploring-the-impact-and-benefits-of-open-source-software" rel="noopener noreferrer nofollow">open-source toolkit</a> for mining infrastructure. The company presented the backing as a step towards a more interoperable environment for operating Bitcoin mining equipment and related systems.</p>
<p>For mining operators, the relevance of a shared interface is straightforward: fleets can draw on equipment and services from different providers. Tether’s effort is aimed at reducing the need for applications to build a separate connection for every platform they need to work with. The announcement, however, is a commitment to integration work rather than evidence that a common operating layer is already available across all 15 firms.</p>
<h2 id="mdk-workers-are-the-interoperability-layer">MDK Workers are the interoperability layer</h2>
<p>The concrete mechanism is an MDK Worker. Each participating company is expected to build and maintain one, creating a translation layer between its own hardware, mining pool or system and MDK’s shared interface, according to <a href="https://crypto.news/tether-15-bitcoin-mining-firms-ai-automation-mdk/" rel="noopener noreferrer nofollow">Crypto.news</a>.</p>
<p>That maintenance requirement is material. A Worker is not simply a statement of compatibility; it is the component intended to let a provider’s individual technology communicate with the common layer. Its usefulness therefore depends on participants delivering the integrations and continuing to support them as their own products and systems evolve.</p>
<p>The range of named companies illustrates why Tether is emphasizing the arrangement. ASIC manufacturers such as BITMAIN, Canaan and MicroBT sit alongside <a href="https://cryptodaily.co.uk/glossary/mining-pools-boosting-cryptocurrency-mining-efficiency" rel="noopener noreferrer nofollow">pool</a> and infrastructure names including Foundry Digital, F2Pool, Luxor Technology, OCEAN and Stratum V2. Bitdeer and Proto are also among the listed participants.</p>
<h2 id="automation-depends-on-integrations-not-yet-deployed">Automation depends on integrations not yet deployed</h2>
<p>Tether says the intended result is that applications and AI agents can monitor, troubleshoot, optimize and, eventually, control mining infrastructure across vendors without requiring separate integrations for every platform. In that model, Workers would provide the bridge between disparate mining systems and the applications built on top of MDK.</p>
<p>The proposed use cases extend beyond gathering information from machines. Tether’s stated aim includes troubleshooting and optimization, with eventual control of mining infrastructure. Those capabilities would make the quality and scope of individual Worker implementations especially consequential, since the shared interface is designed to span hardware, pools and other systems.</p>
<p>Crypto.news reported that the integrations were not all already built or in use, so the announced backing should be read for now as a development commitment rather than a completed deployment. It establishes a route to cross-vendor automation, but not a finished industry-wide integration layer.</p>
<h2 id="version-1-0-is-targeted-by-year-end">Version 1.0 is targeted by year-end</h2>
<p>During MDK’s planned rollout, Tether targeted version 0.11 for the October 23–24 Plan ₿ Forum in Lugano and its first stable 1.0 release for the end of 2026, according to Crypto.news. Tether also said its QVAC mining agent was already operating on MDK. The 15-company announcement covers commitments from mining companies, ASIC manufacturers and pools to build and maintain MDK Workers, not confirmation that every participant’s integration has been completed or deployed.</p>
<p>Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.</p>

Tether Wins 15-Company Backing for Open Bitcoin Mining Automation Kit

Table of Contents

Crypto Daily™

Other articles published on Oct 29, 2026

Join our free newsletter for daily crypto updates!