Proxy Implementation Verification Linker (Explorer UI)

WHAT IT DOES

This tool connects to your EVM wallet and reads ERC-1967 proxy contract storage slots to link and verify implementation addresses. It fetches the implementation address from the standard storage slot, the beacon address (if used), and the admin address. The tool checks whether the implementation contract is deployed by reading its bytecode and displays the code length. It provides a clear visual link between the proxy and its underlying implementation, making it easy to verify upgradeable contract setups.

HOW TO USE

Connect your Web3 wallet using the Connect button. Enter the proxy contract address in the Proxy Contract Address field. Click "Verify Implementation" to fetch the implementation, beacon, and admin addresses from the proxy's storage slots. Click "Load Sample" to populate fields with an example address. Results appear in the Results card with the proxy address, implementation address with deployment status, beacon address, and admin address, along with bytecode length for the implementation.

TECHNICAL MECHANISM: ERC-1967 STORAGE SLOT QUERYING

The tool uses ethers.js to read specific storage slots defined by the ERC-1967 proxy standard. The implementation address is stored at slot 0x360894a13ba1a3210667c828492db98dca3e2076cc3735a920a3ca505d382bbc. The beacon address is stored at slot 0xa3f0ad74e5423aebfd80d3ef4346578335a9a72aeaee59ff6cb3582b35133d50. The admin address is stored at slot 0xb53127684a568b3173ae13b9f8a6016e243e63b6e8ee1178d6a717850b5d6103. For each retrieved address, the tool uses provider.getCode() to check if the contract is deployed and reports the code length. The tool displays all three addresses with deployment status, providing a complete picture of the proxy's upgradeable setup.

WHAT IT CANNOT SEE

This tool cannot verify that the implementation address is correct or secure—it only reads the stored address. It cannot detect proxies that use non-standard storage patterns—the tool relies on ERC-1967 standard slots. It cannot verify that the implementation bytecode matches a known source—the tool does not compare against source code. It relies on standard storage slot definitions (ERC-1967) and may not support all proxy patterns—some proxies use custom storage layouts. It cannot detect if the implementation has been self-destructed or modified after deployment—the tool only checks current state.

PLEASE NOTE

This is a read-only tool—it never signs transactions. All data is fetched on-demand and stored only in memory; nothing is persisted across page reloads. The tool supports EVM chains only—Ethereum, Polygon, BSC, Arbitrum, Optimism, Base, and their testnets. The tool only works with proxies that follow the ERC-1967 standard—custom proxy implementations may not be detected. Implementation verification is limited to address linkage—always conduct thorough security reviews of both proxy and implementation contracts.