fix: rpc endpoint logic in deploy script (#35)

succinctlabs · Jan 15, 2025 · 9d64ab5 · 9d64ab5
1 parent bef47bb
commit 9d64ab5
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/contracts/.env.example b/contracts/.env.example
@@ -4,7 +4,7 @@ CREATE2_SALT=
 ### The owner of the SP1 Verifier Gateway. This is the account that will be able to add and freeze routes.
 OWNER=
 
-### The chains to deploy to, specified by chain name (e.g. CHAINS=mainnet,sepolia,arbitrum_sepolia)
+### The chains to deploy to, specified by chain name (e.g. CHAINS=MAINNET,SEPOLIA,ARBITRUM_SEPOLIA)
 CHAINS=
 
 ### RPCs for each chain ID

diff --git a/contracts/script/utils/Base.s.sol b/contracts/script/utils/Base.s.sol
@@ -24,9 +24,9 @@ abstract contract BaseScript is Script {
         string[] memory chains = vm.envString("CHAINS", ",");
         for (uint256 i = 0; i < chains.length; i++) {
             string memory chain = chains[i];
-
+            string memory rpcEndpoint = vm.envString(string.concat("RPC_", chain));
             // Switch to the chain using the RPC
-            vm.createSelectFork(chain);
+            vm.createSelectFork(rpcEndpoint);
 
             console.log("Running %s script on %s", KEY, chain);