Feature/lit 3549 js sdk add datiltest support

[Ansonhkg]

Description

Add support for datil-test

npm tag

@datil-test

Test

❗️ All tests passed except wrapped keys tests, we need to add datil-test support in the following services:
✅ (11 Jul 24) All tests related to these services now works!

  TestNetworks: 'https://test.wrapped.litprotocol.com/encrypted',
  Production: 'https://wrapped.litprotocol.com/encrypted',

NETWORK=datil-test yarn test:local

[MaximusHaximus]

I've shipped the update to wrapped-keys backend so it supports datil-test now 👍

Looking at how 'give me an RPC URL for network X' logic is become more complex, and it spans across so many packages, I wonder if it would make sense to create a map of network names to RPC urls in constants and reference it there instead of using || statements checking specific network names -- basically the same pattern I used here:

js-sdk/packages/wrapped-keys/src/lib/service-client/constants.ts

Lines 5 to 17 in 88cf00e

	type NETWORK_TYPES = 'TestNetworks' | 'Production';
	const SERVICE_URL_BY_NETWORKTYPE: Record<NETWORK_TYPES, string> = {
	TestNetworks: 'https://test.wrapped.litprotocol.com/encrypted',
	Production: 'https://wrapped.litprotocol.com/encrypted',
	};
	export const SERVICE_URL_BY_LIT_NETWORK: Record<SupportedNetworks, string> = {
	[LitNetwork.DatilDev]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.DatilTest]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Cayenne]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Manzano]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Habanero]: SERVICE_URL_BY_NETWORKTYPE.Production,
	};

WDYT?

I just added one question about the staging.apis domain vs. lit-general-worker -- otherwise this looks good to me.

[Ansonhkg]

I've shipped the update to wrapped-keys backend so it supports datil-test now 👍

Looking at how 'give me an RPC URL for network X' logic is become more complex, and it spans across so many packages, I wonder if it would make sense to create a map of network names to RPC urls in constants and reference it there instead of using || statements checking specific network names -- basically the same pattern I used here:

js-sdk/packages/wrapped-keys/src/lib/service-client/constants.ts

Lines 5 to 17 in 88cf00e

	type NETWORK_TYPES = 'TestNetworks' | 'Production';
	const SERVICE_URL_BY_NETWORKTYPE: Record<NETWORK_TYPES, string> = {
	TestNetworks: 'https://test.wrapped.litprotocol.com/encrypted',
	Production: 'https://wrapped.litprotocol.com/encrypted',
	};
	export const SERVICE_URL_BY_LIT_NETWORK: Record<SupportedNetworks, string> = {
	[LitNetwork.DatilDev]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.DatilTest]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Cayenne]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Manzano]: SERVICE_URL_BY_NETWORKTYPE.TestNetworks,
	[LitNetwork.Habanero]: SERVICE_URL_BY_NETWORKTYPE.Production,
	};

WDYT?

I just added one question about the staging.apis domain vs. lit-general-worker -- otherwise this looks good to me.

100%

Update 1:
Tracking this here https://linear.app/litprotocol/issue/LIT-3593/[js-sdk]-add-a-map-of-network-names-to-rpc-url

Update 2:
PR up here: https://github.com/LIT-Protocol/js-sdk/pull/527/files

Update 3:
PR#527 is now merged to this PR.

[MaximusHaximus]

I think our symbol is backwards from what I see on chainlist -- otherwise this is GTG. Nice work on the constant maps <3 :)

[MaximusHaximus]

Almost there I think -- tstLPX/tstLIT is a bit of a mindbender. Just one other comment re: relayerUrl handling & types

[MaximusHaximus]

2 last changes I think, and a nit. We're almost there :D

[MaximusHaximus]

👍 LGTM, I think this is GTG 💖
Nice work <3