Native tokenFrom causes an error in executeBridgeTokenTransaction about sdk

[BlazeWasHere]

Can you send a minimal reproducible code?

[Vaulverin]

import {ethers, providers, Wallet} from 'ethers';
import {Bridge, Networks, Tokens} from '@synapseprotocol/sdk';

const WALLET_PRIVATE_KEY = '';
async function main() {
  const provider = new providers.JsonRpcProvider(process.env.ARBITRUM_RPC);
  const walletFrom = new Wallet(WALLET_PRIVATE_KEY, provider);
  const fromNetwork = Networks.ARBITRUM;
  const toNetwork = Networks.AVALANCHE;
  const tokenFrom = Tokens.ETH;
  const tokenTo = Tokens.WETH_E;
  const amountFrom = ethers.constants.WeiPerEther;
  const synapseBridge = new Bridge.SynapseBridge({
    network: fromNetwork.chainId,
    provider: walletFrom.provider,
  });
  const amountTo = await synapseBridge.estimateBridgeTokenOutput({
    tokenFrom,
    chainIdTo: toNetwork.chainId,
    tokenTo,
    amountFrom,
  });
  /** the error occurs in executeBridgeTokenTransaction
   *  reason: 'invalid contract address or ENS name',
   *   code: 'INVALID_ARGUMENT',
   *   argument: 'addressOrName',
   *   value: null
   */
  const tx = await synapseBridge.executeBridgeTokenTransaction(
    {
      amountFrom,
      amountTo: amountTo.amountToReceive,
      chainIdTo: toNetwork.chainId,
      tokenFrom,
      tokenTo,
    },
    walletFrom
  );
  await tx.wait();
  console.log(`Success: ${tx.hash}`);
}

main();

[bleaker0x]

@Vaulverin apologies for not seeing this issue (along with your other one) sooner. So, from what I can see, you're passing chainIdTo: fromNetwork.chainId to executeBridgeTokenTransaction which would lead to the "invalid contract address or ENS name" error you're receiving, since WETH.e doesn't exist on Arbitrum.

Let me know if you still have an issue after passing toNetwork.chainId to the chainIdTo parameter.

[Vaulverin]

Yeah, it's just a misspell in this example. With toNetwork.chainId i have the same error.

[BlazeWasHere]

It seems like you made a fork and fixed it with this commit, could you make a PR into the dev branch with that?

[Vaulverin]

Yeah, sure

[bleaker0x]

Closing as fixed with merge of #58 into dev.