rpc

Usage

$ beam rpc list [--chain <name|id>]
$ beam [--chain <name|id>] rpc add [rpc]
$ beam [--chain <name|id>] rpc remove <rpc>
$ beam [--chain <name|id>] rpc use <rpc>

Examples

$ beam rpc list
$ beam --chain base rpc list

$ beam --chain base rpc add https://beam.example/base-backup
$ beam --chain base rpc use https://beam.example/base-backup
$ beam --chain base rpc remove https://beam.example/base-backup

Overrides

• --rpc <url> on any command overrides the active RPC for that single invocation without modifying config.
• Selecting a different chain (--chain) uses that chain's configured default RPC unless --rpc is also passed.
• In the REPL, changing the session chain clears any prior session RPC override so the prompt and subsequent commands stay on the selected network.

Validation

Beam validates RPC URLs before running a command. Malformed values from --rpc, config.json, or beam chains add fail with a normal CLI error instead of crashing.

ENS lookups always use the configured Ethereum RPC. Beam rejects that endpoint for ENS if it does not report chain id 1.