Yield Vault Emergency Shutdown Executor

WHAT IT DOES

Yield Vault Emergency Shutdown Executor enables authorized roles (owner, guardian, or emergency admin) to trigger an emergency shutdown on yield vault contracts. The tool reads your connected wallet address, vault contract address, emergency shutdown status, shutdown trigger conditions, current block timestamp, vault state (Active/Paused/Shutdown/Withdrawn), outstanding positions, total value locked, and your user role. It displays the current vault status and confirms your authorization before allowing shutdown. Once triggered, the vault immediately pauses all operations, freezes deposits and withdrawals, and initiates the withdrawal of funds to the safety wallet—protecting user funds from potential threats.

HOW TO USE

Connect your wallet and select your network. Enter the yield vault contract address and optionally provide an emergency reason for the audit trail. Click "Fetch vault status" to load the current vault state including TVL, vault state, shutdown status, your role, and outstanding positions. If you are authorized (Owner, Guardian, or Emergency Admin) and the vault is not already shut down, the tool will display a warning box and enable the shutdown button. Review the details carefully, then click "Execute emergency shutdown" to trigger the shutdown. You will be prompted for a final confirmation before the transaction is signed and sent.

THE REAL MECHANISM — ROLE-BASED SHUTDOWN WITH STATE VERIFICATION

Unlike standard pause functions that only check a boolean, this tool implements a comprehensive emergency shutdown system with role-based access control. The vault contract stores user roles (0=None, 1=Owner, 2=Guardian, 3=Emergency Admin) and enforces that only authorized addresses can call emergencyShutdown. The getVaultInfo function returns the TVL, vault state (0=Active, 1=Paused, 2=Shutdown, 3=Withdrawn), shutdown status, and outstanding positions. The shutdown function takes a string reason parameter, which is emitted in an event for audit tracking. When triggered, the vault performs several actions: (1) sets the vault state to Shutdown, (2) pauses all deposit and withdrawal functions, (3) triggers a withdrawal of all funds from active strategies to the vault, and (4) emits a Shutdown event with the reason and caller address. The tool reads the user's role via getUserRole and validates that the caller is authorized before enabling the shutdown button. All arithmetic uses ethers.js BigNumber, and gas costs are reported using receipt.effectiveGasPrice. The tool includes a double-confirmation flow to prevent accidental triggers.

WHAT IT CANNOT SEE

Cannot predict off-chain emergency conditions—the tool has no visibility into market events, oracle failures, or external threats. It cannot ensure shutdown execution correctness—the tool cannot guarantee that the vault's shutdown function will execute correctly or that funds will be safely withdrawn. It cannot detect if the vault contract contains vulnerabilities—the tool does not audit the vault logic or verify its implementation. It cannot verify off-chain risk assessments—the tool has no visibility into any off-chain analysis or threat intelligence. It cannot recover funds if the shutdown fails or if the vault contract is compromised.

PLEASE NOTE — EVM CHAINS ONLY

This tool exclusively supports EVM-compatible chains where ethers.js can connect via standard JSON-RPC. It does not support non-EVM chains such as Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. The vault contract must implement the specific interface expected by this tool (emergencyShutdown, getVaultInfo, getUserRole, isShutdown). Only trigger shutdown in genuine emergencies—this action is irreversible for the current strategy and will impact all vault users. This tool is an emergency response interface, not a financial advisor or security auditor.