Platform networks
Manage the platform network catalogue and its RPC endpoints.
Networks manages the global platform network catalogue and each network's RPC endpoint pool. Saving applies changes to the network definition and its RPC pool. The platform reloads saved configuration without a restart, so a change affects organisations using that network.
Networks is a platform administrator's tool. It defines the catalogue every organisation's own Networks page selects from, so reach for it to add a network before any organisation can enable it. It does not grant one organisation access, which happens on that organisation's own page instead.
Two settings with almost the same name decide whether an organisation can use more than one network. The platform setting multi_network_enabled is not a Console control, and it does not turn on the organisation's own switch. Two switches with similar names says who sets each one and in which order.
Adding, editing, or removing a network or its RPC pool is recorded server-side, but the Console has no page where a platform administrator can review that history.
Configure more than one endpoint when the network needs an alternative during an upstream failure. The platform selects one active upstream from the available candidates. Higher weights give an endpoint priority; health and configuration order help choose between endpoints at the same weight. Weights do not reserve percentages of traffic.
An endpoint with weight 3 has priority over one with weight 1 when both are healthy. The lower-weight endpoint provides another candidate if the preferred endpoint becomes unavailable.
Steps
Open Networks
Open Platform settings, then Networks. Filter by network name or chain ID when required.
Screen equivalent: each card shows the network name, chain, enabled state, default marker, and stored RPC endpoints.
Add or edit a network
Use Add network for a new definition, or Edit network on a card. Enter at least one HTTP or HTTPS endpoint and save the network. A network's chain ID identifies which chain the platform connects to for that catalogue entry. Keep the chain identity consistent with the endpoint pool. A served pool can prevent a chain-identity change. Create a separate network entry when you intend to connect to a different chain.
Set gas and funding
Open Advanced settings on either sheet. Chain charges no gas sits there on both the add sheet and the edit sheet. Leave it unset unless you have measured the chain yourself: the platform probes the chain once, caches the answer, and shows you what it found. Setting it wrongly to Yes turns funding protection off, and nothing reports that until an operation fails at the node for want of funds.
The rest of the block, the Gas and funding group, appears on the edit sheet only. A network is added first and tuned from its saved settings afterwards. The group holds the two operating allowances, the deployment fallback, the reasonable-size ceiling, the fee cap headroom, the funding pause window, the settle delay, and the two sponsorship cost bounds.
Every field in that group is optional. Leave one empty and the network inherits it, and the field's placeholder shows the figure it is inheriting, with a line beneath naming where that figure came from: this network, the deployment values, the chain default, the platform default, or a measurement of the chain. Type a value and that one field is fixed on this network, so no later change to the layers beneath it moves the value. Clear the field again to go back to inheriting. Inheritance is per field, not per group.
Set a figure only when a measurement of the chain contradicts the one shown. The pause window is the usual exception: it describes who funds the wallets and how quickly they respond, which is your deployment's circumstance rather than the chain's. Gas settings carries every key, its unit, its accepted range, and its default.
Set endpoint weight
Set each endpoint's weight to a positive whole number. A larger weight gives the endpoint higher priority among healthy candidates. Equal weights allow health scores and configuration order to decide; they do not produce an even traffic split.
Troubleshooting
A network cannot be enabled
Add a valid RPC endpoint. The Console prevents an enabled catalogue entry that the platform cannot reach.
Saving refuses an endpoint address
The platform refuses an endpoint it would never call: one that resolves to a loopback, private, or carrier-grade NAT
address, or to an address that is always blocked, such as a cloud metadata service. The network definition still
saves; the pool is not written, and the error names the refused endpoint. Use an endpoint that resolves to a public
address. Only a network whose deployment values set rpc.allowPrivateUpstreams accepts private endpoints, and that
setting cannot be changed from the Console; see Networks.
Reads or transactions on a network fail right after a change
Confirm the saved endpoints are actually reachable from the platform's network, not just from your browser. Every chain read and transaction submission on that network routes through the pool you just edited, so a bad endpoint here fails those operations immediately. No fallback to the previous pool configuration exists once you have saved over it.
One endpoint in the pool is unreliable but the network mostly still works
Check the endpoint's individual health before assuming the whole network is fine. The platform can select another candidate when an upstream fails. Lower an unreliable endpoint's priority or remove it after confirming that another usable endpoint remains. Weight must stay a positive whole number.
A gas figure I saved is not the one the platform uses
Check that you saved it on the network you meant. A figure typed into a gas field is fixed on that one network and overrides every layer beneath it, so a value that looks ignored is usually set on a different catalogue entry for the same chain. Reopen the edit sheet: a field you set shows your value, and a field you left empty shows the inherited figure as a placeholder with its origin named underneath.
Operations on a network fail for want of funds and no funding request appears
Check Chain charges no gas on that network. Set to Yes on a chain that does charge, it turns funding protection
off, so an unfunded transaction fails at the node instead of raising a request that names the wallet. Clear the field
to let the platform measure the chain again.
A funding request expires before anyone can act on it
Raise Funding pause window on that network. The default suits a deployment where someone is watching and can top a
wallet up within the half hour. A chain funded by hand from a treasury, or one whose token comes from a faucet an
operator has to visit, needs a longer window, and work that was only waiting for money fails when the window runs out.
A network needs to be removed but organisations already use it
Removal here does not check whether an organisation still has the network enabled, and it behaves differently depending on whether the network came from the platform's own baseline set or was added independently. If the network has a baseline definition, removing it clears only your override and the network reverts to that baseline rather than disappearing, and its RPC pool stays intact. If it has no baseline, removal deletes the catalogue entry entirely and clears its RPC pool in the same step; a network name reused later starts with no endpoints configured, not the ones you just removed. Either way, an organisation still selecting a fully removed network has its reads and transaction submissions on that network fail immediately, with no separate warning sent to the affected organisations.