Main.net Mainnet intelligence

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 use Setup checks
Production risk Rate limits
Privacy risk Request metadata
Required check Chain ID

Common public RPC risks

Networks with explicit public endpoint cautions

Base OP Stack L2 mainnet https://mainnet.base.org Base states its public endpoints are rate-limited and not for production systems. Production apps should use a node provider or run dedicated infrastructure.
Ethereum L1 mainnet https://ethereum-rpc.publicnode.com Ethereum.org does not publish a canonical free public RPC for production use. Treat public endpoints as convenience links and use dedicated infrastructure for apps.
Monad EVM L1 mainnet https://rpc.monad.xyz Monad public RPC access is rate-limited. Use official docs and dedicated provider endpoints before deploying production systems.
MegaETH Ethereum L2 mainnet https://mainnet.megaeth.com/rpc MegaETH states RPC endpoints are rate-limited and may change. Always check official docs before relying on endpoint URLs.
Chiliz Chain EVM mainnet https://rpc.ankr.com/chiliz Chiliz states listed RPC endpoints are free to use and rate-limited; add request pauses or use dedicated infrastructure for heavier traffic.
Flow EVM EVM L1 mainnet https://mainnet.evm.nodes.onflow.org Flow EVM public endpoints are shared endpoints; verify Flow documentation and operate dedicated gateway infrastructure when production requirements demand it.
Sei EVM L1 mainnet https://evm-rpc.sei-apis.com Sei documentation notes that public endpoints have rate limits. Production apps should consider a dedicated RPC provider or running their own node.
Kaia EVM L1 mainnet https://public-en.node.kaia.io Kaia documentation states public endpoints are for testing and development, can be rate-limited, and are not guaranteed for commercial use.
Astar EVM parachain mainnet https://evm.astar.network Astar documentation states free public endpoints are rate-limited and not suitable for high-demand dapp UIs or indexers.
Oasis Sapphire EVM ParaTime mainnet https://sapphire.oasis.io Oasis 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.
Gnosis EVM mainnet https://rpc.gnosischain.com Gnosis describes its free starter RPC as having no SLA. Production apps should use professional RPC providers or dedicated infrastructure.
Celo OP Stack L2 mainnet https://forno.celo.org Celo documentation notes that Forno is rate-limited and recommends higher-support providers as usage grows.
Linea ZK rollup L2 mainnet https://rpc.linea.build Linea notes that dapps using public endpoints may encounter rate limiting. Use private node providers or run infrastructure for production usage.
OP Mainnet OP Stack L2 mainnet https://mainnet.optimism.io Optimism labels public RPC URLs as rate-limited. Use them for development or light checks, not production-grade app reliability.
Unichain OP Stack L2 mainnet https://mainnet.unichain.org Unichain states the public RPC is rate-limited and should not be used in production systems. Use a dedicated provider or node for production traffic.
Ink OP Stack L2 mainnet https://rpc-gel.inkonchain.com Ink lists multiple RPC providers and endpoints. Verify the primary endpoint and provider fit before routing production traffic through a public endpoint.
Soneium OP Stack L2 mainnet https://rpc.soneium.org Soneium states free public endpoints are rate-limited and not suitable for high-demand production usage such as indexers or busy dapp UIs.
Moonbeam EVM parachain mainnet https://rpc.api.moonbeam.network Moonbeam publishes public endpoint rate limits. For production systems, compare limits and provider requirements before choosing an RPC endpoint.
Cronos EVM EVM L1 mainnet https://evm.cronos.org Cronos public endpoints are convenience references. Production systems should review Cronos node documentation and provider limits before routing traffic.
Metis Andromeda Optimistic L2 mainnet https://andromeda.metis.io/?owner=1088 Metis documentation distinguishes public RPCs, private providers, and self-hosted nodes. Use public endpoints for light use and dedicated infrastructure for production.
Zora OP Stack L2 mainnet https://rpc.zora.energy The listed Zora RPC is a public endpoint reference. Verify current Zora documentation and provider limits before routing production traffic.
Taiko ZK rollup mainnet https://rpc.mainnet.taiko.xyz The listed Taiko RPC is a public endpoint reference. Treat it as a convenience link and verify current Taiko infrastructure guidance before production use.
Solana L1 mainnet https://api.mainnet.solana.com Solana 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