Hardfork Feature Support Checker Per Chain

WHAT IT DOES

Hardfork Feature Support Checker Per Chain analyzes smart contract bytecode to detect usage of hardfork-specific opcodes and features, then generates a comprehensive support assessment across multiple EVM chains. It retrieves on-chain contract bytecode via eth_getCode and fetches verified source code and ABI from block explorer APIs. The tool performs opcode-level scanning for features introduced in major EVM hardforks including Shanghai (EIP-3651, 3855, 3860), Cancun (EIP-1153, 4844, 5656, 6780), Prague (EIP-2935, 3074, 6110, 7002), Osaka, London (EIP-1559), and Berlin (EIP-2565, 2929, 2930). It then cross-references detected hardfork feature usage against a built-in database of network-specific hardfork activation status for Ethereum Mainnet, Optimism, BNB Chain, Gnosis, Polygon, Arbitrum, Base, and other EVM chains. The output includes an overall readiness score, a count of detected hardforks, critical mismatches, a visual matrix with hardforks as rows and target chains as columns with status indicators (active, upcoming, inactive, unknown), and actionable recommendations for deployment timing and chain selection.

HOW TO USE

Connect your BGWallet to the target EVM chain. Paste the address of the contract you wish to analyze. Select the target chains you plan to deploy to using the chip selector—you can choose multiple chains to generate a comprehensive cross-chain hardfork assessment. Optionally supply a GitHub repository URL to pull compiler version information and hardfork notes for additional context. The tool fetches the contract's bytecode, performs opcode disassembly to detect hardfork-specific patterns, and builds a support matrix against the selected target chains. Review the overall readiness score, the visual matrix, critical mismatches, and the list of recommendations. Use the assessment to identify chains that may not yet support the hardfork features your contract relies on, and plan your deployment strategy accordingly—for example, by deploying to chains with full support first, or by refactoring your contract to avoid upcoming hardfork features until target chains have upgraded.

HARDFORK OPCODE DETECTION AND CHAIN ACTIVATION MAPPING ENGINE

The real technical mechanism is the hardfork opcode detection and chain activation mapping engine that combines bytecode analysis with a curated database of network-specific hardfork activation blocks. The tool disassembles the deployed bytecode into its constituent opcodes and scans for opcodes and patterns associated with specific hardforks: PUSH0 (0x5F) for Shanghai, TLOAD (0x5C) and TSTORE (0x5D) for Cancun, BASEFEE (0x48) for London, and other hardfork-specific opcodes. For each detected hardfork feature, the engine cross-references a built-in metadata database that tracks hardfork activation status across major EVM chains—Ethereum Mainnet has Shanghai and Cancun active, while BNB Chain and Gnosis may have Cancun still inactive, and Prague features remain upcoming on most chains. The database is versioned and can be updated as networks activate new hardforks. The tool also detects compiler version fingerprints from bytecode metadata to estimate which hardfork features a contract is likely to use based on compiler defaults. The final output includes a weighted readiness score—100% if all detected features are active on all target chains, with penalties for features that are inactive or have unknown activation status. This approach provides developers with a clear, actionable view of cross-chain hardfork compatibility risks before deployment, preventing failures caused by hardfork feature mismatches.

WHAT IT CANNOT SEE

This tool cannot generate a complete hardfork support assessment without access to contract bytecode or source code. It is limited by your RPC provider's rate limits for bytecode retrieval, which may delay analysis on congested networks. It cannot determine if hardfork-specific features are actually executed at runtime versus merely present in bytecode—some features may be used only in unreachable code paths, but the tool flags them regardless. The detection relies on the completeness of the ABI and source code verification; unverified contracts or incomplete verification data will produce incomplete or inaccurate results. Detection is based on bytecode pattern matching and may miss obfuscated or indirect usages, such as hardfork features called via DELEGATECALL or through inline assembly that obscures the opcode. The tool cannot assess runtime behavior or performance implications of hardfork compatibility, such as gas cost differences between chains that have activated a hardfork versus those that haven't. It may produce false positives for opcodes that appear in data sections rather than code, such as in constant data arrays or jump tables. The tool does not execute the contract to validate compatibility, so it cannot confirm whether hardfork-specific operations would succeed or revert on each target chain. It cannot account for network-specific hardfork activation status or future upgrade schedules—some chains may activate hardforks after the analysis is performed. Hardfork support status may vary across chains and change over time as networks upgrade their EVM implementations.

PLEASE NOTE

This tool works exclusively with EVM-compatible chains. It requires active internet connectivity to access block explorer APIs and RPC endpoints. Some block explorers may require API keys for high-volume bytecode retrieval. The tool is read-only and does not modify or deploy any code—it only produces compatibility assessments. Hardfork activation status varies by chain and may change with network upgrades. Always verify compatibility against official network documentation and test on target chains before production deployment.