<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Logs on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/logs/</link>
    <description>Recent content in Logs 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/logs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EIP-7708: ETH Transfer Logs in Glamsterdam</title>
      <link>https://blazed.sh/blog/posts/eip-7708-eth-transfer-logs/</link>
      <pubDate>Wed, 09 Sep 2026 08:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/eip-7708-eth-transfer-logs/</guid>
      <description>&lt;p&gt;An ERC-20 deposit watcher can filter &lt;code&gt;Transfer&lt;/code&gt; logs. A native ETH deposit watcher has more work to do: top-level transaction values are visible in transaction objects, but transfers inside contract execution normally need a trace. Individual contracts may emit their own payment events, but there is no universal native-ETH event on mainnet today.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://eips.ethereum.org/EIPS/eip-7708&#34;&gt;EIP-7708&lt;/a&gt; proposes that missing event. Qualifying nonzero ETH transfers between different accounts emit a log from a fixed system address. Indexers can then use familiar log filters for those movements instead of tracing every transaction solely to discover value transfers.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
