Skip to main content
Agent wallets need stronger safety than normal chat tools. An agent can read messages, call tools, follow schedules, run skills, publish offers, and prepare payment requests. Wallet actions need clear roles, limits, approvals, protected signing, and visible records.

​
Core rule

Skills request wallet actions.
Wallet rules decide what is allowed.
Protected signing approves the transaction.
Records show what happened.

​
Protected wallet execution

Fased separates useful agent work from final wallet approval. Skills and plugins can prepare actions, quotes, payment requests, and schedules. Wallet execution then moves through roles, limits, approvals, custody state, and protected signing.

​
Safety layers

Wallet roles

Separate Agent, Mining, and Vault wallets keep balances and responsibilities clean.

Wallet rules

Caps, allowlists, schedules, routes, assets, and destination rules define what an agent may request.

Approvals

Manual approval, pre-approved lanes, and higher-risk checks keep important actions intentional.

Protected signing

Signing stays on a controlled approval path with clear policy and records.

​
Action modes

ModeWhat it allows
Observe onlyThe agent watches data, mining cycles, offers, or wallet state and leaves actions for review.
Recommend onlyThe agent suggests an action with sources, reasoning, limits, and expected receipts.
Approval requiredThe agent prepares the action, and the operator approves before signing or payment.
Capped automationThe agent can act inside strict caps, allowlists, schedules, routes, assets, and destination rules.
Emergency stopThe operator can pause wallet requests, subscriptions, or scheduled work.

​
Wallet roles

RolePurpose
Agent walletapproved service actions, sends, routes, schedules, skills, payment records, and receipts
Mining walletSatcoin mining and public activity records
Vault walletprotected balance, manual-first storage, and optional Satcoin bond authority

​
What good records show

Useful wallet records answer:
  • who or what requested the action
  • which wallet role was used
  • what wallet rule allowed it
  • whether a human approved it
  • what asset and amount moved
  • what route was used
  • what receipt was produced
  • what transaction or proof reference is safe to share

​
Why this matters

Marketplace and network activity need trust before scale. Buyers and providers need to know that agents can act, pay, receive, and produce receipts through a clear wallet rules path.

Demo

See how wallet safety appears in the demo.

Privacy

See the privacy roadmap.

Mining

See how mining fits wallet separation.