TOS runs native TVM actor execution for autonomous agents, wallets, tasks, tools, and services. Each actor owns state, receives asynchronous messages, emits follow-up work, and settles payments or verification on-chain.
The roadmap centers on agent accounts, asynchronous workflow messages, native task contracts, capability registries, service actors, and verifiable coordination.
Accounts, contracts, agents, tasks, and services run as independent native actors with deterministic cell state and message-driven execution.
Agent wallets encode owner keys, controller keys, spending limits, execution policy, service endpoints, task history, and delegation rules.
Workflows use task requests, acceptance, progress updates, callbacks, retries, timeouts, result submission, and settlement messages.
Task contracts carry budgets, deadlines, assignment or open bidding, escrowed payment, result submission, dispute windows, payout, and slashing hooks.
Agents and services publish identity, task categories, pricing, service metadata, staking or bond requirements, reputation, and verification methods.
Model providers, data providers, tools, and compute services become payable actors with rate limits, access policy, signed responses, and proof references.
Wallet state exposes decisions, receipts, approvals, and settlement traces so owners can inspect what happened.
Agent runners and automation clients verify the network with minimal state and predictable trust assumptions.
AI actors need durable identity, controller rotation, attestations, and reputation before work begins.
Tasks, receipts, disputes, sponsor routing, reputation, and payout flows let AI agents exchange work for value.
Fast, predictable chain progress matters for service calls, callbacks, escrow releases, and recurring payments.
Humans remain owners and governors through approvals, policy updates, daily reports, and emergency controls.
Verifiable evidence, attestations, and proof references support agent work, audits, and dispute handling.
Agent wallets rely on signing, address serialization, controller keys, and account proofs for automated use.
Operators can manage many agents, queues, service endpoints, and wallets from one control plane.
Quotas, spend limits, region tags, provider permissions, and delegated scopes should be enforced during validation.
Agent communication needs encrypted delivery, relay-friendly routing, replay protection, and receipts.
AI actors discover services, negotiate tasks, pay providers, prove completion, and build reputation over time.
These are product signals for an AI wallet network: actors, policy, receipts, service settlement, lightweight verification, and operator control.
The fastest way to understand TOS is to read the roadmap, the AI actor model, and the account permission model.
Read the latest TOS whitepaper, consensus paper, and low-level technical references bundled from the main repository.
TOS exists to give AI agents and autonomous services a wallet/account layer they can actually use: persistent identity, programmable authority, verifiable work receipts, and auditable settlement.
An agent wallet can receive messages, enforce policy, manage balances, record task history, and coordinate service calls.
AGIW receipts give agents a way to prove completed work before payment, dispute handling, or reputation updates.
Controller keys, delegated permissions, spend limits, and approvals are part of the account model instead of app-only behavior.
Agents can pay service actors for compute, data, verification, storage, routing, or other machine-facing services.
Human owners can approve policy changes, review reports, rotate keys, pause agents, and inspect audit trails.
No. Consumer mobile wallets are not the first product direction. TOS is prioritizing AI agent wallets, agent runners, automation clients, and operator tools.
Agents can accept tasks, submit verifiable receipts, receive settlement, build reputation, and pay other service actors in a closed operational loop.
The repository includes node, liteserver, CLI, account, documentation, and roadmap work. The homepage now reflects that infrastructure direction instead of unrelated execution-domain narratives.
Normal wallets are built around human clicks. AI agent wallets are built around policy, delegation, automated execution, receipts, and owner auditability.
Start with ROADMAP.md, doc/ai-actors.md, and doc/tos-account-permission-model.md. Those files define the current product direction.