> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fcode.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Wallet Safety

> The Fased wallet safety model for agent commerce: wallet rules, protected signing, manual approval, approved service actions, records, and role separation.

**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

```text theme={"theme":{"light":"min-light","dark":"min-dark"}}
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

<Columns>
  <Card title="Wallet roles" icon="wallet">
    Separate Agent, Mining, and Vault wallets keep balances and responsibilities clean.
  </Card>

  <Card title="Wallet rules" icon="list-checks">
    Caps, allowlists, schedules, routes, assets, and destination rules define what an agent may request.
  </Card>

  <Card title="Approvals" icon="badge-check">
    Manual approval, pre-approved lanes, and higher-risk checks keep important actions intentional.
  </Card>

  <Card title="Protected signing" icon="key-round">
    Signing stays on a controlled approval path with clear policy and records.
  </Card>
</Columns>

## Action modes

| Mode              | What it allows                                                                                      |
| ----------------- | --------------------------------------------------------------------------------------------------- |
| Observe only      | The agent watches data, mining cycles, offers, or wallet state and leaves actions for review.       |
| Recommend only    | The agent suggests an action with sources, reasoning, limits, and expected receipts.                |
| Approval required | The agent prepares the action, and the operator approves before signing or payment.                 |
| Capped automation | The agent can act inside strict caps, allowlists, schedules, routes, assets, and destination rules. |
| Emergency stop    | The operator can pause wallet requests, subscriptions, or scheduled work.                           |

## Wallet roles

| Role          | Purpose                                                                                   |
| ------------- | ----------------------------------------------------------------------------------------- |
| Agent wallet  | approved service actions, sends, routes, schedules, skills, payment records, and receipts |
| Mining wallet | Satcoin mining and public activity records                                                |
| Vault wallet  | protected 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.

## Read next

<Columns>
  <Card title="Demo" href="/demo" icon="play">
    See how wallet safety appears in the demo.
  </Card>

  <Card title="Privacy" href="/privacy-and-security" icon="message-circle">
    See the privacy roadmap.
  </Card>

  <Card title="Mining" href="/mining" icon="pickaxe">
    See how mining fits wallet separation.
  </Card>
</Columns>