Review an Unfamiliar Add-Network Prompt Before Accepting

A wallet can receive suggested network details from a website. Those suggestions are untrusted input: a reassuring network name does not establish that the endpoint or chain is the one you intended.

Compare the complete network description

Record the proposed chain identifier, RPC URLs, explorer URL and currency metadata, then compare them with independently located official documentation. EIP-3085 describes an add-network method and its security considerations, but it is a proposal rather than proof that every wallet implements identical validation. A copied network name or familiar currency symbol is weak identity evidence compared with the complete documented configuration.

Understand the endpoint trust question

An RPC service supplies chain observations and may learn request metadata. HTTPS protects a transport connection but does not establish that the service returns honest chain data or belongs to the intended provider. A matching chain ID is necessary context, yet a local fork can use a mainnet ID too. Keep the endpoint’s provenance and environment separate from the identifier it reports.

Distinguish adding from switching

Adding network details does not necessarily select that network, and selecting it does not move balances from another chain. Base’s official documentation distinguishes mainnet 8453 from Base Sepolia 84532. If a prompt suggests one while the task requires the other, investigate before proceeding. Testnet and mainnet balances remain separate even when their currency labels and account-address formatting look similar.

Stop when the suggestion cannot be verified

Do not replace an existing trusted endpoint simply because an error page or unsolicited message supplies a faster alternative. Keep the unfamiliar details for a non-sensitive report and consult the wallet’s official instructions. This page adds or switches no network and changes no RunixCoin configuration. Its public form remains fixed to Base WETH-to-USDC estimates, with execution unavailable; accepting an add-network prompt would not establish a verified swap route.

References and verification

Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.