Guardian Veto Executor

WHAT IT DOES

This tool executes guardian vetoes on proposals, allowing guardians to block harmful or malicious actions. It reads and displays veto proposal details (target contract, calldata, value, and proposer), veto eligibility (whether the caller is authorized to veto), veto status (pending, eligible, executed, or cancelled), guardian balance, chain ID, veto history (number of past vetoes), and veto threshold (minimum number of guardians required). Beyond read-only access, the tool lets you execute the five key actions: execute a guardian veto on a proposal, approve a veto execution (if required), batch execute multiple vetoes in one transaction, claim veto confirmation, and cancel a pending veto.

HOW TO USE

Connect your wallet and select the network. Enter the guardian veto contract address, veto ID, and type "VETO" in the confirmation field. Click "Load State" to fetch the proposal target, proposer, veto status, eligibility, threshold, and veto history. Review the proposal details and veto status. If you are eligible and have sufficient balance, click "Execute Veto" to veto the proposal. If the contract requires explicit approval, click "Approve" first. To veto multiple proposals at once, click "Batch Veto." Click "Claim" to confirm a completed veto, or "Cancel" to cancel a pending veto. Each transaction shows confirmation and gas cost reporting.

TECHNICAL MECHANISM

The tool interacts with a guardian veto contract that allows authorized guardians to block proposals. The vetoProposal() function executes a veto on a proposal, preventing its execution. The contract validates that the caller is eligible and that the proposal is still pending. The vetoStatus() function returns the current state (0 = pending, 1 = eligible, 2 = executed, 3 = cancelled). The vetoThreshold() function returns the minimum number of guardians required for a veto. Batch veto uses vetoBatch() with an array of veto IDs. The tool fetches veto history via vetoHistory().

WHAT IT CANNOT SEE

Cannot verify that the veto is justified or that the proposal is harmful. Relies entirely on the guardian contract's verification and the destination chain's final state. Cannot detect if the veto is being used maliciously, if the proposal is actually harmful, or if the veto 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 vetoProposal(), approveVeto(), vetoBatch(), claimVeto(), cancelVeto(), proposalTarget(), proposer(), vetoStatus(), vetoEligible(), vetoThreshold(), and vetoHistory(). The tool is read-write: it signs transactions for vetoing, approval, batch vetoing, claiming, and cancellation. Always verify the contract address and veto ID before submitting. Veto requires explicit confirmation.