<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Paas on BLAZED.sh Blog</title>
    <link>https://blazed.sh/blog/tags/paas/</link>
    <description>Recent content in Paas on BLAZED.sh Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 25 Aug 2025 14:00:00 +0000</lastBuildDate>
    <atom:link href="https://blazed.sh/blog/tags/paas/index.xml" rel="self" type="application/rss+xml" />
    <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>
