Merge branch 'master' into perf/1-lighthouse-setup

Author: chrstph-dvx

package.json

@@ -32,7 +32,9 @@
     "**/react-syntax-highlighter/refractor/prismjs": "1.30.0",
     "**/@babel/runtime": "7.26.10",
     "**/tar-fs": "2.1.3",
-    "sharp/tar-fs": "3.0.9"
+    "sharp/tar-fs": "3.0.9",
+    "**/form-data": "4.0.4",
+    "**/axios": "1.11.0"
   },
   "keywords": [],
   "author": "",

packages/arb-token-bridge-ui/.env.local.sample

@@ -24,8 +24,24 @@ NEXT_PUBLIC_INFURA_KEY_BASE_SEPOLIA=
 
 # ----- Alchemy -----
 
+# Default Alchemy key. If no network-specific keys are set, it will fallback to this key.
 NEXT_PUBLIC_ALCHEMY_KEY=
 
+# L1 Mainnet
+NEXT_PUBLIC_ALCHEMY_KEY_ETHEREUM=
+
+# L1 Testnet
+NEXT_PUBLIC_ALCHEMY_KEY_SEPOLIA=
+
+# L2 Mainnet
+NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_ONE=
+NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_NOVA=
+NEXT_PUBLIC_ALCHEMY_KEY_BASE=
+
+# L2 Testnet
+NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_SEPOLIA=
+NEXT_PUBLIC_ALCHEMY_KEY_BASE_SEPOLIA=
+
 # ----- Custom RPCs -----
 
 # L1 Mainnet

packages/arb-token-bridge-ui/docs/rpc-configuration.md

@@ -36,7 +36,15 @@ The Alchemy key is provided through the following environment variable:
 
 - `NEXT_PUBLIC_ALCHEMY_KEY`
 
-The key will be used for all chains.
+The key will be used for all chains. However, if you need to have different keys for each chain, you can do so through the following environment variables:
+
+- `NEXT_PUBLIC_ALCHEMY_KEY_ETHEREUM`
+- `NEXT_PUBLIC_ALCHEMY_KEY_SEPOLIA`
+- `NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_ONE`
+- `NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_NOVA`
+- `NEXT_PUBLIC_ALCHEMY_KEY_BASE`
+- `NEXT_PUBLIC_ALCHEMY_KEY_ARBITRUM_SEPOLIA`
+- `NEXT_PUBLIC_ALCHEMY_KEY_BASE_SEPOLIA`
 
 ## Custom RPCs
 

packages/arb-token-bridge-ui/package.json

@@ -22,7 +22,8 @@
     "@unstoppabledomains/resolution": "^8.3.3",
     "ajv": "^8.17.1",
     "ajv-formats": "^2.1.1",
-    "axios": "^1.8.4",
+    "apollo-link-timeout": "^5.0.2",
+    "axios": "^1.11.0",
     "boring-avatars": "^1.11.2",
     "cheerio": "^1.0.0",
     "dayjs": "^1.11.13",