<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rpc on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/rpc/</link>
    <description>Recent content in Rpc on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Aug 2026 10:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/rpc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Alchemy vs Infura vs QuickNode: Free Tier RPC Latency Against a Co-located Node</title>
      <link>https://blazed.sh/blog/posts/free-tier-rpc-latency-vs-colocated-node-benchmark/</link>
      <pubDate>Mon, 10 Aug 2026 10:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/free-tier-rpc-latency-vs-colocated-node-benchmark/</guid>
      <description>&lt;p&gt;Our &lt;a href=&#34;https://blazed.sh/blog/posts/ethereum-rpc-latency-benchmark&#34;&gt;August RPC latency benchmark&lt;/a&gt; measured nine keyless public endpoints and left two gaps that the post named itself: no account-backed endpoint was tested, and our own node was not in the table. This study closes both.&lt;/p&gt;&#xA;&lt;p&gt;We registered accounts with Alchemy, Infura and QuickNode, measured their endpoints against six keyless ones, added our own production node from two separate vantage points, and added a dimension the first run missed entirely: what happens when you stop sending one request at a time and start sending the burst a strategy actually sends when a block lands.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ethereum RPC Latency in 2026: IPC vs WebSocket vs Remote Providers, Measured</title>
      <link>https://blazed.sh/blog/posts/ethereum-rpc-latency-benchmark/</link>
      <pubDate>Sat, 01 Aug 2026 14:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/ethereum-rpc-latency-benchmark/</guid>
      <description>&lt;p&gt;Every RPC provider sells latency and almost nobody publishes a distribution. You get a marketing average, occasionally a p95 on a status page, and never the methodology. We wrote a &lt;a href=&#34;https://blazed.sh/blog/posts/ipc-vs-http-websocket-ethereum-rpc&#34;&gt;transport comparison&lt;/a&gt; last June that leaned on illustrative ranges because we had not measured them ourselves, and that has bothered us since. So this post measures instead: nine public Ethereum endpoints, up to 300 samples each, percentiles rather than means, a race between three subscription feeds to see who learns about a new block first, and a separate benchmark of what a JSON-RPC round-trip costs when there is no network in the path at all.&lt;/p&gt;</description>
    </item>
    <item>
      <title>BLAZED.sh Now Has a Free Tier: 1M RPC Credits and a Live Script on the Node</title>
      <link>https://blazed.sh/blog/posts/free-tier-launch/</link>
      <pubDate>Fri, 31 Jul 2026 09:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/free-tier-launch/</guid>
      <description>&lt;p&gt;Until now the only way to find out what running your code on the node actually feels like was to pay for the Beta plan or poke at the &lt;a href=&#34;https://demo.blazed.sh&#34;&gt;live demo panel&lt;/a&gt;. That was the wrong shape for a product whose whole pitch is a latency difference you have to measure yourself. So there is now a free plan: one always-on JavaScript script, running on a host with a fully synced Ethereum mainnet node, with 1,000,000 RPC credits a month. No card, no trial clock.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Infura Alternatives for High-Volume Ethereum RPC in 2026</title>
      <link>https://blazed.sh/blog/posts/infura-alternative/</link>
      <pubDate>Fri, 10 Jul 2026 10:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/infura-alternative/</guid>
      <description>&lt;p&gt;Infura is where most teams start, and for good reason: it is reliable, well documented, and free to begin with. The trouble usually shows up later, at scale, when the same properties that made it easy start to constrain you. If you are reading this, you have probably already hit a &lt;code&gt;429 Too Many Requests&lt;/code&gt;, watched a compute-unit bill climb, or realized your whole app depends on a single provider. This post is an honest look at the alternatives in 2026, what to weigh when choosing one, and where each option actually fits. Provider plans, quotas, and pricing change frequently; treat this as a qualitative snapshot as of July 2026 and check official docs before buying or migrating.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Alchemy Alternatives for Ethereum RPC in 2026</title>
      <link>https://blazed.sh/blog/posts/alchemy-alternative/</link>
      <pubDate>Fri, 10 Jul 2026 09:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/alchemy-alternative/</guid>
      <description>&lt;p&gt;Alchemy is often the first serious upgrade a team makes after outgrowing a free endpoint, and it earns that position: the SDK is pleasant, the enhanced APIs remove real work, and the free tier is generous enough to carry a project a long way. The reasons people start shopping for an alternative are rarely about quality. Usually it is the compute-unit meter climbing faster than traffic, the slow realization that the enhanced APIs which saved time have also become hard to leave, or a latency-sensitive workload that would rather sit next to the node than call across the internet to reach it. This post is an honest look at the alternatives in 2026, what to weigh, and where each one actually fits. Provider plans, compute-unit weights, and enhanced-API pricing change often; treat this as a qualitative snapshot as of July 2026 and confirm against official docs before you migrate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cheapest Ethereum RPC in 2026: How to Actually Pay Less</title>
      <link>https://blazed.sh/blog/posts/cheapest-ethereum-rpc/</link>
      <pubDate>Thu, 09 Jul 2026 08:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/cheapest-ethereum-rpc/</guid>
      <description>&lt;p&gt;Search for the cheapest Ethereum RPC and you get a list of headline prices, which is the one number that reliably fails to predict your invoice. The honest answer is that the cheapest provider depends on the shape of your traffic, and that the sticker price is only the floor. What actually decides the bill is how a model prices the heavy parts of your workload: traces, wide log queries, large responses, and bursts. This post breaks down where the real cost hides, which model is cheapest for which workload, and how to compare them without guessing. Plans and weights move often; treat the specifics here as a qualitative snapshot as of July 2026 and confirm against official docs before you commit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>QuickNode Alternatives for Ethereum RPC in 2026</title>
      <link>https://blazed.sh/blog/posts/quicknode-alternative/</link>
      <pubDate>Wed, 01 Jul 2026 09:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/quicknode-alternative/</guid>
      <description>&lt;p&gt;QuickNode is a strong product, and most teams that pick it are happy for a while. It is fast, it covers a long list of chains, and its add-on marketplace lets you switch on traces, token APIs, or a mempool feed without standing up your own infrastructure. The reasons people start shopping for an alternative are rarely about quality; they are about where the model stops fitting. Usually it is the credit meter climbing faster than traffic, an edge function bumping into its runtime ceiling, or the realization that the workload really wants to live next to the node rather than call across the internet to reach it. This post is an honest look at the alternatives in 2026, what to weigh, and where each one actually fits. Provider plans, credit weights, and add-on pricing change often; treat this as a qualitative snapshot as of July 2026 and confirm against official docs before you migrate.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ethereum RPC Pricing Explained: Compute Units vs Credits</title>
      <link>https://blazed.sh/blog/posts/ethereum-rpc-pricing-compute-units-vs-credits/</link>
      <pubDate>Wed, 24 Jun 2026 09:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/ethereum-rpc-pricing-compute-units-vs-credits/</guid>
      <description>&lt;p&gt;Ethereum RPC pricing is harder to compare than it looks. Two providers can advertise similar headline numbers and still bill you wildly differently, because the unit being counted is not the same. This post breaks down the pricing models you will actually meet, shows how to estimate a monthly bill for each, and explains where a bundled-credit plan fits. Provider plans and weights change frequently; treat the numbers here as a qualitative snapshot as of June 2026 and confirm against official docs before you commit.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What &#34;missing trie node&#34; Means and Why You Need an Archive Node</title>
      <link>https://blazed.sh/blog/posts/missing-trie-node/</link>
      <pubDate>Tue, 23 Jun 2026 10:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/missing-trie-node/</guid>
      <description>&lt;p&gt;You ran a query against a slightly older block, and instead of an answer you got this:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;missing trie node 2bca...e91f (path ) state 0x2bca...e91f is not available&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Or a nearby historical-query failure such as:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;header not found&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;code&gt;missing trie node&lt;/code&gt; specifically means the state needed to answer your query is unavailable. &lt;code&gt;header not found&lt;/code&gt; can also come from a bad block reference, an unsynced endpoint, or provider retention behavior, so treat it as a related symptom rather than the exact same error. This post explains what the state trie is, why a full node prunes it, exactly when you will trip missing historical state, and how to fix it; at the end we look at why an archive node, ideally one you do not have to operate, is the only real cure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>eth_getLogs Block Range Limits: Why Your Queries Fail and How to Fetch 1,000 Blocks at Once</title>
      <link>https://blazed.sh/blog/posts/eth-getlogs-block-range-limit/</link>
      <pubDate>Sat, 20 Jun 2026 14:30:11 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/eth-getlogs-block-range-limit/</guid>
      <description>&lt;p&gt;If you have ever indexed an ERC-20, backfilled a DEX, or built a liquidation monitor, you have met this error:&lt;/p&gt;&#xA;&lt;div class=&#34;highlight&#34;&gt;&lt;pre tabindex=&#34;0&#34; class=&#34;chroma&#34;&gt;&lt;code class=&#34;language-text&#34; data-lang=&#34;text&#34;&gt;&lt;span class=&#34;line&#34;&gt;&lt;span class=&#34;cl&#34;&gt;query returned more than 10000 results&#xA;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Or one of its many cousins: &lt;code&gt;Exceed maximum block range: 5000&lt;/code&gt;, &lt;code&gt;eth_getLogs is limited to a 1024 block range&lt;/code&gt;, or a silent &lt;code&gt;query timeout&lt;/code&gt;. They all mean the same thing: your &lt;code&gt;eth_getLogs&lt;/code&gt; call asked for more than the provider is willing to return in one request. This post explains why those limits exist, lists where the common providers draw the line, and shows a chunking strategy that fetches any range reliably. At the end we look at why running your code on the node sidesteps most of the pain entirely.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Unlocking the Blockchain: A Beginner&#39;s Guide to Ethereum Nodes</title>
      <link>https://blazed.sh/blog/posts/ethereum_nodes/</link>
      <pubDate>Mon, 21 Jul 2025 15:51:00 +0200</pubDate>
      <guid>https://blazed.sh/blog/posts/ethereum_nodes/</guid>
      <description>&lt;p&gt;Ethereum runs on a network of thousands of computers called nodes. These nodes store blockchain data, validate transactions, and let external software (wallets, dApps, bots) talk to the network. If you&amp;rsquo;ve ever wondered what&amp;rsquo;s actually running behind MetaMask or your favorite DeFi app, it&amp;rsquo;s nodes, and this post explains how they work.&lt;/p&gt;&#xA;&lt;h2 id=&#34;what-is-ethereum-and-why-does-it-matter&#34;&gt;What Is Ethereum and Why Does It Matter?&lt;/h2&gt;&#xA;&lt;p&gt;Ethereum is a decentralized platform for running smart contracts, programs that execute automatically based on coded rules, and decentralized applications (dApps) built on top of them. DeFi, NFTs, and most of the interesting stuff in crypto runs on Ethereum.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
