40 posts.
Seven BNB Smart Chain RPC providers compared on current pricing, free tiers and measured limits. BSC's 0.45 s blocks and shallow state make log caps and archive the deciding factors. Pricing checked October 6, 2026.
Read →Seven OP Mainnet RPC providers compared on current pricing, free tiers and measured limits, including log caps, tracing and pre-Bedrock history. Pricing checked October 6, 2026.
Read →Seven Solana RPC providers compared on current pricing, free tiers and measured limits. Per-method weights, getProgramAccounts rules and history depth decide the bill. Pricing checked October 6, 2026.
Read →Seven Arbitrum One RPC providers compared on current pricing, free tiers and measured limits. Arbitrum's 0.3 s blocks change what log caps and archive mean. Pricing checked October 3, 2026.
Read →Seven Ethereum RPC providers compared on current pricing, free tiers and measured limits, with what 30M and 100M requests a month cost on each. Pricing checked October 3, 2026.
Read →Seven Polygon PoS RPC providers compared on current pricing, free tiers and measured limits, including why Polygon's shallow default state matters. Pricing checked October 3, 2026.
Read →How to use Cronos EVM over JSON-RPC — chain ID 25, ~0.42 second blocks with instant finality, a 10,000-block eth_getLogs cap, historical state pruned after ~100 blocks, and no debug or trace namespace.
Read →How to query Babylon Genesis over RPC and LCD — CometBFT 0.38.22 on chain bbn-1, ~9.6 second blocks, 68 validators, blocks filled with finality signatures, why tx_search refuses ranges, and the pruning floor that gave three different answers in six calls.
Read →How to query HyperEVM over JSON-RPC — chain 999, ~1s blocks, a near-fixed 0.1 gwei base fee, a 1000-block and 1 MiB eth_getLogs cap, no WebSocket, and the one that will cost you money: state methods accept a block number and then ignore it, so historical reads silently return the latest state.
Read →How to query Neutron over JSON-RPC — CometBFT 0.38 on chain neutron-1, why there is no numeric chain ID, the header fields that disappeared in 0.38, a tx_search that times out instead of answering, a pruning floor that differs between nodes, and a block time that measured 7s this week against a 2s baseline.
Read →How to connect to Arbitrum One over JSON-RPC — chain ID 42161, why the block gas limit is a sentinel value, what safe and finalized actually mean here, zero priority fees, and where archive reads stop working.
Read →How to connect to Ethereum Classic over JSON-RPC — chain ID 61, proof-of-work still live, why blocks carry no baseFeePerGas, what carries over from Ethereum unchanged, and where historical reads stop working.
Read →How to connect to Gnosis Chain via JSON-RPC — the dual-token model (xDAI + GNO), DAI-bridged stablecoin gas, consensus via GPOS, and what makes it different from other EVM chains. Includes production setup and fee optimization.
Read →How to connect to Polygon zkEVM via JSON-RPC — the Type 1 prover, equivalence testing, bridge architecture, and what makes it different from every other zkEVM. Includes production setup and fee optimization.
Read →How to connect to Tron via JSON-RPC and HTTP — TRC-20 token transfers, smart contract interaction, energy and bandwidth, and how to pick a Tron endpoint for production use.
Read →How to connect to Solana via JSON-RPC — the methods you'll use daily, commitment levels, WebSocket subscriptions, account parsing, and how to pick an endpoint that handles real traffic.
Read →Everything you need to connect to Ethereum via RPC — the methods you'll actually use, how to set up viem and ethers, WebSocket vs HTTP, archive access, and how to pick an endpoint that won't fall over under load.
Read →Public endpoints, provider free tiers, keyless access — 'free RPC' covers four very different deals with very different failure modes. A field guide to the real limits, from someone who operates against all of them.
Read →Bitcoin Core's JSON-RPC can't tell you an address's balance — it has no address index. Here's the gap, the three ways to fill it, and how to pick a Bitcoin RPC provider.
Read →The write path trips up more developers than the read path. Here's why you sign transactions locally and broadcast them with eth_sendRawTransaction — with the full build-sign-send flow.
Read →Linea is a Consensys zkEVM L2 where standard eth_* just works — but gas estimation and finality have Linea-specific behavior worth knowing. A developer's guide.
Read →eth_call's third parameter lets you override balances, code, and storage before simulating. Here's how state overrides work, with a reproducible example and real use cases.
Read →Ankr's free public RPC is everywhere — until production. Here's where the public endpoints stop, how Ankr's API-credit pricing works, and when flat-rate is the better fit.
Read →Robinhood Chain is a new Arbitrum Orbit L2 built for tokenized stocks and real-world assets. Here's how to connect, what stays standard EVM, and the one thing that isn't.
Read →eth_syncing returns false when a node is fully synced — and also when it hasn't started syncing. That trap, plus how to really tell if an RPC node (your own or a provider's) is at the chain tip: compare block height to a reference, check block-timestamp freshness, and the Solana equivalents (getHealth, catchup). A liveness check is not a freshness check.
Read →A naive retry loop turns a brief blip into an outage. Here's how to retry RPC calls correctly: exponential backoff with jitter, knowing which calls are safe to retry, and failing over across providers — with copy-paste examples in viem, ethers, and web3.py.
Read →Mantle looks like a standard EVM L2 until two things trip you up: gas is paid in MNT, not ETH, and data availability runs through EigenDA instead of Ethereum calldata. Here's what that means for your RPC calls, plus the Mantle endpoints to point at.
Read →On an Ethereum L2, a single component decides the order your transaction lands in and how fast it confirms: the sequencer. Here's what it actually does, why nearly every rollup runs a centralized one today, and what that means when you're reading L2 state over RPC.
Read →Polling eth_getLogs in a loop is the slow, brittle way to watch contract events. eth_subscribe pushes logs to you over WebSocket the instant they're mined. Here's how to build a subscription that filters correctly, survives reconnects, and never silently misses an event.
Read →Solana's high block rate makes RPC rate limiting a constant production concern — 429s show up under load and break bots, indexers, and frontends. Here's why they happen, how to handle them with backoff and batching, and how to size your endpoint so they stop happening at all.
Read →dRPC and Alchemy take opposite paths to the same metered-compute billing model — one decentralized and pay-as-you-go, one a polished managed platform. Here's how they actually differ, where each wins, and why the deciding question is whether your workload fits compute-unit pricing at all.
Read →Zora is an OP Stack L2 built for mints, and minting traffic is bursty in a way that punishes public RPC endpoints. Here's what you need to build on Zora in 2026 — chain ID 7777777, Superchain finality, the public-node trap, and the query patterns for reading mints at scale.
Read →A WebSocket subscription that silently drops is worse than no subscription at all — you keep running, but events vanish into the gap. Here's how to build reconnect logic that detects the drop, backs off, re-subscribes, and backfills the missed events so your indexer never loses a log.
Read →BNB Smart Chain is one of the busiest EVM chains on the planet, but its public RPC endpoints fold under any real load. Here's what you need to connect reliably in 2026 — chain ID, finality, the public-node trap, and the query patterns that matter at BSC's transaction volume.
Read →Every RPC provider limits you, but they don't agree on what a limit even is. One caps requests per second, another meters compute units, a third deducts API credits. Here's how the three models work, why the same workload costs differently on each, and how to estimate your own number.
Read →They share a name and a parent company, but Polygon PoS and Polygon zkEVM are two separate chains — different chain IDs, different gas tokens, different security models, and very different liquidity. Here's how to tell which RPC endpoint your app actually needs.
Read →Every blockchain tutorial says 'connect to an RPC endpoint' and then moves on. Here's what one actually is, what the URL means, how a request works, and when you need a provider — in five minutes.
Read →QuickNode bills in API credits: methods cost up to 50x each other, marketplace add-ons stack on top, and overage is automatic. Real monthly costs for a wallet, a DEX, and an indexer — with the math to forecast yours.
Read →Eight Base RPC providers compared on current pricing, free tiers and measured limits, with the monthly cost of 30M and 100M requests on each. Pricing checked October 3, 2026.
Read →Alchemy now bills $0.525 per million Compute Units, and debug_traceTransaction uses 1,000 CU/s of throughput. Current method costs and three priced workloads.
Read →