Guide
Copy Base chain ID and RPC URL
Base mainnet uses chain ID 8453 / 0x2105, ETH as the gas token,
the public RPC endpoint https://mainnet.base.org, and explorer
https://base.blockscout.com.
Answer first
Base chain ID 8453 quick answer
Use 8453 / 0x2105 for Base mainnet, with RPC URL
https://mainnet.base.org, explorer https://base.blockscout.com,
and ETH as the gas token. The canonical indexed page for this chain is
/status/base/.
https://mainnet.base.org Verification record
Manual metadata review and automated evidence checks are tracked separately. This is not a live uptime, latency, or production reliability monitor.
- Manual metadata review
- Verification status
- Verified metadata
- Verification run
source-monitoring-2026-06-10- Verification tool
source-monitoring-refresh- Source set
- Base docs
- Manual review cadence
- monthly; after July 10, 2026
- Latest recorded chain ID probe
-
eth_chainIdmatched expected0x2105; observed0x2105on
Base mainnet settings
- RPC URL
https://mainnet.base.org- Explorer
- https://base.blockscout.com
- Chain ID
- 8453
- Chain ID hex
0x2105- Currency symbol
- ETH
- Source docs
- Base docs
Base EIP-3085 config JSON
Text-only wallet_addEthereumChain parameters generated from reviewed fields.
Main.net does not connect wallets or request permissions.
Review source documentation before using this in an app or wallet flow.
{
"chainId": "0x2105",
"chainName": "Base",
"nativeCurrency": {
"name": "ETH",
"symbol": "ETH",
"decimals": 18
},
"rpcUrls": [
"https://mainnet.base.org"
],
"blockExplorerUrls": [
"https://base.blockscout.com"
]
} Important note
Base states its public endpoints are rate-limited and not for production systems. Production apps should use a node provider or run dedicated infrastructure.
Main.net is an independent reference site and is not affiliated with Coinbase or Base. Always verify important details in the source documentation before moving funds.
Treat the public RPC endpoint as a setup reference, not as a production reliability promise. Teams running apps on Base should compare monitored provider endpoints, request limits, archive access, alerting, and fallback behavior before shipping user-facing flows.
Use the status page copy path for the current reviewed config: /status/base/#copy-ready-config.