Contract Bytecode Identity Verifier

Paste the runtime code and creation code a counterparty gave you, plus the deployer and either a nonce (CREATE) or a salt (CREATE2). The node hashes both blobs, checks the two size limits, reads the fields the compiler appended, recomputes the address the deployment must have produced and compares it with the address and verified-source hash they declared. Nothing is read from a chain, so it tells you whether the bytes agree with the claims, not whether those bytes are what is deployed.

🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.

Not proved. A zero-knowledge proof of this node is slow, because hashing the code inside the prover is expensive; it waits on a host hashing function and a scheduled downtime run. The result below is a plain recomputation, not a sealed proof.

Declared bytes (JSON)

creation_code, runtime_code, creation_scheme (create or create2), deployer, then nonce or a 32-byte salt; optional declared_address and declared_verified_source_hash. All hex is 0x-prefixed.

Result

Manifest