BSC network fields in MetaMask and Trust Wallet

Read network fields as different kinds of evidence

A wallet network form combines a human-readable name, a node endpoint, a Chain ID, a currency-symbol label and sometimes an explorer link. They do different jobs. MetaMask defines Chain ID as the value used for network-specific signing, Network URL as the endpoint used to access the network, Currency Symbol as the native-currency display, and Block Explorer URL as an optional place to inspect records. Trust Wallet Mobile documents a similar field set for its custom-network form.

A name such as “BNB Smart Chain” is only a label. A symbol such as BNB is also not a unique network identifier or token contract. Compare the Chain ID and the rest of the fields against the intended network’s own current documentation; an approved-looking form or wallet validation is not proof that a network or endpoint is genuine.

Evidence: MetaMask network fields and trust limits · Trust Wallet Mobile custom-network field names

Field meanings and warnings for MetaMask Extension/Mobile custom-network confirmations. It does not authenticate an RPC provider, guarantee the supplied values or establish a current BSC endpoint.

Trust Wallet Mobile custom-network article only. Its UI path is not generalized to the browser extension, all app versions, regions or a claim that BSC must always be added manually. The article says to use a trusted RPC source; this lesson provides no fixed endpoint.

Compare the documented fields with BNB Chain references

Evidence: MetaMask network fields and trust limits · Trust Wallet Mobile custom-network field names · Dated BSC mainnet settings reference · BSC network data · BSC native BNB gas role

Field meanings and warnings for MetaMask Extension/Mobile custom-network confirmations. It does not authenticate an RPC provider, guarantee the supplied values or establish a current BSC endpoint.

Trust Wallet Mobile custom-network article only. Its UI path is not generalized to the browser extension, all app versions, regions or a claim that BSC must always be added manually. The article says to use a trusted RPC source; this lesson provides no fixed endpoint.

BNB Smart Chain configuration reference, not a live network check. Chain ID, native symbol and explorer are cited with the page date and corroborated by current BNB Chain docs where applicable. RPC endpoints and menu instructions can change.

Used only for the documented role of native BNB as BSC gas. The same page contains dated validator details; those counts and performance claims are not reused as current facts.

MetaMask surfaces are versioned; check support before custom setup

MetaMask’s Help Center page “How to add a network,” checked 2026-10-26, currently lists BNB Chain among supported networks. It describes one route for a network already shown under Additional networks and a separate custom-network form for cases where a network is not listed. The same article covers Extension and Mobile, but names no app build number or publication/update date; treat its menu wording as a dated snapshot of the article, not as a guaranteed screen in every installation.

The companion “How to verify custom network information in MetaMask” page says the details can include name, Network URL, Chain ID, currency symbol and optional explorer URL—and explicitly warns MetaMask does not verify that a custom network is genuine. The lesson compares the fields on paper only; it does not connect a wallet, accept a request, add a network or test an endpoint.

Evidence: MetaMask supported and custom network surfaces · MetaMask network fields and trust limits

MetaMask current support documentation, checked 2026-10-26. Menu labels and availability can change; the page does not require every user to add a custom BNB Chain network manually. No wallet was opened.

Field meanings and warnings for MetaMask Extension/Mobile custom-network confirmations. It does not authenticate an RPC provider, guarantee the supplied values or establish a current BSC endpoint.

Trust Wallet’s cited custom-network guide is mobile-specific

Trust Wallet’s official Academy article “How to Add a Custom Network on the Trust Wallet Mobile App” was published 2025-02-20 and updated 2026-08-19. It lists network name, network symbol, RPC/node URL, Chain ID and optional explorer URL, and says to use a trusted RPC source. It does not name an app build version.

That article documents the Mobile custom-network flow only. It does not establish that every Trust Wallet user must add BSC manually, nor does it define the browser-extension interface. First compare the current provider documentation and the network already offered by the installed product; do not transplant old menu steps or copy a node URL from a dated tutorial.

Evidence: Trust Wallet Mobile custom-network field names · Dated BSC mainnet settings reference

Trust Wallet Mobile custom-network article only. Its UI path is not generalized to the browser extension, all app versions, regions or a claim that BSC must always be added manually. The article says to use a trusted RPC source; this lesson provides no fixed endpoint.

BNB Smart Chain configuration reference, not a live network check. Chain ID, native symbol and explorer are cited with the page date and corroborated by current BNB Chain docs where applicable. RPC endpoints and menu instructions can change.

Resolve a fictional BSC-versus-opBNB mismatch on paper

Fictional worksheet, not a screenshot or observed wallet: a sample form says Network Name “BNB Smart Chain,” Chain ID “204,” Currency Symbol “BNB,” and Explorer “opbnbscan.com.” The name and symbol look plausible for BSC, so neither settles the question.

Compare with the official BNB Chain network references checked 2026-10-26. BSC Mainnet is listed with Chain ID 56 (0x38), symbol BNB and BscScan. The opBNB network-information page lists Mainnet Chain ID 204, symbol BNB and opBNBScan. The solved discrepancy is the Chain ID plus the explorer: this fictional set matches opBNB’s published identifiers more closely than BSC’s, despite its editable BSC-like name and shared BNB symbol. Expected conclusion: flag “not established as BSC; appears to be an opBNB configuration by documented fields,” then leave it unresolved: the live endpoint remains unverified. The fields alone cannot authenticate a live node or rule out a misconfigured/malicious endpoint.

Evidence: Dated BSC mainnet settings reference · BSC network data · opBNB mainnet identifier comparison · MetaMask network fields and trust limits

BNB Smart Chain configuration reference, not a live network check. Chain ID, native symbol and explorer are cited with the page date and corroborated by current BNB Chain docs where applicable. RPC endpoints and menu instructions can change.

opBNB network reference, not BSC. Chain ID 204 and symbol BNB demonstrate why the symbol/name alone does not distinguish networks; the listed RPC endpoints are not reproduced as permanent.

Field meanings and warnings for MetaMask Extension/Mobile custom-network confirmations. It does not authenticate an RPC provider, guarantee the supplied values or establish a current BSC endpoint.

Keep the network, native asset, endpoint and explorer separate

BSC Mainnet’s documented native gas asset is BNB. That says what the protocol uses for fees; it does not mean every token called BNB is the same asset on every network, or that a wallet’s symbol label verifies a token contract. The same BNB symbol appears in BNB Chain’s opBNB Mainnet reference, which is why Chain ID and other network evidence matter.

An RPC URL points to a node service; the explorer URL points to a separate website for reading public records. Providers, endpoints, supported networks and user-interface labels can change. This lesson deliberately gives no fixed RPC endpoint and makes no claim that a displayed configuration was live-tested. No wallet or dApp was opened, connected or signed into; no network was added or transaction sent.

Evidence: BSC native BNB gas role · Dated BSC mainnet settings reference · opBNB mainnet identifier comparison · BSC network data · Network context and wallet display limits

Used only for the documented role of native BNB as BSC gas. The same page contains dated validator details; those counts and performance claims are not reused as current facts.

BNB Smart Chain configuration reference, not a live network check. Chain ID, native symbol and explorer are cited with the page date and corroborated by current BNB Chain docs where applicable. RPC endpoints and menu instructions can change.

opBNB network reference, not BSC. Chain ID 204 and symbol BNB demonstrate why the symbol/name alone does not distinguish networks; the listed RPC endpoints are not reproduced as permanent.

Used only for the conceptual fact that an asset display depends on selected network context; not a diagnosis of any real wallet, balance or transfer. Its example RPC URLs and operational recovery claims are not reused.