Which RPC providers support Base RPC?

Base RPC provider decision checklist

Before you commit to a Base RPC provider, run through this checklist to avoid common pitfalls:

• Confirm the provider supports Base mainnet and Base Sepolia testnet if you need both for development and production.
• Check whether you need archive data or trace methods for analytics, indexing, or debugging. Not all providers offer archive nodes.
• Verify WebSocket support if your app relies on real-time updates or subscriptions.
• Review rate limits and pricing for your expected request volume. Free tiers are often too restrictive for production.
• Look for failover and redundancy options, such as multiple endpoints or automatic routing, to minimize downtime.
• Test latency from your deployment region to ensure the endpoint is fast enough for your users.
• Check if the provider offers dedicated nodes if you need consistent performance and no noisy neighbors.
• Read the provider's documentation for Base-specific settings, such as the correct chain ID and any network-specific JSON-RPC methods.

What is Base RPC?

Base is an Ethereum Layer 2 network built on the OP Stack, designed to provide low-cost, high-throughput transactions. To interact with Base, applications use JSON-RPC endpoints, commonly referred to as Base RPC. These endpoints allow wallets, dApps, and backend services to read blockchain data, submit transactions, and listen for events.

Base's public RPC endpoint (https://mainnet.base.org) is available for testing, but it is rate-limited and not recommended for production workloads. For reliable access, developers typically rely on third-party RPC providers that offer managed infrastructure with higher limits, better uptime, and additional features.

Why do you need a dedicated Base RPC provider?

Running your own Base node is possible, but it requires significant operational effort: syncing the chain, maintaining hardware, monitoring uptime, and handling upgrades. For most teams, using an RPC provider is more practical, especially when you need:

• High availability: Providers run redundant nodes across regions to minimize downtime.
• Scalability: Providers can handle spikes in request volume without you having to provision new infrastructure.
• Archive data: Access to historical state, which is essential for analytics and certain dApp features.
• Developer tools: Many providers offer debugging, tracing, and analytics tools that simplify development.

What to look for in a Base RPC provider

When evaluating providers, consider the following criteria:

Popular RPC providers that support Base

Many established RPC providers offer Base endpoints. Here are some of the most well-known ones, based on public documentation and community usage:

• Alchemy: Offers a free tier and paid plans, with support for Base mainnet and Base Sepolia. Known for its developer tools and SDKs.
• QuickNode: Provides fast endpoints with a free tier and scalable paid plans. Supports Base mainnet and testnet.
• Ankr: Offers both public and private RPC endpoints for Base, with a globally distributed node network.
• Chainstack: Provides managed infrastructure with a focus on reliability and performance. Supports Base mainnet and testnet.
• dRPC: A decentralized RPC provider that aggregates multiple node providers, offering high reliability and failover.
• PublicNode: A free, privacy-focused RPC provider that supports Base.
• 1RPC: A privacy-preserving RPC relay that offers a free Base endpoint.
• OnFinality: Provides RPC endpoints for Base as part of its multi-chain infrastructure, with options for shared and dedicated nodes.

This list is not exhaustive, and the landscape changes frequently. Always check the provider's official documentation for the latest supported networks and features.

How to connect to Base RPC

Once you have chosen a provider, you will need to configure your application to use the Base RPC endpoint. Here is a basic example using curl to make a JSON-RPC request to a Base endpoint:

curl https://your-provider-endpoint/base \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Replace https://your-provider-endpoint/base with the actual RPC URL from your provider. The response will contain the current block number, confirming that your connection works.

For WebSocket connections, you can use libraries like ethers.js or web3.js. Here is a simple example using ethers.js:

const { ethers } = require("ethers");

const provider = new ethers.providers.WebSocketProvider("wss://your-provider-endpoint/base");

provider.on("block", (blockNumber) => {
  console.log("New block:", blockNumber);
});

Base chain settings for your wallet or dApp

When adding Base to a wallet or configuring a dApp, you will need the following network details:

• Network Name: Base
• RPC URL: Provided by your RPC provider
• Chain ID: 8453
• Currency Symbol: ETH
• Block Explorer URL: https://basescan.org

For Base Sepolia testnet, the chain ID is 84532.

Common pitfalls when using Base RPC

• Using the public endpoint in production: The public endpoint is rate-limited and not reliable for production. Always use a provider.
• Ignoring WebSocket support: If your app needs real-time updates, ensure your provider supports WebSocket.
• Not planning for archive data: If you need historical data, make sure your provider offers archive nodes, as not all do.
• Overlooking rate limits: Free tiers often have strict limits that can break your app under load. Upgrade to a paid plan if needed.
• Forgetting to test on testnet: Always test on Base Sepolia before deploying to mainnet to avoid costly mistakes.

How to evaluate Base RPC providers for your use case

The best provider for you depends on your specific needs. Consider the following scenarios:

• For a small dApp or hackathon project: A free tier from a provider like Alchemy or QuickNode may be sufficient.
• For a production DeFi app: You will likely need a paid plan with higher rate limits, WebSocket support, and possibly a dedicated node.
• For analytics or indexing: You will need archive data and possibly trace methods. Check if the provider offers these.
• For a global user base: Choose a provider with multiple regions and low latency to ensure fast responses worldwide.

Key Takeaways

• Base RPC providers offer managed endpoints that are more reliable and scalable than running your own node.
• When choosing a provider, consider network support, endpoint types, archive data, rate limits, pricing, and reliability.
• Always test on Base Sepolia before deploying to mainnet.
• Use the chain ID 8453 for Base mainnet and 84532 for Base Sepolia.
• OnFinality provides Base RPC endpoints as part of its multi-chain infrastructure, with options for shared and dedicated nodes. Check our RPC pricing and supported networks for more details.

Frequently Asked Questions

What is the Base chain ID?

The Base mainnet chain ID is 8453, and Base Sepolia testnet is 84532.

Can I use the public Base RPC endpoint for production?

No, the public endpoint is rate-limited and not recommended for production. Use a third-party provider for reliable access.

Do all RPC providers support Base Sepolia?

Not all providers support testnets. Check the provider's documentation to confirm Base Sepolia support.

What is the difference between shared and dedicated nodes for Base?

Shared nodes are used by multiple customers and may have variable performance. Dedicated nodes are single-tenant, providing consistent performance and more control.

How do I choose between HTTPS and WebSocket endpoints?

Use HTTPS for standard requests and WebSocket for real-time subscriptions or event listening.

Does OnFinality support Base?

Yes, OnFinality provides RPC endpoints for Base and Base Sepolia. Visit our Base network page for more information.