improve: use recipient ZERO_ADDRESS

across-protocol · Oct 25, 2023 · aba05f7 · aba05f7
1 parent 351f102
commit aba05f7
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 2 deletions.
diff --git a/api/_utils.ts b/api/_utils.ts
@@ -488,7 +488,7 @@ export const getRelayerFeeDetails = async (
   amount: sdk.utils.BigNumberish,
   originChainId: number,
   destinationChainId: number,
-  recipientAddress = "0x893d0d70ad97717052e3aa8903d9615804167759", // A known dummy address
+  recipientAddress: string,
   tokenPrice?: number,
   message?: string,
   relayerAddress?: string

diff --git a/api/limits.ts b/api/limits.ts
@@ -30,6 +30,7 @@ import {
   HUB_POOL_CHAIN_ID,
   ENABLED_ROUTES,
 } from "./_utils";
+import { constants } from "@across-protocol/sdk-v2";
 
 const LimitsQueryParamsSchema = object({
   token: validAddress(),
@@ -149,7 +150,7 @@ const handler = async (
         ethers.BigNumber.from("10").pow(18),
         computedOriginChainId,
         Number(destinationChainId),
-        undefined,
+        constants.ZERO_ADDRESS,
         tokenPriceNative
       ),
       hubPool.callStatic.multicall(multicallInput, { blockTag: BLOCK_TAG_LAG }),