Warp Route Deploy Init

You are generating the initial deploy.yaml for a new Hyperlane warp route deployment.

Input

The user provides:

• Linear ticket URL or ID (required, e.g. ENG-3516 or https://linear.app/hyperlane-xyz/issue/ENG-3516/...)
• Deployer address (required — the temporary owner for all chains, e.g. 0xabc...)

If the ticket is not provided, ask for it now.

If the deployer address is not provided, ask for it before proceeding. The deployer address is always used as the owner for every owner field in the deploy.yaml (chain-level and tokenFee-level). Real ownership is set later via /warp-deploy-update-owners — never use real Safe/ICA addresses in this step.

Multi-protocol deployer addresses: if the route spans multiple VM protocols (e.g. EVM + Sealevel), each protocol requires its own deployer address with a different format (EVM: 0x..., Solana: base58). In this case, ask for a separate deployer address per protocol and use: