<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mempool on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/mempool/</link>
    <description>Recent content in Mempool on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 23 Jun 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/mempool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Why MEV Is a Latency Game: The Case for Co-located Ethereum Nodes</title>
      <link>https://blazed.sh/blog/posts/mev-latency-colocated-ethereum-nodes/</link>
      <pubDate>Tue, 23 Jun 2026 09:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/mev-latency-colocated-ethereum-nodes/</guid>
      <description>&lt;p&gt;Most write-ups about MEV focus on strategy: arbitrage, liquidations, sandwiching, backruns. Strategy is necessary, but it is not what separates a profitable searcher from a spectator. The deciding factor is usually time. By the time a pending transaction reaches you over a public RPC gateway, has been parsed, evaluated, and answered with a fresh state read across the network, the opportunity may already belong to someone closer to the chain. This post is about where those milliseconds go and how co-located node access closes the gap.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Access the Ethereum Mempool: Streaming Pending Transactions From a Co-located Node</title>
      <link>https://blazed.sh/blog/posts/how-to-access-ethereum-mempool/</link>
      <pubDate>Sat, 20 Jun 2026 14:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/how-to-access-ethereum-mempool/</guid>
      <description>&lt;p&gt;Every transaction spends a moment in limbo between &amp;ldquo;broadcast&amp;rdquo; and &amp;ldquo;mined&amp;rdquo;. That waiting room is the mempool, and it is where a lot of the interesting work in Ethereum happens: a searcher spots an arbitrage before it lands, a bot front-runs a large swap, a liquidation watcher sees the transaction that will tip a position underwater. If you want to act on a transaction before it is final, you have to read the mempool.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
