Tether's mining kit lets AI reboot rigs, but the human who approves is undefined
Tether's open-source Mining Development Kit can reboot a Bitcoin rig or switch its power mode, and its reference agent stops to ask a human first. The catch, according to Token Times' review of the v0.11 code and documentation, is that the same version cannot reliably say which human is answering.
Tether announced on October 24 that 15 industry participants had committed to build and maintain integrations with MDK, a framework meant to give mining hardware, pools and applications a common interface. The list includes BITMAIN, MicroBT, Canaan, Bitdeer, Foundry Digital, Luxor Technology, F2Pool, OCEAN, Proto, SpiderPool, Stratum V2, ACME Swisstech, Elektron Energy, EMCD and Heatbit. Each will build Workers, software that translates a company's existing hardware or pool interface into MDK's language, and each chooses which functions it exposes.
The reference site's action tool accepts one named device and offers two operations: reboot it, or set its power mode to low, normal, high or sleep. Because the tool is classed as a write, the agent's execution loop emits a pending-approval event and pauses before calling it; a rejection blocks the command, and the Gateway plugin documents a default two-minute window after which an unanswered request resolves to rejection. But the v0.11 plugin binds sessions and approvals to the identity that created them, and when no user identity is supplied it falls back to a shared local operator, so the pause does not distinguish one person from another. A mine running this version must attach its own identity checks to the approval surface.
The tagged security blueprint draws a similar line elsewhere. Direct command.request calls carry no Kernel-side permission check, and the v0.11 Worker dispatches network commands without checking the caller's key, so a peer that can reach a Worker and address its public key could submit commands directly, the blueprint warns. Newer main-branch code tightens this: at the pinned snapshot checked on October 24, Workers require admitted caller keys unless an explicit allowAll setting is enabled, and a v0.12-labelled changelog describes Kernel roles for reading, writing and administration. The published security guide still describes Workers without caller allowlists, so operators need to match the guide to the code they actually deploy.
Data leaves the site too, depending on configuration. The agent supports local QVAC models and hosted endpoints, and with a hosted provider prompts and tool results travel to that endpoint's host. Tether says its QVAC mining agent already runs on MDK as an early demonstration, but the announcement gives no participating-fleet capacity, share of Bitcoin hashrate or measured savings. MDK's governance document reserves final project authority for the core team, final technical authority over merges and releases for the Lead Maintainer, and authority over strategy and roadmap for the Community Manager, while the v0.11 security policy handles fixes on a best-effort basis for the latest main commit only. A mine's autonomy therefore rests on three choices it makes itself: who may approve writes, which backend programs can reach its equipment, and whose software updates it adopts.
