BNB Chain network reference: Chain IDs, gas assets, explorers and verification
A practical reference for identifying BNB Smart Chain, opBNB and Greenfield without relying on a token symbol or an unverified wallet prompt.
The safest way to identify a blockchain network is to compare several parameters together: network name, Chain ID, native gas asset, RPC source and block explorer. BNB Smart Chain mainnet uses Chain ID 56 and opBNB mainnet uses Chain ID 204. Both use BNB for gas, so the symbol alone cannot identify the network.
BNB Smart Chain mainnet
RPC endpoints can change or be rate-limited. Obtain them from current official documentation or a provider you have independently verified.
opBNB mainnet
A wallet can display BNB on both BSC and opBNB. Confirm the selected network before signing or transferring.
BNB Greenfield
Greenfield combines a blockchain ledger with storage providers. It should not be described as another EVM execution network identical to BSC. Applications can use cross-chain programmability to connect data ownership with BSC or opBNB.
A verification checklist
- Confirm the Chain ID in official documentation.
- Confirm the explorer domain independently.
- Do not trust a token symbol as proof of network identity.
- Verify token contracts on the intended network.
- Send a small test transaction when using a new route.
What changes frequently
Public RPC endpoints, recommended providers, gas conditions, explorer interfaces and wallet labels can change. Chain IDs are operational identifiers and should still be checked before high-value transfers.
Reference tools
Primary sources
Revision record
- Baseline research questions and direct answers were reviewed.
- Operational facts are separated from interpretation and linked to primary documentation.
- Future revisions should record material changes rather than only refreshing the date.