WHAT

Previously, we added support for specifying a private RPC URL in the artillery test, which was great as it resolved the artillery issue. However, the SDK itself should also allow overwriting the RPC URL. This is important for servers running our SDK long term, as they will eventually hit the RPC URL rate limit.

I was thinking we could do something like this initially:

const litClient = await createLitClient({
  networkModule: nagaDev,
  rpcUrl: '<private_rpc_url'
});

but this is not a good solution, because the nagaDev module is a singleton that has already captured the hardcoded RPC when it was instantiated. Overwriting methods on the shared networkModule inside createLitClient is risky because it might have global side effects.

Solution

Add a .withOverrides method on the network module. It’s safer, more testable, and lets you spin up multiple clients with different RPCs without stepping on each other.

eg.

import { nagaDev } from '@lit-protocol/networks';

const customNagaDev = nagaDev.withOverrides({ rpcUrl: '<private_rpc_url' });
const litClient = await createLitClient({ network: customNagaDev });

TEST

LIT_YELLOWSTONE_PRIVATE_RPC_URL=https://rpc-chronicle-yellowstone-testnet-9qgmzfcohk.t.conduit.xyz/xxx bun run test:e2e "rpc override"

Docs Update

https://github.com/LIT-Protocol/docs-v2/pull/1/files