Building on Base? What to check in an RPC provider

Base is a fast network: it adds a new block every 2 seconds, and its Flashblocks feature confirms transactions every 200 milliseconds. That changes four things about RPC: reads need the pending tag, streams produce far more notifications, history counts as archive after about four minutes, and block ranges should be sized in time, not blocks. A provider for Base should support Flashblocks, predictable streaming costs, archive access and a private submission path.

At one block every 2 seconds, Base produces 43,200 blocks a day, against about 7,200 on Ethereum mainnet. As of October 20, 2026, DefiLlama shows $6.16 billion of TVL on the chain, $5.07 billion in stablecoins and about $29.7 billion of DEX volume over the past 30 days. Money moves at that speed too, and the RPC layer is where it shows up first: in latency, in streaming volume and in the bill for reading history.

Why is Base so busy?

The current numbers, from DefiLlama on October 20, 2026:

• TVL: $6.16 billion.
• Stablecoins: $5.07 billion in circulation, which means a steady flow of payments and transfers on top of trading.
• DEX volume: $29.7 billion over 30 days, roughly $1 billion a day on average.
• Block cadence: 2-second blocks, split into 10 Flashblocks of 200 ms each (Base docs).

Daily volume and block time together set the shape of the traffic. Trading bots, payment flows and automated agents all react to state that changes five times a second, so they poll, subscribe and submit constantly.

What does Base need from an RPC provider?

Four things change when blocks come every 2 seconds.

1. Reads need the pending state. A normal latest read shows the last sealed block, up to 2 seconds old. Flashblocks let apps read the in-progress block with the pending tag on methods such as eth_call, eth_getBalance and eth_getTransactionCount, updated roughly every 200 ms. The catch is that a preconfirmed state is not final, and the provider's node has to run the Flashblocks module for it to work.
2. Streaming adds up quickly. On Chainstack, each WebSocket push counts as one request. A newHeads subscription on Base is about 43,200 notifications a day. A stream of full Flashblocks, one every 200 ms, is about 432,000 a day, roughly 13 million request units a month, more than the Developer plan includes.
3. History ages fast. On Chainstack, an EVM request 127 or more blocks behind the tip is billed as archive. On Ethereum that is about 25 minutes of history. On Base it is about 4 minutes. A job that walks one day of Base block by block makes 43,200 calls, which is 86,400 request units at the archive rate. Run it daily for a month and you reach roughly 2.6 million, about an eighth of the 20 million included in the $49 Growth plan. Archive access starts on paid plans.
4. Range queries need real limits. eth_getLogs caps differ by plan, and a block range means something different on a 2-second chain. A 100-block range is about 3 minutes of Base. A 10,000-block range is about 5.5 hours. Indexers should size their ranges in time, not in blocks.

Submission matters as well. Base is a sequencer chain, and its transactions are not broadcast to a public mempool, so there is no public mempool to watch. What helps is a short, private submission path, and that is a provider feature, not something your code can add.

One change is coming: Base's Denim upgrade replaces Flashblocks with canonical blocks every 200 milliseconds, on Base Sepolia on October 21, 2026 and on Base Mainnet in November 2026 (planned). The time figures above then shrink tenfold, and Flashblocks subscriptions give way to newHeads and logs.

How does Chainstack support Base?

Chainstack runs Base on Global Nodes, starting at $0 a month, with full and archive modes, HTTPS and WebSocket endpoints, and Flashblocks on mainnet. Chainstack's own docs put confirmation at about 300 to 500 ms on a Flashblocks-enabled endpoint, compared with about 2,000 ms on a standard one, once network latency is included. The pending reads and the newFlashblockTransactions, pendingLogs and newFlashblocks subscriptions are available on those endpoints.

Pricing is flat: 1 request unit per full request and 2 per archive request. Debug and trace calls are a flat 2. The Developer plan includes 3M request units a month at 25 requests per second. Growth is $49 for 20M and 250 requests per second. The eth_getLogs range is 100 blocks on the Developer plan and 10,000 on paid plans.

For transaction submission, Optimized Submission routes eth_sendRawTransaction through a private, optimized path. It is available on Base mainnet Global Nodes on every plan, including the free one. New Global Nodes include it by default, and it can be disabled in the node's Add-ons tab. Teams that want isolated capacity can deploy a Dedicated Node in full or archive mode (Pro plan and above), which is billed monthly and not per request. For steady, high-volume streams, the Unlimited Node add-on (Growth plan and above) replaces per-request billing with a flat fee tied to a requests-per-second tier. Chainstack Self-Hosted runs Base nodes in your own environment. Chainstack holds SOC 2 Type II and ISO 27001 certifications and covers 70+ networks from one account.

Chainstack for Base at a glance

• Endpoints: HTTPS and WebSocket, full and archive modes
• Flashblocks: Base mainnet, pending reads and Flashblocks subscriptions
• Pricing: 1 request unit per full request, 2 per archive request, debug and trace calls 2
• Plans: Developer: 3M request units, 25 requests per second. Growth: $49, 20M, 250 requests per second
• Submission: Optimized Submission on Global Nodes (every plan, on by default)
• Capacity: Dedicated Node (Pro plan and above), Unlimited Node add-on (Growth plan and above), Self-Hosted
• Certifications: SOC 2 Type II and ISO 27001

How to choose an RPC provider for Base

Choose a Base RPC provider on five checks: it serves Flashblocks reads and streams, bills streaming predictably, prices archive and log queries predictably, offers a private submission path, and can move you to dedicated or self-hosted capacity when shared nodes stop being enough. Chainstack covers all five on Base: Flashblocks reads and subscriptions, a flat 1 request unit per call (2 for archive, debug and trace), Optimized Submission on every plan, Dedicated Nodes from the Pro plan and Self-Hosted in your own environment, with SOC 2 Type II and ISO 27001. Start on a free Global Node, count your notifications and backfill calls, and move to the Unlimited Node add-on or a Dedicated Node when the bill needs a fixed number.