Proposal Execution Trigger

WHAT IT DOES

Proposal Execution Trigger is a governance tool that checks the status of governance proposals and triggers execution for those that are ready. After a proposal passes a vote, it typically enters a timelock period before execution — this prevents immediate execution and allows for review or veto. Once the timelock expires, someone must call the `execute` function on the governor contract to actually enact the proposal. This tool automates that process: it reads the state of multiple proposals, identifies those that are passed, have cleared the timelock, and are not yet executed, then triggers their execution in a single interface — or optionally, in a batched transaction.

HOW TO USE

Connect your EVM wallet via the BGWallet bridge. Enter your governor contract address and a comma-separated list of proposal IDs you want to check. Select your preferred mode: "Check only" to see proposal statuses, or "Check and execute ready" to automatically execute all ready proposals. Click "Check Status" to fetch the current state of each proposal. The tool will display each proposal's ID and its status — "Ready for execution" (passed and timelock complete), "Already executed", or "Pending" (still in voting or timelock). If any proposals are ready, the "Execute Ready Proposals" button becomes active. Click it to trigger execution. The tool handles the execution transaction(s) and provides progress updates and a transaction hash for tracking.

TECHNICAL MECHANISM

The tool reads proposal states from the governor contract using the `state(proposalId)` function, which returns an enum indicating the proposal's current lifecycle stage. It checks for the "Succeeded" state (proposal passed and timelock completed) and verifies that the proposal has not already been executed. When executing, the tool calls the governor's `execute` function with the encoded proposal data (targets, values, calldata, description hash). The tool may use a multicall pattern to execute multiple proposals in a single transaction if the governor supports it. The entire operation is atomic for each execution — if a proposal's state changes between check and execution, the transaction may revert, leaving other proposals unaffected if batched.

WHAT IT CANNOT SEE

This tool cannot guarantee that the proposal will execute successfully if the target contract state or calldata requirements have changed since the proposal was created. Proposals often rely on specific contract states (e.g., a token price, a specific address balance) that may change over time. The tool also cannot predict if the execution will be front-run or if the timelock delay will be extended by the timelock controller. Always verify that the proposal's calldata is still valid and that the target contracts are in the expected state. This tool is an aid for execution, not a guarantee of successful enactment.

PLEASE NOTE

EVM chains only. This tool relies on the BGWallet connector and will not function on Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The user is responsible for ensuring the supplied governor address is correct and that the governor supports the standard `state` and `execute` functions (e.g., OpenZeppelin Governor). Executing proposals may require significant gas — check gas estimates before proceeding.