Practical writing for developers building on multi-chain RPC. Tutorials, benchmarks, and honest takes on the infrastructure landscape.
Hemi is an OP Stack chain whose EVM can read Bitcoin. Measured: 12 s blocks, a 252 wei base fee, a transfer costing ~0.00000018 ETH (88% of it L1 data), the hVM Bitcoin precompiles in practice, ~20 min to finalized, full archive and eth_getLogs limits.
Read →ApeChain is an Arbitrum Orbit L3 that pays gas in APE. Measured: ~0.9 s blocks, a 101.7 gwei base fee in APE, transfers estimating 21,169 gas, ~14 min to safe and ~24 min to finalized, full archive, and how wide eth_getLogs can go.
Read →Abstract is a ZK Stack rollup where most transactions come from smart accounts. Measured: 0.58 s blocks, a flat 0.045 gwei gas price, transfers using ~95k gas, a 10,000-log result cap, ~3.8 h to finalized, and full history from block 1.
Read →Between August 25 and October 6, 2026, ten of 110 chains we scanned stopped producing blocks for 10 minutes or more. TAC was down 10.6 days, Neutron 77.75 hours, Cosmos Hub 24.8 hours, Cronos 17 hours. The full list, the method, and the raw data.
Read →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 →MegaETH runs 1 s EVM blocks over ~10 ms mini-blocks. Measured: a 10-billion gas limit, transfers estimating 63,349 gas, a bogus eth_feeHistory oldestBlock, ~32 min to finalized, and what works over standard RPC.
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 →Ronin became an OP Stack layer 2 in May 2026. Measured: 2 s blocks, a fixed 20 gwei base fee, a 200-block getLogs cap, ~23 min to finalized, and no pre-migration history.
Read →Kava runs an EVM beside a Cosmos SDK chain. Measured: 5.7 s blocks, instant finality, a 10,000-block getLogs cap, ~100 blocks of state, archive routing.
Read →Aurora is an EVM running as a contract on NEAR. Measured: 0.6 s blocks, instant finality, a 2^53 gas limit, zero cumulativeGasUsed, NEAR receipt hashes.
Read →eth_getBlockByNumber('finalized') ranges from instant to four hours across 62 EVM chains; five give no answer, one returns genesis. The table and code.
Read →opBNB is an OP Stack L2 settling to BNB Smart Chain, with 250 ms blocks. Measured finality, fees, the 50,000-block getLogs cap and a stale-finality trap.
Read →Shibarium runs Polygon PoS's Bor and Heimdall with BONE for gas. Measured block time, finality, getLogs range and archive, plus the quirks it inherits.
Read →Katana (chain ID 747474) is an OP Stack L2 with ZK proofs and 1-second blocks. Measured finality, fees, getLogs limits, archive access and code.
Read →Since October 2025, Kusama balances live on Asset Hub, not the relay chain. What the relay RPC still serves, finality, runtime upgrades and code.
Read →We tested every keyless public RPC endpoint listed for 65 EVM chains. 49% of HTTP endpoints answered correctly, 52% of WebSockets streamed, and one was 4.4 million blocks behind. The numbers, the failure modes, and how to pick one.
Read →What a dedicated blockchain node buys you over a shared RPC endpoint, what it costs in 2026 (from $1,000/mo on GetBlock, ~$1,279/mo for Ethereum on Chainstack, custom quotes elsewhere), and the four signals that mean you need one.
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 →Axelar is a Cosmos SDK network for cross-chain interoperability — token bridging and General Message Passing across dozens of blockchains. Its RPC is CometBFT (Tendermint) RPC, not eth_*. Here's what Axelar actually does, the RPC you connect to, how GMP works under the hood, and how to read the chain.
Read →Boba Network mainnet RPC endpoint and chain ID 288 — the EVM optimistic rollup where smart contracts can call off-chain compute and APIs. Live fee numbers, block cadence, what carries over from Ethereum, and what to verify.
Read →PulseChain mainnet RPC endpoint and chain ID 369 — the EVM-compatible full-state fork of Ethereum. Gas in PLS, ~10-second blocks, what carries over from Ethereum, what doesn't, and live fee numbers.
Read →Optimism (chain ID 10) is both a mature optimistic rollup — 2-second blocks, ETH gas, fault proofs live since 2024 — and the origin of the OP Stack, the codebase behind Base, Zora, opBNB, Unichain, and Soneium. The developer map: what the two-layer fee model means for gas estimation, why traces are uneven there, and how everything you learn on OP Mainnet carries across the family.
Read →Receipts show that a transaction succeeded; traces show what it did. How trace_transaction and trace_filter expose internal calls, where the Parity trace namespace actually works in 2026 (we probe it weekly — it's 11 of 54 EVM chains), and the param quirks that trip people up.
Read →-32601, -32000, code 3, HTTP 429 — every RPC error belongs to one of three families: try another node, fix your request, or accept the chain's answer. A field guide with real error payloads.
Read →sn_* methods land on every paid SwiftNodes plan: token balances with metadata, multi-address portfolios, transactions with decoded logs, allowance audits, full block bundles — each one call, each counted as one request.
Read →Add protect=1 to your SwiftNodes Ethereum endpoint and your transactions skip the public mempool entirely — routed through a private relay that shields them from sandwich bots and rebates backrun value to you.
Read →Moonbeam ceased operations on July 31, 2026. We watched it go dark from the infrastructure side. Chains end in three distinct ways — full shutdown, successor migration, and rebrand — and each breaks your code differently.
Read →A light client verifies Ethereum's headers against the validator set on your laptop — turning any untrusted RPC endpoint into a verified one. How sync committees work, what Helios-style clients actually do, and their honest limits.
Read →Every eth_call answer is just something a server told you. eth_getProof returns state with a Merkle proof you can check yourself — the primitive behind bridges, light clients, and trust-minimized reads.
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 →Story's IP Assets, licenses, and derivative trees are ordinary contract state on an EVM chain. A hands-on guide to indexing the IP graph with eth_getLogs, eth_call, and a WebSocket.
Read →Story rebranded to the DATA Network in June 2026, migrating $IP to $DATA and pivoting to AI training data. Here's what actually changed on-chain (almost nothing) and what to update anyway.
Read →Since Pectra, a plain wallet address can carry code. What EIP-7702 delegation actually does, how to spot it over RPC, and why 'no code means EOA' is no longer a safe assumption.
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 →Every time you move funds to an L2 you use a bridge — but 'bridge' hides several very different mechanisms with very different risk. A plain explainer of how they actually work.
Read →85 earlier posts, grouped by what they are about. Each group shows its four newest; the tag list above reaches the rest.
eth_getLogs, eth_call, tracing, batching, subscriptions — how each one behaves on public nodes.
Rollups, finality, sequencers and where an L2 actually keeps its data.
Connecting to specific networks, and the quirks that break integrations silently.
How RPC is billed across providers, and what the invoice does not show.
Self-hosting, sync and archive behaviour, latency, retries and failover.
