<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Mev on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/mev/</link>
    <description>Recent content in Mev on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 21 Jul 2026 14:26:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/mev/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Arbitrage Basics: How to Build a Crypto Arbitrage Bot</title>
      <link>https://blazed.sh/blog/posts/how-to-build-crypto-arbitrage-bot/</link>
      <pubDate>Tue, 21 Jul 2026 14:26:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/how-to-build-crypto-arbitrage-bot/</guid>
      <description>&lt;h2 id=&#34;welcome-back-to-arbitrage-basics&#34;&gt;Welcome Back to Arbitrage Basics&lt;/h2&gt;&#xA;&lt;p&gt;This is part three of our arbitrage series, and it is the one where the math starts running. &lt;a href=&#34;https://blazed.sh/blog/posts/tri_arbitrage&#34;&gt;Part one&lt;/a&gt; built a triangular arbitrage checker for Uniswap V2 and walked through pairs, reserves, and the exact &lt;code&gt;getAmountOut&lt;/code&gt; formula. &lt;a href=&#34;https://blazed.sh/blog/posts/graph_theory_arbitrage&#34;&gt;Part two&lt;/a&gt; generalized detection with graph theory: tokens become vertices, pairs become edges weighted by negative log exchange rates, and Bellman-Ford surfaces profitable cycles of any length as negative cycles. Both posts end at the same place, a function that takes fresh reserves and returns candidate trading loops.&lt;/p&gt;</description>
    </item>
    <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>
    <item>
      <title>What Is ePBS? Ethereum&#39;s Enshrined Proposer-Builder Separation (EIP-7732), Explained</title>
      <link>https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders/</link>
      <pubDate>Mon, 20 Jul 2026 08:12:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/epbs-eip-7732-searchers-builders/</guid>
      <description>&lt;p&gt;ePBS stands for enshrined proposer-builder separation. It is the change, specified in &lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-7732&#34;&gt;EIP-7732&lt;/a&gt;, that moves Ethereum&amp;rsquo;s block-building marketplace out of trusted off-chain middleware and into the protocol itself. Today, a validator who wants a professionally built block hands the deal to a relay, an unpaid third party that both sides simply have to trust. Under ePBS the builder&amp;rsquo;s signed bid goes into the beacon block directly, payment is enforced by consensus, and the relay&amp;rsquo;s trust role disappears. It ships as the headline consensus change of Glamsterdam, the hard fork after Fusaka, currently targeted at mainnet in the second half of 2026.&lt;/p&gt;</description>
    </item>
    <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>
