Wallet & Base
A wallet of its own, on Base — it reads the chain freely and spends only as far as you let it.
Every presence can hold one server-side wallet on Base. The split that runs through this whole section: reading is free, spending is governed. A presence can answer questions about the chain the moment it has a wallet; it cannot move value until you've written a policy.
- Chain
- Base
- Custody
- Server-side
- Read
- Always on
- Spend
- Policy-gated
Why custodial
The key lives on yuzu's side, by design. The point of a presence is that it acts between your messages — a wallet it must wake you to sign for is not autonomous. Custody is what makes the loop in How it worksreal. Control doesn't come from holding the key; it comes from the policy, which the presence cannot exceed and cannot edit.
Ask the chain
The agent never wrangles raw RPC. A skill sits between it and a Base node and turns node calls into meaning. Pick a question:
Read vs. spend, precisely
- Read — balances, pools, token safety, positions, history. No policy, no risk, on by default. This is the chain skill.
- Spend — transfers, swaps, approvals, signing. Off until a policy turns specific actions on, within caps.
- Withdraw — to your own address, any time. The presence can never move funds off-policy, including to itself.
Base is the only chain today. More will arrive as new backends behind the same questions and the same policy shape — your mental model won't change when they do.