Base Infrastructure:
build for the next generation of applications on Base

Base RPC is a JSON-RPC API endpoint for Base, Coinbase's Ethereum Layer 2 built on the OP Stack. Through a Base RPC endpoint you read blocks and balances, broadcast transactions, subscribe to logs and run debug traces — the same interface you already use on Ethereum.

BlockPI exposes two Base RPC endpoints: https://base.blockpi.network/v1/rpc/{api_key} for Base mainnet (chain ID 8453), and https://base-sepolia.blockpi.network/v1/rpc/{api_key} for Base Sepolia (chain ID 84532). Drop in your BlockPI API key, and the endpoints are live — no waitlist, no approval step.

Yes. BlockPI supports Base mainnet (chain ID 8453) and Base Sepolia testnet (chain ID 84532), with the same method coverage on both. You build against Sepolia, switch the RPC URL to mainnet, and ship — without changing your code or redeploying your indexer.

Base mainnet uses chain ID 8453 and Base Sepolia uses chain ID 84532. Both use ETH as the native gas token. Blocks land roughly every 2 seconds, and the chain settles back to Ethereum mainnet through the OP Stack.

In MetaMask, open Add network → Add a network manually and enter: Network name Base, Default RPC URL your BlockPI endpoint (https://base.blockpi.network/v1/rpc/{api_key}), Chain ID 8453, Currency symbol ETH, Block explorer URL https://basescan.org. For the testnet use chain ID 84532 and the Sepolia endpoint.

BlockPI supports the full Ethereum eth_ method set on Base over HTTPS plus WebSocket subscriptions for eth_subscribe logs and pending transactions, eth_newFilter and eth_getFilterChanges. Batch (multi-call) requests are supported on both Base mainnet and Sepolia, with identical method coverage.

Base is EVM equivalent, so your existing Ethereum and OP Stack code deploys as-is. Hardhat, Foundry and Remix all work, and your libraries — viem, ethers.js and web3.py — connect to BlockPI's Base endpoint without any adapter.

On BlockPI's shared Base RPC, rate limits scale with the RU package you buy — Free runs at 20 requests per second, the $49 Elementary package at 1,000 requests per second, and the $299 Premium package at 2,500 requests per second — so a spike on mint day does not mean rewriting your retry logic. Need the cap removed entirely? A BlockPI dedicated node ships with no QPS limit and no method limit, with typical capacity above 10,000 requests per second and sub-20 ms responses.

BlockPI runs Base RPC across six global regions with a median response time around 2 ms and a 99.99% uptime measured over a rolling 90-day window. Requests are routed to the nearest healthy region automatically, so a regional outage does not turn into failed user transactions.

Point your project at the BlockPI Base Sepolia endpoint (chain ID 84532), deploy with the same artifacts you use on mainnet, and fund the account from the official Base Sepolia faucet. When you are ready, swap the RPC URL to the BlockPI mainnet endpoint — methods, request shape and response format are identical.

Yes. Every BlockPI Base node ships with archive state from genesis and full-range eth_getLogs, plus the full debug_ and trace_ surface: debug_traceTransaction, debug_traceCall, debug_traceBlockByNumber and debug_traceBlockByHash. Use it for reconciliation, historical backfills, transaction simulation and indexer bootstrapping.

Inside the BlockPI dashboard you can monitor Base request volume by chain — mainnet and Sepolia shown separately — track RU consumption against your package balance, and set hard spend caps plus alert thresholds.

BlockPI bills Base RPC in RU (request unit) packages rather than a recurring monthly subscription. Each method carries an RU weight — eth_chainId is 5 RU, eth_getLogs is 50 RU (larger eth_getLogs payloads cost more), and on the $49 Elementary package (500M RU) the blended rate is about $0.10 per 1M RU. Formula: cost = requests × method RU × rate. On a complete 2M-request workload, BlockPI fits inside the $49 Elementary package, while the same workload costs $173 on QuickNode and $167 on Alchemy (archive eth_getLogs tier).

A dedicated Base node on BlockPI runs on a flat, predictable monthly fee with custom pricing based on your region and workload. The Standard plan starts at $900/month; BlockPI dedicated node provides archive from genesis, debug and trace methods, your choice of US, EU or APAC, and a direct engineer support channel.

Migration is a one-line change: replace your provider URL with https://base.blockpi.network/v1/rpc/{api_key} in your client config. Because BlockPI is JSON-RPC compatible, viem, ethers.js, web3.py and your indexer connect without code changes.

Yes. BlockPI dedicated Base nodes include private endpoints, cross-region failover and a 99.99% service-level agreement (SLA). Support is engineer-led rather than ticket-only: Standard and Customized dedicated-node plan customers get a direct channel and an assigned contact, so a stuck sync or a replay issue reaches someone who can restart the node.