Protocol Pause Proposal Executor

WHAT IT DOES

This tool executes protocol pause proposals, allowing authorized parties to temporarily halt protocol functionality during emergencies. It reads and displays protocol pause proposal details (target contract, calldata, proposer, and duration), pause eligibility (whether the caller is authorized to execute the pause), pause status (pending, eligible, executed, or cancelled), executor balance, chain ID, pause history (number of past pauses), and pause threshold (minimum number of executors required). Beyond read-only access, the tool lets you execute the five key actions: execute a protocol pause proposal, approve a pause execution (if required), batch execute multiple pause proposals in one transaction, claim pause confirmation, and cancel a pending pause.

HOW TO USE

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

TECHNICAL MECHANISM

The tool interacts with a pause executor contract that manages protocol pause proposals. The executePause() function executes a pause proposal, temporarily halting protocol functions for the specified duration. The contract validates that the caller is eligible and that the pause is still pending. The pauseStatus() function returns the current state (0 = pending, 1 = eligible, 2 = executed, 3 = cancelled). The pauseThreshold() function returns the minimum number of executors required. Batch pause uses pauseBatch() with arrays of pause IDs and durations. The tool fetches pause history via pauseHistory().

WHAT IT CANNOT SEE

Cannot verify that pausing the protocol is the correct response or that the proposal is valid. Relies entirely on the protocol contract's verification and the destination chain's final state. Cannot detect if the pause is being used maliciously, if the proposal is actually harmful, or if the pause is being performed by an unauthorized party.

PLEASE NOTE — EVM CHAINS ONLY

Supports Ethereum, Polygon, Optimism, Arbitrum, Base and similar EVM chains. The pause executor must implement proposalTarget(), proposer(), pauseStatus(), pauseEligible(), pauseThreshold(), pauseDuration(), executePause(), approvePause(), pauseBatch(), claimPause(), cancelPause(), and pauseHistory(). The tool is read-write: it signs transactions for execution, approval, batch execution, claiming, and cancellation. Always verify the contract address and pause ID before submitting. Pausing requires explicit confirmation.