Network and RPC Setup

Networks stores the RPC connections used for balance reads, NFT loading, task preparation, and live transactions. Add and test at least one network before using an operational workspace.

Add and test a network

1. Open Networks.
2. Under Add RPC Network, enter a Network Name and the RPC Node URL supplied by your provider.
3. Review Network identity. Sthang makes an initial guess from the name and URL; select the correct chain when the guess is wrong.
4. Choose + RPC. This saves the network and adds it to Configured Networks.
5. In the new configured row, choose Test. The test is read-only and checks the chain identity and basic RPC responsiveness.
6. Confirm that the reported chain matches your intended network and that the latency result is usable.

Do not use a network for live work when the test reports the wrong chain, stale or inconsistent reads, repeated timeouts, or another blocker. Edit the row to correct it, or delete it and add the intended endpoint.

Set the default order

The first configured network is the default when you create a task. Drag rows or use the row movement controls to put your normal network first. Re-test a network after changing its URL or identity.

Optional ABI Wizard key

The Networks workspace also holds the optional Etherscan V2 API Key used to load verified contract ABIs in Custom Contract. Enter the key and choose Save only if you use that feature; it is not required for ordinary RPC access.

Keep RPC URLs and API keys out of screenshots and support messages because a URL may contain a credential. Prefer a dedicated provider credential with provider-side rate and spend limits.