Guardian Veto Revocation Tool

WHAT IT DOES

This tool revokes previously executed guardian vetoes, allowing guardians to undo veto decisions. It reads and displays veto revocation proposal details (original veto target and proposer), revocation eligibility (whether the caller is authorized to revoke), revocation status (pending, eligible, executed, or cancelled), guardian balance, chain ID, revocation history (number of past revocations), and revocation threshold (minimum number of guardians required). Beyond read-only access, the tool lets you execute the five key actions: revoke a previously executed guardian veto, approve a veto revocation (if required), batch revoke multiple vetoes in one transaction, claim revocation confirmation, and cancel a pending revocation.

HOW TO USE

Connect your wallet and select the network. Enter the guardian veto contract address, revocation ID, and type "REVOKE" in the confirmation field. Click "Load State" to fetch the original veto target, proposer, revocation status, eligibility, threshold, and revocation history. Review the revocation details and status. If you are eligible and have sufficient balance, click "Revoke Veto" to undo the veto. If the contract requires explicit approval, click "Approve" first. To revoke multiple vetoes 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 guardian veto contract that allows authorized guardians to revoke previously executed vetoes. The revokeVeto() function undoes a veto, restoring the original proposal's ability to be executed. The contract validates that the caller is eligible and that the revocation is still pending. The revokeStatus() function returns the current state (0 = pending, 1 = eligible, 2 = executed, 3 = cancelled). The revokeThreshold() function returns the minimum number of guardians required for a revocation. Batch revocation uses revokeBatch() with an array of revocation IDs. The tool fetches revocation history via revocationHistory().

WHAT IT CANNOT SEE

Cannot verify that the revocation is justified or that the original veto was incorrect. Relies entirely on the guardian contract's verification and the destination chain's final state. Cannot detect if the revocation is being used maliciously, if the original veto was correct, or if the revocation is being performed by an unauthorized party.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The veto contract must implement revokeVeto(), approveRevocation(), revokeBatch(), claimRevocation(), cancelRevocation(), vetoTarget(), vetoProposer(), revokeStatus(), revokeEligible(), revokeThreshold(), and revocationHistory(). The tool is read-write: it signs transactions for revocation, approval, batch revocation, claiming, and cancellation. Always verify the contract address and revocation ID before submitting. Revocation requires explicit confirmation.