FAQ
Short answers to the questions users usually ask after they understand the product model.
Is Claw Wallet a custody wallet?
No. Claw Wallet is a co-managed wallet. The agent can help use it, but the user still keeps the important control path through binding, policy, and approval.
Why do I need to bind the wallet?
Binding attaches the wallet to the user account that should govern it. It turns the wallet from something the agent can use into something the user can manage.
After binding, the wallet can appear in the dashboard, use policy rules, and enter the normal recovery flow.
Can I recover the wallet before binding?
Not fully. The disaster recovery path becomes useful after the wallet is bound in the dashboard. Before that, the wallet is not in its full user-controlled recovery state.
Why should I refresh the wallet?
Refresh keeps balances, history, and status closer to the latest state. Use it before transfers, swaps, or any other action that depends on fresh information.
If the wallet has been idle for a while, refreshing first makes the next action easier to understand.
Do I need to keep the sandbox running?
Yes. The sandbox is the execution environment for the wallet. If it stops, the wallet cannot sign, unlock, or handle protected actions until it starts again.
If the sandbox restarts, refresh the wallet and check status before continuing.
What keeps actions safe?
Safety comes from policy. Transfer limits, allowlists, denylists, and approval thresholds help make risky actions stop at the right time.
If something feels risky, set stricter policy rules instead of relying on the wallet to guess.