What the specification defines

EIP 3855 introduces PUSH0 at opcode 0x5f. It pushes zero, occupies one byte and costs 2 gas. PUSH1 with a zero argument occupies two bytes and costs 3 gas. Whole-contract size and cost still depend on the full bytecode and execution path. Ethereum EIP 3855 ↗

How a build becomes incompatible

Imagine deploying one application to networks with different active EVM rules. An updated compiler produces the same build for both, including an instruction supported by only one configuration. Deployment or calls can then behave differently. Examine the submitted bytecode and the compiler's target-EVM setting, retaining compiler and optimization versions.

Checking a release

Deploy and exercise the principal calls on every supported configuration. Connect each artifact hash to its build settings so a dependency update remains reproducible. Separate network build profiles can make compatibility explicit. Compare gas on identical inputs to connect any cost change to the actual build used by the application.