Main.netChain settings lookup

Guide

Public RPC safety

Public RPC endpoints are useful for setup and troubleshooting. They are not production guarantees: expect rate limits, privacy tradeoffs, wrong-chain risk, and provider changes unless you add monitoring and fallback infrastructure.

Quick answer

A public RPC URL is fine for wallet setup, chain ID checks, demos, and read-only troubleshooting. Do not treat it as a production RPC provider unless you have measured limits, monitored errors, reviewed privacy exposure, and configured fallback endpoints.

Best useSetup checks
Production riskRate limits
Privacy riskRequest metadata
Required checkChain ID

Common public RPC risks

Networks with explicit public endpoint cautions

BaseOP Stack L2 mainnethttps://mainnet.base.orgBase states its public endpoints are rate-limited and not for production systems. Production apps should use a node provider or run dedicated infrastructure.
EthereumL1 mainnethttps://ethereum-rpc.publicnode.comEthereum.org does not publish a canonical free public RPC for production use. Treat public endpoints as setup references and use dedicated infrastructure for apps.
MonadEVM L1 mainnethttps://rpc.monad.xyzMonad public RPC access can be rate-limited or temporarily unavailable. Verify Monad docs and current endpoint response before deploying production systems.
MegaETHEthereum L2 mainnethttps://mainnet.megaeth.com/rpcMegaETH states RPC endpoints are rate-limited and may change. If a public endpoint fails, recheck official docs and current availability before relying on it.
RoninOP Stack L2 mainnethttps://api.roninchain.com/rpcRonin documents its public RPC endpoints as rate-limited and not for production environments. Use provider-backed access for production systems.
Chiliz ChainEVM mainnethttps://rpc.ankr.com/chilizChiliz states listed RPC endpoints are free to use and rate-limited; add request pauses or use dedicated infrastructure for heavier traffic.
Flow EVMEVM L1 mainnethttps://mainnet.evm.nodes.onflow.orgFlow EVM public endpoints are shared endpoints; verify Flow documentation and operate dedicated gateway infrastructure when production requirements demand it.
BNB Smart ChainEVM L1 mainnethttps://bsc-dataseed.bnbchain.orgBNB Chain lists several public RPC endpoints. Public dataseed endpoints can be rate-limited or unavailable, so use monitored providers or dedicated infrastructure for production traffic.
SeiEVM L1 mainnethttps://evm-rpc.sei-apis.comSei documentation notes that public endpoints have rate limits. Production apps should consider a dedicated RPC provider or running their own node.
KaiaEVM L1 mainnethttps://public-en.node.kaia.ioKaia documentation states public endpoints are for testing and development, can be rate-limited, and are not guaranteed for commercial use.
AstarEVM parachain mainnethttps://evm.astar.networkAstar documentation states free public endpoints are rate-limited and not suitable for high-demand dapp UIs or indexers.
Oasis SapphireEVM ParaTime mainnethttps://sapphire.oasis.ioOasis documentation warns that public RPC endpoints are points of trust and may be rate-limited, censored, or man-in-the-middle targets. Run dedicated infrastructure for sensitive use.
GnosisEVM mainnethttps://rpc.gnosischain.comGnosis describes its free starter RPC as having no SLA. Production apps should use professional RPC providers or dedicated infrastructure.
CeloOP Stack L2 mainnethttps://forno.celo.orgCelo documentation notes that Forno is rate-limited and recommends higher-support providers as usage grows.
LineaZK rollup L2 mainnethttps://rpc.linea.buildLinea notes that dapps using public endpoints may encounter rate limiting. Use private node providers or run infrastructure for production usage.
OP MainnetOP Stack L2 mainnethttps://mainnet.optimism.ioOptimism labels public RPC URLs as rate-limited. Use them for development or light checks, not production-grade app reliability.
UnichainOP Stack L2 mainnethttps://mainnet.unichain.orgUnichain states the public RPC is rate-limited and should not be used in production systems. Use a dedicated provider or node for production traffic.
InkOP Stack L2 mainnethttps://rpc-gel.inkonchain.comInk lists multiple RPC providers and endpoints. Verify primary endpoint availability and provider fit before routing production traffic through a public endpoint.
SoneiumOP Stack L2 mainnethttps://rpc.soneium.orgSoneium states free public endpoints are rate-limited and not suitable for high-demand production usage such as indexers or busy dapp UIs.
MoonbeamEVM parachain mainnethttps://rpc.api.moonbeam.networkMoonbeam publishes public endpoint rate limits. For production systems, compare limits and provider requirements before choosing an RPC endpoint.
Cronos EVMEVM L1 mainnethttps://evm.cronos.orgCronos public endpoints are convenience references. Production systems should review Cronos node documentation and provider limits before routing traffic.
Metis AndromedaOptimistic L2 mainnethttps://andromeda.metis.io/?owner=1088Metis documentation distinguishes public RPCs, private providers, and self-hosted nodes. Use public endpoints for light use and dedicated infrastructure for production.
ZoraOP Stack L2 mainnethttps://rpc.zora.energyThe listed Zora RPC is a public endpoint reference. Verify current Zora documentation and provider limits before routing production traffic.
TaikoZK rollup mainnethttps://rpc.mainnet.taiko.xyzThe listed Taiko RPC is a public endpoint reference. Treat it as a convenience link and verify current Taiko infrastructure guidance before production use.
SolanaL1 mainnethttps://api.mainnet.solana.comSolana says public endpoints are rate-limited and not intended for production applications. Use dedicated or private RPC servers for launch traffic.

Production checklist

Before using an RPC endpoint in production, confirm the chain ID, verify the endpoint in official documentation, measure reliability from your own regions, monitor errors, and keep fallback providers ready. Main.net does not publish live uptime or latency.

Related checks