<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flashbots on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/flashbots/</link>
    <description>Recent content in Flashbots on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 08:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/flashbots/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Flashbots Bundle Not Included: Why a Profitable Bundle Doesn&#39;t Land</title>
      <link>https://blazed.sh/blog/posts/flashbots-bundle-not-included/</link>
      <pubDate>Sun, 13 Sep 2026 08:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/flashbots-bundle-not-included/</guid>
      <description>&lt;p&gt;A bundle hash is an acknowledgement, not a receipt. A successful simulation is a result for a chosen state and execution environment, not a reservation in the next block. Keeping those two distinctions in your logs makes a missing bundle much easier to investigate.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://docs.flashbots.net/flashbots-auction/advanced/troubleshooting&#34;&gt;Flashbots troubleshooting guide&lt;/a&gt; identifies several common causes: a transaction reverts, the incentive is insufficient, a competing bundle changes the opportunity, delivery is late, or the block producer does not use the relevant builder path. More than one can apply to the same attempt.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
