ERC-777 Operator Revocation Tool

WHAT IT DOES

This tool evaluates ERC-777 operator revocation readiness, helping users determine if an operator's authorization can be revoked. Given an ERC-777 token contract address, a token holder address, and an operator address, it reads the token's name, symbol, decimals, total supply, granularity, and balances for both the holder and operator. It then checks whether the operator is a default operator (cannot be revoked individually), whether the operator is specifically authorized for the given holder via isOperatorFor, and retrieves the full list of default operators and the holder's authorized operators. The tool then displays a clear revocation status—Operator authorized (can revoke), Default operator (cannot revoke individually), or Operator not authorized (already revoked)—along with all relevant token parameters and operator lists. All data is pulled directly from the blockchain in real time, providing a transparent, auditable view of ERC-777 operator revocation readiness.

HOW TO USE

Connect your wallet using the Connect button in the header. Select the target network from the dropdown—Ethereum Mainnet, Polygon, Optimism, Arbitrum One, Base, or Sepolia testnet. Enter the ERC-777 token contract address, the token holder address, and the operator address to revoke. Click "Check revocation." The tool will fetch the token details, balances, granularity, default operators, isOperatorFor status, and authorized operators for the holder. Results appear in the card below with a prominent revocation status badge, lists of default operators and authorized operators for the holder, token information including name, symbol, decimals, granularity, total supply, holder and operator balances, and a breakdown of revocation factors with checkmarks or crosses. Use this information to verify that an operator authorization can be revoked.

ERC-777 OPERATOR REVOCATION VERIFICATION WITH DEFAULT OPERATOR SUPPORT

The tool provides comprehensive ERC-777 operator revocation verification through multiple on-chain reads. First, it retrieves the token's name, symbol, decimals, and total supply via standard ERC-20 view functions. It then reads granularity() to get the smallest unit of token transfers, which is specific to ERC-777. The tool calls balanceOf() for both the token holder and the operator to display their token balances. For revocation assessment, it calls isDefaultOperator() to check if the operator is a default operator—these are operators that are automatically authorized for all token holders and cannot be revoked individually. It then calls isOperatorFor() to check if the operator is specifically authorized for the given token holder. The tool also retrieves the full list of default operators via defaultOperators() and the holder's authorized operators via authorizedOperators(). The revocation status is determined by checking isOperatorFor first—if true and not a default operator, the operator can be revoked. If isDefaultOperator is true, the operator cannot be revoked individually. If neither is true, the operator is not authorized (already effectively revoked). All factors are combined to provide a clear, actionable view of ERC-777 operator revocation readiness.

WHAT IT CANNOT SEE

This tool cannot verify off-chain revocation conditions or ensure that the revocation will be effective. It cannot detect revocation fraud or ensure that the operator is actually de-authorized. It cannot validate revocation decisions or guarantee that the operator will not regain authorization. It cannot guarantee regulatory compliance or ensure that the token contract is compliant with applicable laws. It cannot assure that the ERC-777 contract is free from vulnerabilities, bugs, or malicious code. It cannot verify that the token contract address is correct or that the operator address is valid. It cannot detect front-running or other execution risks. It cannot provide legal or financial advice or guarantee that revoking an operator is safe. All data is provided as-is for informational purposes only; any reliance on the tool's output for revocation decisions is the sole responsibility of the user.

PLEASE NOTE

This tool supports EVM-compatible chains only: Ethereum Mainnet (1), Polygon (137), Optimism (10), Arbitrum One (42161), Base (8453), and Sepolia testnet (11155111). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool requires a Web3 provider (MetaMask or WalletConnect) and access to an RPC endpoint for the selected chain. It does not store any wallet data, token addresses, or revocation records. All queries are performed directly against the blockchain in real time. The tool only provides read-only information and does not execute any transactions. Operator revocation status is based on the token contract's implementation and does not guarantee actual authorization. Always verify critical data independently through a block explorer and consult with security professionals before making any operator revocation decisions.