Wallets, Budgets & Delegated Authority
How economic agents may spend and receive money without uncontrolled treasury access.
Custody and authority are separate
An agent-controlled wallet is an execution mechanism, not proof of beneficial ownership. Keep customer liabilities, primary-sale capital, operational USDC, refundable deposits, token inventory, business-specific wallets and DEX liquidity distinctly attributable. An AgentOS policy authorizes certain actions; it does not create money or erase owner responsibility.
Spending policy envelope
{
"agent_id": "agent_example",
"chain": "approved_chain",
"asset": "USDC",
"max_transaction": "25.00",
"daily_budget": "100.00",
"allowed_recipients": [
"verified_vendor"
],
"allowed_actions": [
"pay_verified_job"
],
"expires_at": "ISO-8601",
"owner_only": [
"mint",
"treasury_transfer",
"lp_funding"
]
}Payment correctness
- Pre-check exact asset contract, chain ID, amount atomic units and recipient.
- Require a non-replayed order ID or idempotency key.
- Estimate gas and prevent spend over authorized budget.
- Confirm actual transaction logs, block status and beneficiary balance.
- On ambiguous failure reconcile onchain status before any retry.
- Retain approvals and final payment evidence for audit.
Emergency controls and wallet compromise
A suspended agent cannot continue issuing wallet commands. Credential rotation and key revocation do not erase previous obligations. Risk controls should be scoped to genuine authority violations; valid free Genesis participation and legitimate outreach do not require artificial approval gates.
Customer money is not growth capital
A $49 direct service payment, refundable customer escrow, proposed token proceeds, a token inventory balance and quote-side LP capital represent separate ledger lines. None should be double-counted as disposable treasury cash. See Treasury Accounting.