Agentic Wallet 2026: self-custody wallet for AI on TON

Agentic Wallet is a smart-contract wallet built specifically for AI agents on TON, published as part of TON Toolset 2026. It’s the first production solution to “how do you give an AI money without it spending everything”.

The problem Agentic Wallet solves

When an LLM agent needs to execute an on-chain operation (buy USDT, send a tip, rebalance a DEX position), it needs a wallet. Options:

1. Hand over your seed — full custody. Agent can drain everything. Hard no.
2. Create a separate wallet for the agent, transfer some funds — better, but manual top-ups and no protection against “spend it all at once”.
3. MPC wallet with co-signature — works in theory, but the user must sign each op (slow, non-autonomous).
4. Agentic Wallet — split keys + on-chain budget. Agent is autonomous within the limit, user stays out of the way.

Architecture

Agentic Wallet is a smart contract, not a regular wallet-v5. It has:

• User key (full control): top-up, revoke, change budget, withdrawal.
• Agent key (limited): routine ops (transfer, swap, stake) — only if they fit the budget.
• Budget rules (on-chain): daily limit, whitelist, time-window, per-recipient, etc.
• Event log (on-chain): every agent operation is recorded and visible to the user.

       User key                Agent key
          ↓                        ↓
   admin operations         routine operations
   (revoke, top-up)         (transfer, swap, etc)
          ↓                        ↓
   ┌─────────────────────────────────┐
   │     Agentic Wallet (contract)   │
   │  - balance                      │
   │  - budget rules                 │
   │  - event log                    │
   └─────────────────────────────────┘

Budget types

Daily limit: agent can’t spend more than N TON or $N equivalent per calendar day. Resets at UTC midnight.

{
  type: 'daily',
  amount: '50',
  currency: 'USDT',
}

Whitelist: agent can only pay listed addresses. Useful for DCA (agent buys USDT only on STON.fi).

{
  type: 'whitelist',
  recipients: ['EQDxxx...stonfi', 'EQDyyy...dedust'],
}

Per-recipient cap: agent can’t send more than N TON to one address per week.

{
  type: 'per_recipient_weekly',
  amount: '10',
  currency: 'TON',
}

Time window: agent operates only at specified time-of-day (e.g., 9-18 UTC).

{
  type: 'time_window',
  start: '09:00',
  end: '18:00',
  timezone: 'UTC',
}

Combo: multiple rules at once. All must hold (AND).

One-transaction revoke

If the agent is compromised, or you decide to end the experiment:

await agenticWallet.revoke(userSigner);
// On-chain transaction → agent key can no longer do anything.
// User key fully controls funds.

A critical advantage over offline-managed setups. No seed gathering for revocation, no panicking — one transaction, fully revoked.

Integration with MCP

Agentic Wallet is the natural partner for TON MCP. Pattern:

1. User creates an Agentic Wallet with budget $50/day, whitelist of STON.fi + DeDust.
2. Connects Claude/ChatGPT to this wallet via MCP.
3. LLM can swap and transfer — bounded by budget.
4. Every action is on-chain, visible.
5. Anything goes wrong — revoke.

When this matters

Good use cases:

• DCA agent: buys USDT daily for N TON. Simple, bounded.
• Yield agent: monitors APY across staking protocols, moves the position to the best. Whitelist of staking contracts only.
• Personal assistant: LLM helper that can send tips, pay for services. Daily limit.
• AMM agent: auto-rebalances an LP position by triggers.
• Tax bot: calculates gain/loss and auto-sells losers for tax-loss harvesting.

Not for:

• High-frequency trading: daily budgets and whitelists don’t fit HFT.
• Hot custody for large sums: even with budget, an agent could slowly drain within the limit. Small amounts only.

Security: what can go wrong

1. Agent key compromise. Attacker gets the agent key → can operate within budget (e.g., spend $50/day). Mitigation: revoke + rotate key.

2. Hallucinating LLM. LLM mistakenly sends funds to the wrong recipient. Mitigation: whitelist recipients. Without whitelist — the limit caps the loss.

3. Bug in the smart contract. Agentic Wallet is code, and any code can have a bug. Mitigation: open source + audit results public.

4. User-key compromise. The user key grants full control. If compromised, none of the above helps. Protecting the user key is standard operational security (hardware wallet, secure storage).

Compared to alternatives

Agentic Wallet is the sweet spot: bounded protection (budget, not zero spend) + full autonomy within limit + cheap to implement.

What’s next

• Docs: docs.ton.org/overview/ai/wallets.
• Site: agents.ton.org.
• GitHub: the-ton-tech/agentic-wallet-contract.

A new primitive — gives TON an edge in the AI × crypto segment. Building an AI agent that should work with crypto — Agentic Wallet is the base infrastructure to build on.

Pairing with MCP — in our TON MCP piece. Bigger AI × TON picture — in our AI agents on TON piece. Full TON Toolset — overview.