Session Key Revoker

WHAT IT DOES

This tool revokes active session keys, preventing them from being used for further transactions or actions. It reads and displays the session key address, session key expiry (timestamp), session key permissions (bitmask of allowed actions), session key status (active, revoked, or expired), your account balance, chain ID, and revocation history. Beyond read-only access, the tool lets you execute the five key actions: revoke an active session key, approve a session key revocation (if required), batch revoke multiple session keys in one transaction, claim revocation confirmation, and cancel a pending revocation.

HOW TO USE

Connect your wallet and select the network. Enter the revoker contract address and the session key address you want to revoke. Click "Load State" to fetch the session key status, expiry, permissions, and revocation history. Review the session key status, expiry date, and permissions. If the session key is active and you have sufficient balance, click "Revoke" to invalidate the session key. If the contract requires explicit approval, click "Approve" first. To revoke multiple session keys at once, click "Batch Revoke." Click "Claim" to confirm a completed revocation, or "Cancel" to cancel a pending revocation. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with a session key contract that manages session keys for delegated execution. The revokeSession() function marks a session key as revoked, invalidating any future transactions signed with it. The contract validates that the caller is the owner of the session key or has appropriate permissions. The sessionStatus() function returns the current state (0 = unknown, 1 = active, 2 = revoked, 3 = expired). The sessionExpiry() function returns the expiration timestamp. Batch revocation uses revokeBatch() with an array of session key addresses. The tool fetches revocation history via revocationHistory().

WHAT IT CANNOT SEE

Cannot verify that the session key is no longer being used off-chain or that the revocation will be respected by all dApps. Relies entirely on the session key contract's verification and the destination chain's final state. Cannot detect if the session key is still cached in other applications, if the revocation transaction is front-run, or if the session key is being used in a separate context.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The revoker contract must implement sessionStatus(), sessionExpiry(), sessionPermissions(), revokeSession(), approveRevocation(), revokeBatch(), claimRevocation(), cancelRevocation(), and revocationHistory(). The tool is read-write: it signs transactions for revocation, approval, batch revocation, claiming, and cancellation. Always verify the contract address and session key address before submitting.