<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mev-Infrastructure on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/mev-infrastructure/</link>
    <description>Recent content in Mev-Infrastructure on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 20 Jul 2026 13:47:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/mev-infrastructure/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>What Is a MEV Searcher? Infrastructure, Latency, and Whether You Need Your Own Node</title>
      <link>https://blazed.sh/blog/posts/what-is-a-mev-searcher/</link>
      <pubDate>Mon, 20 Jul 2026 13:47:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/what-is-a-mev-searcher/</guid>
      <description>&lt;p&gt;If you have read anything about MEV, you have met the word &amp;ldquo;searcher&amp;rdquo;. It is the working job title of everyone actually running the bots: the arbitrageur closing a price gap between two DEX pools, the liquidator watching health factors on a lending market, the operator whose bundle landed one block ahead of yours. The term gets used constantly and defined rarely. This post fixes that. It covers what a MEV searcher actually is, where they sit in Ethereum&amp;rsquo;s block-building pipeline, which strategies they run, what their infrastructure looks like in practice, and then the question almost everyone asks next: do you need to run your own node to compete?&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
