Spending permissions
Optional, limited AGW session signing—not blanket access to your wallet.
On this page
Check availability first
Wallet → Spending permissions lets you review optional Abstract Global Wallet session limits. Session activation is gated by Abstract’s mainnet policy registry; the current swap policies require review and are not available for activation yet.
The availability check does not authorize spending. Only an approved route can proceed to explicit consent and owner-wallet authorization. Normal wallet-confirmed swaps remain separate and available without a session.
Choose a narrow permission
The supported scope is one ETH/USDC.e input direction through the direct V2 pool. It is not permission to trade arbitrary tokens, call arbitrary contracts, or buy cubes. V3 swaps still require owner confirmation.
Choose a total token limit, a per-swap limit, an ETH gas budget, and a 15-minute, 1-hour, or 4-hour expiry. Limits are token quantities, not guaranteed dollar values. Installing or revoking a permission has separate wallet-confirmed network costs.
When available, review the limits and consent before authorizing. Remaining spending, approval, and gas allowances can be checked in the same section.
Each swap is still your action
An active matching permission can be selected with Use approved V2 session before requesting a quote. This explicitly selects the V2 route, which may quote differently from V3; it does not silently change an existing quote.
You still press Confirm swap for each action. A session may sign within its approved limits without another wallet popup, but it does not run background trades. A required USDC.e approval remains a separate action from the swap.
Pause, revoke, or recover
Pause stops this device from using the permission; it is not on-chain revocation. Revoke in wallet requests an actual on-chain revocation. Use Refresh status to confirm installation or revocation rather than assuming a submitted request succeeded.
Reloading or signing out removes the local signing key, not necessarily the on-chain grant. If the key is missing, the saved permission information remains available for checking or revocation. An unresolved old grant must not be silently replaced.
Keep pending requests blocked until their status is verified. Never share a private key or recovery phrase to restore a session.