Beacon Proxy Upgrade Executor

WHAT IT DOES

Beacon Proxy Upgrade Executor is a specialized developer tool that upgrades beacon proxy contracts by updating the implementation address stored in the beacon contract. It reads the current beacon address directly from the EIP-1967 beacon storage slot (0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50) of the proxy using eth_getStorageAt, ensuring accurate detection of the beacon contract. The tool then reads the beacon contract's current implementation address via the implementation() view function or by querying the beacon's EIP-1967 implementation slot. It retrieves the proxy's bytecode via eth_getCode to verify it follows the beacon proxy pattern and confirms the proxy is properly deployed. The tool also reads chain state to determine the current block number and checks the connected wallet's balance to estimate gas availability. Once the beacon proxy state is verified, the tool builds and signs upgrade transactions on the beacon contract using the wallet as the upgrade executor (the beacon's owner or authorized caller), calling either upgradeTo for standard beacon upgrades or upgradeToAndCall for upgrades that require an initialization call. All operations include gas estimation and optional calldata support.

HOW TO USE

Connect your wallet to the target EVM chain. Enter the beacon proxy contract address and the new implementation address. Optionally, check the "Include initialization call" box and provide calldata (hex-encoded) if the beacon upgrade requires additional setup. Click "Read proxy state" to fetch and verify the current proxy configuration. The tool will display the current beacon address, current implementation (as reported by the beacon), and validate that the proxy follows the beacon pattern. Review the upgrade details carefully. If all checks pass, click "Sign & execute beacon upgrade" to submit the upgrade transaction. The tool will send the transaction to the beacon contract, wait for confirmation, and update the review panel with the new implementation address upon completion. A confirmation message will display the transaction hash and block number.

TECHNICAL NOTE: BEACON SLOT RESOLUTION AND DUAL VERIFICATION

The tool first reads the beacon address from the proxy's EIP-1967 beacon slot. It then performs bytecode verification to confirm the proxy uses the beacon pattern by checking for the presence of the beacon slot and validating that the proxy contains the standard beacon proxy fallback logic. Next, the tool resolves the current implementation address from the beacon contract using two strategies: it first attempts to call implementation() on the beacon, and if that fails, it reads the beacon's own EIP-1967 implementation storage slot directly. This dual-verification approach ensures accurate detection even when the beacon contract uses non-standard function names. The tool dynamically detects which upgrade function the beacon exposes—upgradeTo or upgradeToAndCall—by checking the contract's ABI. If upgradeToAndCall is available and calldata is provided, the tool routes the transaction accordingly; otherwise, it falls back to upgradeTo. Gas estimation is performed before sending, and the tool provides real-time feedback during transaction submission and confirmation.

WHAT IT CANNOT SEE

The tool cannot verify that the new implementation's storage layout is compatible with all proxies pointing to the beacon, meaning upgrades that introduce storage conflicts or shift existing state variables in any proxy will still execute. It cannot detect logic errors, reinitialization failures, or missing function selectors in the new implementation that would break the behavior of proxies using this beacon. It cannot predict the full runtime impact of the upgrade on all proxies that reference the beacon, including interactions with other contracts that depend on the proxy's ABI. It cannot handle proxies that are not beacon-compliant or that use non-standard patterns. The tool cannot perform upgrades on non-EVM chains and cannot verify the implementation's source code or security audits. It also cannot detect if multiple proxies using the same beacon will be affected by the upgrade or if any proxies will become incompatible.

PLEASE NOTE

This tool is designed exclusively for EVM-compatible chains (Ethereum, Polygon, BSC, Arbitrum, Optimism, Avalanche C-Chain, etc.). It does not support non-EVM blockchains like Bitcoin, Solana, Cosmos, or Tron. The connected wallet must have upgrade authority over the beacon contract (typically the beacon's owner). The upgrade transaction is irreversible; only a subsequent beacon upgrade can roll back changes. All proxies pointing to this beacon will immediately use the new implementation after the upgrade is confirmed. Always test beacon upgrades on a testnet before executing on mainnet. Gas costs vary by network and the complexity of the upgrade calldata. The tool provides no warranty or guarantee of upgrade safety; users are responsible for verifying all implementation details and testing all dependent proxies before execution.