Contract Code Identity Verifier

Choose this endpoint when you need cryptographic assurance that a deployed contract's bytecode matches a known-good reference (e.g. from an audit report), when you need dual-node confirmation to guard against a compromised RPC, or when you need to resolve proxy patterns (EIP-1167/1967/1822) to find the actual implementation contract. Prefer this over a simple eth_getCode call when security and tamper-evidence are required, or when dealing with upgradeable proxy contracts where the logic address may have changed.

• Invalid or non-checksummed contract address returns a 400 error
• Address is an EOA (not a contract) — returns empty code hash or error
• Expected hash provided but does not match — returns mismatch result
• Two nodes return conflicting code hashes — verification fails with inconsistency error
• Unsupported chain specified — returns 400 validation error
• Network timeout or node unavailability — returns 503 or partial result