Remove ISM requirement for warp route deploys (#2936)

### Description Warp Deploys should not require the specification of an ISM
hyperlane-xyz · Nov 20, 2023 · 6985064 · 6985064
1 parent bbe8071
commit 6985064
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 5 deletions.
diff --git a/typescript/cli/src/deploy/warp.ts b/typescript/cli/src/deploy/warp.ts
@@ -162,10 +162,7 @@ async function runBuildConfigStep({
   }
 
   // Request input for any address fields that are missing
-  const requiredRouterFields: Array<keyof ConnectionClientConfig> = [
-    'mailbox',
-    'interchainSecurityModule',
-  ];
+  const requiredRouterFields: Array<keyof ConnectionClientConfig> = ['mailbox'];
   let hasShownInfo = false;
   for (const [chain, token] of Object.entries(configMap)) {
     for (const field of requiredRouterFields) {

diff --git a/typescript/sdk/src/deploy/HyperlaneDeployer.ts b/typescript/sdk/src/deploy/HyperlaneDeployer.ts
@@ -229,7 +229,7 @@ export abstract class HyperlaneDeployer<
           chain,
           setIsm(contract, targetIsm),
         );
-        if (targetIsm !== (await getIsm(contract))) {
+        if (!eqAddress(targetIsm, await getIsm(contract))) {
           throw new Error(`Set ISM failed on ${chain}`);
         }
       });