<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Erc20 on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/erc20/</link>
    <description>Recent content in Erc20 on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 23 Jul 2026 07:19:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/erc20/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ERC-20 Transfer Webhooks: Build One in 50 Lines on a Co-located Node</title>
      <link>https://blazed.sh/blog/posts/erc20-transfer-webhooks/</link>
      <pubDate>Thu, 23 Jul 2026 07:19:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/erc20-transfer-webhooks/</guid>
      <description>&lt;p&gt;The most requested webhook on Ethereum is also the simplest to describe: tell my backend when this token moves, or when this wallet receives funds. Exchange deposit flows, payment confirmations, treasury alerts and airdrop trackers are all variations of that one sentence. Search for an ERC-20 transfer webhook and you will mostly find hosted products that charge per delivered event, but underneath every one of them sits a primitive small enough to read in one sitting: an &lt;code&gt;eth_subscribe&lt;/code&gt; log filter on one side and an HTTP POST on the other.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
