Networks and RPC setup

Who this is for: developers configuring a project (wallet, script, Hardhat/Truffle config, indexer) to talk to Lumia.

Prerequisites: none.

Choosing a network

Beam testnet is where you build and test. It costs nothing to use once you have testnet tokens, and mistakes there don't touch real funds. Almost all development should target Beam until you're intentionally deploying for production use. Mainnet is the live network with real value: use it only once you've finished testing on Beam.

Steps

1

Decide mainnet or Beam

Per the guidance above.

2

Copy the RPC URL into your project's config

Open /reference/networks and copy the RPC (HTTPS) URL for that network into your project's config as an environment variable, not a hardcoded literal, so you can swap networks without editing code.

3

Copy the matching chain ID into the same config

Wallet and SDK libraries frequently validate the RPC response's chain ID against what you configured; a mismatch here is one of the most common setup errors.

4

Check for a WSS endpoint if your tooling needs one

Check /reference/networks first.

Verify it worked

Call the RPC's eth_chainId method (directly with curl, or through whatever library you're using) and confirm the returned chain ID matches the value in /reference/networks for the network you intended.

curl -s -X POST -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}' \
  "<RPC URL from /reference/networks>"

Troubleshooting

Requests time out or connection refused

You're likely pointed at the retired network's RPC. Recheck against /reference/networks.

eth_chainId returns a value you didn't expect

Your config still has an old RPC URL cached from a previous project or tutorial; replace it with the current value from Reference rather than editing the hex by hand.

Rate limiting on the public RPC. If you're hitting limits, consider running your own node. See /run-a-node/rpc-node/overview.