Revoking a delegation
Revoking a delegation is instant, permanent, and gasless - and it is the only way to stop a single delegation.
Revoking is the kill switch for one specific delegation. It's instant, it can't be undone, and it never costs you gas.
What revoke does on-chain
Revoking builds an operation that removes the delegation's session from the account's Smart Sessions module outright. There's no timelock and no delay - once it's relayed and included, the session is gone. It's also always gasless, through a dedicated revoke-only path that's never gated on you holding native currency to pay for it - you can revoke even an account you can't otherwise afford to transact from.
A mandate is revoked the same way in spirit, but even more simply: revoking a mandate is instant and unconditional, with no optional gating at all.
There's no pause button for one delegation
Smart Sessions has no concept of pausing a single session - it's either enabled or it's gone. There is no freeze or unfreeze action scoped to one delegation: attempting either always fails outright, and it's documented that way rather than silently ignored.
That leaves exactly two real options:
- Revoke this one delegation - permanent, instant, and specific to this delegate.
- Freeze the whole account - reversible, and it stops every delegation at once, not just one. See The smart account and Rules & AgentGuard for how account-wide freezing works.
If you only want to pause one delegate temporarily, there's no way to do that today. Revoking is permanent; freezing is account-wide. Choose whichever tradeoff you actually want before you act.
The revoke flow
Build - the backend builds the unsigned revoke operation for the delegation you selected.
Sign - you sign it client-side, the same as any other owner-lane action.
Relay - the signed operation is relayed to the chain.
Revoking isn't shown to you as done the moment it's relayed - it's only reported back as revoked once that operation is actually included on-chain, not merely accepted by the bundler.
What stays behind
Revoking removes future authority - it doesn't erase history. The delegation's record, its status, and every immutable policy snapshot captured while it was active all remain visible for review; only its ability to act going forward is gone.