Error creating NxtpSdkConfig

Describe the bug Using @connext/nxtp-sdk@0.2.0-beta.17. When create NxtpSdkConfig, ran into error: No domainId was found for the following chains: 0, 3, 10, 25, 56, 69, 97, 100, 122, 128, 137, 250, 288, 1285, 2221, 9001, 43113, 43114, 42161, 42170, 421611, 192837465, 1666600000; Continuing without indexing these chains. No Connext contract address for domain 3331.

To Reproduce Steps to reproduce the behavior:

1. Create NXTPConfig:

const nxtpConfig: NxtpSdkConfig = {
      logLevel: "info",
      signerAddress,
      chains: {
            "1111": {
		"assets": [
		     {
			"name": "TEST",
			"symbol": "TEST",
			"address": "0x3FFc03F05D1869f493c7dbf913E636C6280e0ff9"
		     },
		     {
			"name": "madWETH",
			"symbol": "TWETH",
			"address": "0xF25927315D101aC04C631878570152658defa7Db"
		     }
		],
	        "providers": ["https://rinkeby.infura.io/v3/d2560cac8f5645fba802260cf1f8c777", "https://rpc.ankr.com/eth_rinkeby"]
	    },
	    "3331": {
		"assets": [
		     {
			"name": "TEST",
			"symbol": "TEST",
			"address": "0x26FE8a8f86511d678d031a022E48FfF41c6a3e3b"
		      }
		 ],
		"providers": ["https://goerli.infura.io/v3/d2560cac8f5645fba802260cf1f8c777"]
	     }
       },
       network: 'testnet',
       environment: 'production'
   };

1. const {nxtpSdkBase} = await create(nxtpConfig);

[just-a-node]

Nice digging - we did update domains in preparation for a major upgrade and we don’t expect things to work on current testnet since everything is going to be redeployed very soon. See https://blog.connext.network/amarok-amb-update-77f142c22db3 for more details.

Please join us in our discord as we’ll announce when new testnet is ready (the docs you were following will also be updated at that time).

[HenryHengZJ]

Was following the SDK Quickstart, when execute yarn xtransfer error was thrown No Connext contract address for domain 3331. Tracing back to source code, looks like its using this json in function getChainData(). From the json file, Goerli has domainId of "1735353714" instead of "3331" which was specified in Nomad. Replacing that fixes the issue. I can see xCall transaction created from the log. However the transaction failed, example tx on Rinkeby. But this is a separate issue.