<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Webhooks on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/webhooks/</link>
    <description>Recent content in Webhooks 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/webhooks/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>
    <item>
      <title>Building Real-Time Ethereum Event Notifications with BLAZED.sh</title>
      <link>https://blazed.sh/blog/posts/ethereum-webhook-tool-blazed/</link>
      <pubDate>Mon, 25 Aug 2025 14:00:00 +0000</pubDate>
      <guid>https://blazed.sh/blog/posts/ethereum-webhook-tool-blazed/</guid>
      <description>&lt;p&gt;Applications that react to blockchain events in real time need low-latency infrastructure, especially when dealing with event filters that return large datasets (liquidation monitors, DEX aggregators, cross-chain bridges).&lt;/p&gt;&#xA;&lt;p&gt;In this tutorial, we&amp;rsquo;ll build a webhook service that monitors Ethereum events and sends notifications to configured URLs, using BLAZED.sh&amp;rsquo;s co-located Ethereum node access for a local path to chain data.&lt;/p&gt;&#xA;&lt;h2 id=&#34;understanding-blazedshs-architecture&#34;&gt;Understanding BLAZED.sh&amp;rsquo;s Architecture&lt;/h2&gt;&#xA;&lt;p&gt;BLAZED.sh is optimized for Ethereum applications that require consistent low latency and predictable costs. Instead of calling a remote gateway across the public internet, your service runs on the same host as a fully synced Ethereum node and connects today over the node&amp;rsquo;s local WebSocket endpoint (&lt;code&gt;ws://eth:8545&lt;/code&gt;).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
