fix: set legacy contracts to zero address in protocol deployment mode for subgraph service

tmigone · tmigone · commit 74c08074814f · 2025-09-18T11:59:12.000-03:00
Signed-off-by: Tomás Migone &lt;tomas@edgeandnode.com&gt;
diff --git a/packages/subgraph-service/ignition/configs/protocol.default.json5 b/packages/subgraph-service/ignition/configs/protocol.default.json5
@@ -13,6 +13,11 @@
     "gnsImplementationAddress": "",
     "subgraphNFTAddress": "",
 
+    // These do not exist in the protocol deployment, but are needed by ignition modules
+    // so we set them to 0x00...00
+    "legacyDisputeManagerAddress": "0x0000000000000000000000000000000000000000",
+    "legacyServiceRegistryAddress": "0x0000000000000000000000000000000000000000",
+
     // Must be set for step 2 of the deployment
     "disputeManagerProxyAddress": "",
     "disputeManagerProxyAdminAddress": "",
diff --git a/packages/subgraph-service/ignition/configs/protocol.localNetwork.json5 b/packages/subgraph-service/ignition/configs/protocol.localNetwork.json5
@@ -13,6 +13,11 @@
     "gnsImplementationAddress": "",
     "subgraphNFTAddress": "",
 
+    // These do not exist in the protocol deployment, but are needed by ignition modules
+    // so we set them to 0x00...00
+    "legacyDisputeManagerAddress": "0x0000000000000000000000000000000000000000",
+    "legacyServiceRegistryAddress": "0x0000000000000000000000000000000000000000",
+
     // Must be set for step 2 of the deployment
     "disputeManagerProxyAddress": "",
     "disputeManagerProxyAdminAddress": "",
