Tether's MDK v0.11 reference agent pauses device actions for human approval, but each mine must decide who is allowed to approve. The software version a site runs also changes which equipment-command checks apply.
Paolo Ardoino's push to bring AI into Bitcoin mining has a human decision at its center: who may authorize a machine to change what it is doing? Tether's MDK v0.11 reference agent pauses its device-action tool for human approval, while the site must establish who is entitled to give it.
Tether announced commitments from 15 industry participants on October 24 to build and maintain integrations with its Mining Development Kit, an open-source framework connecting mining equipment, pools and applications. The list includes BITMAIN, MicroBT, Canaan, Bitdeer, Foundry Digital and Luxor Technology.
What the reference agent can do
Participants will build Workers, software that translates a company's existing hardware, pool or system interface into MDK's common language. Each company chooses the functions it exposes. The announcement gives no participating-fleet capacity, share of Bitcoin hashrate or measured savings.
The v0.11 reference site's action tool accepts one named device and offers two operations: reboot it or change its power mode. The power-mode options are low, normal, high and sleep.
Approval depends on the site
The reference tool is marked as a write, so the agent's execution loop emits a pending-approval event and pauses before invoking it. The Gateway agent plugin documents a default two-minute approval window, and an unanswered request resolves to rejection.
However, when no user identity is supplied, requests use a shared local operator. In that configuration, an approval pause does not distinguish one human from another. A mine assembling this version must therefore connect its own identity checks to the approval surface.
Newer code changes the picture
The tagged v0.11 security blueprint says direct command.request calls have no Kernel-side permission check. Newer main-branch code differs: at the pinned snapshot, Workers require admitted caller keys unless an explicit allowAll setting is enabled.
Meanwhile, the published security guide retrieved October 24 still describes Workers without caller allowlists. An operator needs to match the guide to the deployed code before treating either as the description of a site's protections.
Release authority stays with the project. The governance document gives the core team final project authority, and an integration commitment does not itself grant a participant authority over MDK's releases.
Source: CryptoSlate
Trading involves risk.
Risk Disclaimer
