Upgrade Event Alert Tool

WHAT IT DOES

Upgrade Event Alert Tool is a read-only security tool that detects and alerts on smart contract upgrade events in EVM proxies and upgradeable contracts. It scans contract logs using chunked eth_getLogs fetching (automatically halving block ranges when RPC providers reject full-range requests), matches event signatures against a built-in database of upgrade event names (Upgraded, Upgrade, ImplementationChanged, ProxyUpdated, etc.), and provides a detailed report of all detected upgrade events. The tool extracts the new implementation address from event data when available, contextualizes each upgrade with transaction details, block number, timestamp, and gas usage, and includes an alert stub for notification integration. It helps developers and security teams monitor proxy upgrades, detect unauthorized or unexpected implementation changes, and maintain visibility into contract evolution.

HOW TO USE

Connect your EVM-compatible wallet via the BGWallet bridge and select the network where your proxy contract is deployed. Enter the proxy contract address and set the block range to scan (100-10,000 blocks). Click "Monitor Upgrades" to fetch and analyze logs. Results include a summary of total upgrades found, a detailed table of each upgrade event with event name, new implementation address, caller address, block number, transaction hash, gas used, and timestamp, and an alert stub indicating which events would trigger notifications. The tool uses a built-in database of upgrade event signatures (Upgraded, Upgrade, ImplementationChanged, ProxyUpdated, etc.) and supports chunked log fetching to handle RPC provider limits. All analysis is read-only—no signatures or transactions are submitted.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to fetch contract logs via the provider. It maintains a built-in database of upgrade event signatures mapped to 4-byte topic hashes, including 0xbc7cd75a20ee27fd9adebab32041f755214dbc6bffa90cc0225b39da2e5c2d3b (Upgraded), 0x3659cfe6, 0x4f1ef286, 0x8f283970 (ImplementationChanged), 0x7a49e285 (ProxyUpdated), and others. The tool uses chunked log fetching (fetchLogsChunked) that handles provider-specific eth_getLogs limits by recursively halving block ranges until requests succeed. It filters logs by the contract address and by the upgrade event topic signatures. For each log found, the tool retrieves the transaction details via provider.getTransaction(hash), the receipt via provider.getTransactionReceipt(hash), and the block timestamp via provider.getBlock(number). It also extracts the new implementation address from the log data when available (parsing the last 40 hex characters). The tool is compatible with major RPC providers (Alchemy, Infura, QuickNode, Ankr).

WHAT IT CANNOT SEE

This tool has fundamental limitations that users must understand. It cannot actually send alerts or notifications—the tool provides an alert stub but requires external infrastructure for actual notifications. It cannot detect upgrades that do not emit standard upgrade events—custom proxy patterns or non-standard event naming will not be detected. It cannot determine if an upgrade is malicious or legitimate without context—the tool flags all upgrade events, leaving interpretation to the user. It cannot analyze the new implementation bytecode to determine if it contains vulnerabilities—the tool only detects the upgrade event, not the security of the new code. It cannot predict whether an upgrade will break existing contract functionality—the tool does not perform compatibility analysis. It cannot detect upgrades that occur as internal transactions or via delegatecall—only external transaction logs are scanned. It cannot detect upgrades that occur through non-standard proxy patterns (e.g., minimal proxies, beacon proxies) without additional configuration. It cannot monitor upgrades across multiple contracts simultaneously. The tool's alert stub is a placeholder for demonstration purposes.

PLEASE NOTE

This tool only supports EVM-compatible blockchains (Ethereum, Polygon, BSC, Avalanche C-Chain, Optimism, Arbitrum, and their testnets). Solana, Tron, Starknet, SUI, TON, Aptos, Bitcoin, Cosmos, and XRP are not supported. The tool is free, open-source, requires no API keys, and uses the wallet's native provider for all read operations. For production alerting, integrate the tool's output with external notification systems.