​

Wallet Roles and Policies

Agent wallet  = normal approved work, Marketplace order actions, skills, sends
Mining wallet = Satcoin mining actions and mining/operator proof
Vault wallet  = protected storage and optional Fased Network bond authority
External addr = read-only balance checks or send destination, never a local source

​

Role map

​

How to enable

1. Create or import an Agent wallet.
2. Set one Agent wallet as the primary Agent fallback if you want approved actions to have a default.
3. Create or import the singleton Mining wallet before SAT mining.
4. Create or import a Vault wallet for protected storage or Fased Network bond.
5. Enable chains and token caps in wallet runtime policy.
6. Enable protected custody or split-key/passkey flows for wallets that require stronger unlock.
7. Keep the Agent wallet funded only for the amount of work it is allowed to do.

@wallet:agent
@wallet:agent-1
@wallet:mining
@wallet:vault

​

Chat behavior

Show all balances for @wallet:agent.
Show SOL and SPL assets for @wallet:agent-1.
Show all balances for @wallet:mining.
Show the vault SOL balance for @wallet:vault.

Show SOL and SPL balances for 4ey8zYsSo9...nfXWVg5g.

• prepare and send require an Agent wallet source
• advanced wallet actions, recurring wallet-action plans, and scheduled sends use the Agent-only wallet_action tool
• Mining and Vault wallets are rejected as chat automation sources
• destination can be a raw address or a receive handle like @wallet:vault
• policy still checks chain, token, amount, direct signing, skill permission, custody state, and approval path

Send 0.1 SOL from @wallet:agent to @wallet:vault.

​

Manual send in Wallets

• a visible source wallet selector
• balances per wallet handle
• manual review before a send
• destination as @wallet:<id> or an external address
• custody unlock prompts
• transaction records and approval state

​

Marketplace use

1. Buyer starts checkout from a Marketplace listing.
2. No funds move at checkout start.
3. Buyer clicks Pay.
4. Agent wallet sends to the seller payee address under wallet policy.
5. Order records tx, invoice, receipt, order evidence, delivery, and result.
6. Seller Sales receives the inbound order envelope and validates evidence.

1. Seller publishes an offer backed by a real manual or automated service path.
2. Seller Agent wallet or configured payee receives the order funds.
3. Seller Sales shows invoice, receipt, order evidence, and delivery state.
4. Reviews or disputes reference saved evidence.

​

Skills, plugins, and automation

• skills can see wallet tools only through the selected Agent’s tool surface
• risky wallet actions require a wallet action manifest or explicit allowlist
• skill origin and registry allowlists can reject wallet access
• wallet policy caps still apply even when a skill is approved
• disabled skills cannot use wallet tools
• skills can request optional route actions, schedule plans, scheduled sends, and trigger-order actions only when their wallet action grant includes those actions
• custom, workspace, and catalog-installed skills cannot use Mining or Vault wallets; only the built-in Satcoin mining runtime and bundled SAT mining skill use the @wallet:mining path

• skills inherit wallet access only through an approved persona or tool policy
• each persona can define allowed wallets, assets, routes, max spend, cadence, data sources, and approval requirements
• personas should make wallet authority easier to reason about, not broader than the current Agent-only wallet action grants
• data skills can inform a wallet action, but they do not bypass wallet policy

​

Advanced and scheduled wallet actions

• reviewed sends
• autonomous sends when Agent policy allows them
• invoice or order action
• scheduled sends
• Marketplace order action
• skill/plugin wallet task with manifest permissions
• inspected token-action routes
• reviewed trigger-order actions when configured
• recurring wallet-action plans through Tasks and wallet_action.schedule_plan
• event-triggered wallet actions under explicit policy

• persona-reviewed wallet plans
• recurring Marketplace subscriptions

• allowed wallet role: Agent
• allowed chain and asset
• max amount per action and period
• allowed destination or venue
• approval mode
• schedule or trigger source
• receipt storage
• emergency stop

​

Mining use

@mining

Check @mining status and readiness.
Start @mining with @wallet:mining.
Stop @mining.
Deposit 1 SOL into @mining capital.
Set @mining commit to 0.5 SOL.
Claim @mining for cycle 123.
Ask @mining to analyze strategy from my history.

Stop @mining if pool capital is above 100 SOL and miner count is above 10.
Start @mining when miner count drops below 10.
Every cycle, analyze @mining history and set the best strategy before submit.

​

Vault and split-key custody

• higher-value balances
• manual-first storage
• recovery separation
• optional Fased Network bond authority
• receiving funds from the Agent wallet

Wallet is locked by split-key custody.
Unlock the selected wallet and retry.
No funds were moved.

​

Scenario guide

​

Read next

• Wallet
• Wallet Chat and Channels
• Mining Chat and Automation
• Wallet Selection Contract
• Wallet Autonomous Security
• Mining
• Offers and Marketplace