<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Trading-Bots on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/trading-bots/</link>
    <description>Recent content in Trading-Bots 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/trading-bots/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Glamsterdam Gas Repricing: What Trading Bots Need to Know</title>
      <link>https://blazed.sh/blog/posts/glamsterdam-gas-changes-trading-bots/</link>
      <pubDate>Wed, 16 Sep 2026 08:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/glamsterdam-gas-changes-trading-bots/</guid>
      <description>&lt;p&gt;A transaction that works before a gas repricing can fail afterward without any change to its calldata or contracts. Raising its outer gas limit may fix the failure. If a contract forwards a hardcoded amount of gas to the failing call, raising the outer limit may do nothing.&lt;/p&gt;&#xA;&lt;p&gt;That is the compatibility question for trading bots ahead of Glamsterdam. &lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-8037&#34;&gt;EIP-8037&lt;/a&gt; introduces separate accounting for state creation. &lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-8038&#34;&gt;EIP-8038&lt;/a&gt; raises the cost of several state-access and write operations. As of September 16, 2026, both are planned for the upgrade, not active on Ethereum mainnet.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to Benchmark Ethereum RPC for Trading Bots</title>
      <link>https://blazed.sh/blog/posts/benchmark-ethereum-rpc-trading-bots/</link>
      <pubDate>Thu, 03 Sep 2026 08:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/benchmark-ethereum-rpc-trading-bots/</guid>
      <description>&lt;p&gt;A fast response to &lt;code&gt;eth_blockNumber&lt;/code&gt; tells you how quickly an endpoint can return a small piece of data. It does not tell you when that endpoint learned about the block, whether twenty pool reads will finish before your deadline, or whether the transaction you submit will reach a builder in time.&lt;/p&gt;&#xA;&lt;p&gt;Our &lt;a href=&#34;https://blazed.sh/blog/posts/free-tier-rpc-latency-vs-colocated-node-benchmark&#34;&gt;free-tier RPC comparison&lt;/a&gt; measured request latency, burst capacity and head delivery separately. This post is the method you can apply to your own bot. It is not a new provider ranking, and it does not reuse those measurements as if they were taken today.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
