Tether CEO Backs AI Wallets, Developers Must Enforce Limits

Tether CEO Paolo Ardoino has promoted AI-capable wallets and described the company’s Wallet Development Kit (WDK) as a way to connect people, machines and AI agents while preserving owner control. Tether published technical documentation in September explaining the WDK command-line interface (CLI), a background daemon and a bundled Model Context Protocol (MCP) server.

The documentation describes how a wallet seed is stored and how access changes after unlocking. The seed is encrypted with AES-256-GCM and the encryption key is derived using scrypt. On macOS and Linux, the daemon exposes a local socket that is restricted to the operating-system account that owns the process, but the daemon does not require separate credentials for each program. Any process running under that same OS account and able to reach the socket can request the unlocked wallet to sign transactions without re-entering the passphrase.

The default unlocked session lasts five minutes and does not extend automatically with activity. Users can lock the wallet sooner, explicitly unlock it again to reset the timer, or disable the timeout by setting the session lifetime to zero. Tether frames same-user access as an accepted hot-wallet trade-off and recommends operational measures such as a dedicated wallet with limited funds and a dedicated operating-system account.

The bundled MCP server exposes structured tools that let an AI client request actions. The MCP guide says the send_token operation defaults to a dry run and recommends a preview-confirm-execute sequence: preview network, token, recipient, amount and estimated fee, then obtain confirmation before broadcasting. The daemon does not require proof that a prior preview or confirmation occurred, and an execution request sent to an unlocked wallet can broadcast immediately. A separate call_method operation can invoke chain-specific write actions without an enforced dry run or confirmation.

Developers can integrate the WDK SDK to add local transaction policies with configurable ALLOW and DENY rules for recipients and amount conditions. Those checks are opt-in and operate before governed wallet or protocol actions execute. The SDK documentation warns it is not a complete sandbox: raw account references and some internal module calls are not intercepted. The SDK does not automatically maintain recipient lists, fetch prices, decode contract-call data or persist spending counters, so applications must record prior spending and handle concurrent requests if they enforce cumulative budgets or daily ceilings.

The MCP Toolkit provides an additional option for custom agent servers and can be configured to expose read-only tools or require explicit approval flows for write operations. Tether positions the CLI for local operator workflows, the SDK for applications and the Toolkit for custom agent servers, letting builders choose different integration models as they move from tests to products that handle user funds.

The documentation contains minor inconsistencies in tool counts and release labels: a September guide lists eleven tools in some places and nine in others, and a CLI guide shows a 1.0.0-beta.3 label while an August changelog records beta.4. Tether’s Nov. 11, 2024 announcement of WDK set out the broader programmable-wallet ambition. The technical details in the current documentation indicate that when a wallet is unlocked, local processes under the same OS account can request signed transactions, and that enforcement of per-payment approvals and cumulative spending limits depends on how developers integrate WDK and on application-level controls.