<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: George Merabishvili</title>
    <description>The latest articles on DEV Community by George Merabishvili (@george_merabishvili_0dc15).</description>
    <link>https://dev.to/george_merabishvili_0dc15</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3904483%2Ff76c9ced-8ba6-4cb0-9985-052ebe66fe6c.png</url>
      <title>DEV Community: George Merabishvili</title>
      <link>https://dev.to/george_merabishvili_0dc15</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/george_merabishvili_0dc15"/>
    <language>en</language>
    <item>
      <title>Crypto Arbitrage Alerts (arb-signal.com)</title>
      <dc:creator>George Merabishvili</dc:creator>
      <pubDate>Wed, 29 Apr 2026 13:51:52 +0000</pubDate>
      <link>https://dev.to/george_merabishvili_0dc15/crypto-arbitrage-alerts-arb-signalcom-1p2b</link>
      <guid>https://dev.to/george_merabishvili_0dc15/crypto-arbitrage-alerts-arb-signalcom-1p2b</guid>
      <description>&lt;p&gt;One thing that made a huge difference for me was switching from REST polling to WebSockets. I’m parsing order books from the nearest servers, and the latency improvement was massive — not just faster, but way less load on the exchanges. Also interesting: running everything on Linux (Ubuntu) felt noticeably more stable than Windows for long-running connections. Biggest unexpected challenge wasn’t the arbitrage logic — it was payments. Integrating them cleanly (especially as a non-US founder) took more time than the trading side.&lt;/p&gt;

</description>
    </item>
  </channel>
</rss>
