Guardian Whitelist Manager

WHAT IT DOES

This tool manages guardian whitelists for security-sensitive contracts. It reads and displays guardian addresses, whitelist status (whether each address is on the whitelist), whitelist entry details (address and permissions), manager account balance, chain ID, whitelist history (number of whitelist changes made), and guardian permissions (bitmask of allowed actions). Beyond read-only access, the tool lets you execute the five key actions: add a guardian to the whitelist, remove a guardian from the whitelist, approve whitelist changes (if required), batch add or remove multiple guardians in one transaction, claim whitelist change confirmation, and cancel a pending whitelist change.

HOW TO USE

Connect your wallet and select the network. Enter the whitelist contract address. Add guardians by entering their address and optional permissions (bitmask). The tool builds a list of pending changes. Click "Load State" to fetch your account balance, whitelist history, and contract state. Review the pending changes and whitelist state. If you have sufficient balance, click "Apply Changes" to submit all pending whitelist modifications. To add or remove multiple guardians at once, use "Batch Apply." If the contract requires explicit approval, click "Approve" first. Click "Claim" to confirm a completed whitelist change, or "Cancel" to cancel a pending change. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with a whitelist contract that manages guardian addresses. The addGuardian() function adds an address to the whitelist with specified permissions. The removeGuardian() function removes an address from the whitelist. The applyBatch() function accepts arrays of addresses to add and remove, applying all changes in a single transaction. The contract validates that the caller is authorized to manage the whitelist. The guardianPermissions() function returns the permissions for a given guardian. The tool fetches whitelist history via whitelistHistory().

WHAT IT CANNOT SEE

Cannot verify that the guardian addresses are trustworthy or that the whitelist changes are authorized. Relies entirely on the contract's verification and the destination chain's final state. Cannot detect if the guardians are malicious, if the permissions are appropriate, or if the whitelist changes are being performed by an unauthorized party.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The whitelist contract must implement isGuardian(), guardianPermissions(), addGuardian(), removeGuardian(), approveWhitelistChange(), applyBatch(), claimWhitelistChange(), cancelWhitelistChange(), and whitelistHistory(). The tool is read-write: it signs transactions for adding, removing, approval, batch applying, claiming, and cancellation. Always verify the contract address and guardian addresses before submitting.