openclast-wallet

# Openclast Wallet Agent Guide

## Quick start

- Use the CLI to bootstrap:
  - `openclast-wallet setup` creates `wallet-config.json` in the current folder.
  - `openclast-wallet setup --config ./wallet-config.json` initializes the wallet from that file.
- Prefer `wallet-config.json` in the project root and customize chains and limits before use.
- Keep `wallet-config.json` separate from `openclaw.json` (Openclaw config does not accept a top-level `wallets` key).

## Approval flow (mandatory)

All send/approve/contract operations create a **pending transaction** that requires explicit approval.
Always:
1. Create the pending tx (send/erc20/contract call).
2. Ask the user to approve.
3. Only after approval, broadcast and confirm.

If the user asks to “just send,” still require approval unless config is explicitly set to auto mode.

## Key export warning (mandatory)

Never expose private keys by default. If the user asks for export:
- Require explicit confirmation.
- Warn that key export is dangerous and should be protected.
- Use environment gates if available (e.g., `MOLTBOT_ALLOW_WALLET_EXPORT=1`) and explicit CLI confirmation.

If export is not supported in this host, say so and offer safer alternatives.

## Common tasks

### Balance and tokens
- Use the correct chainId for the chain the user mentions.
- If a chain is not configured, read-only balance may still be possible via well-known public RPCs.

### Sending
- Validate chainId and recipient.
- Respect per-tx and daily limits from config.
- Always provide a block explorer link when a tx is confirmed.

### Chain name → chainId

- Ethereum / Mainnet: `1`
- Sepolia: `11155111`
- Polygon: `137`
- Base: `8453`
- Arbitrum One: `42161`

When the user says “balance on Sepolia” or “send on Ethereum,” always map to a chainId and proceed.

## Safety defaults

- Default mode is notify/approval, not auto-send.
- Restrict unverified contracts when possible.
- Store private keys only in OS keychain (macOS) and never in config...