<?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: ChainHint</title>
    <description>The latest articles on DEV Community by ChainHint (@chainhint).</description>
    <link>https://dev.to/chainhint</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%2F3869979%2Fe10d7609-e659-4185-accc-7d1476da0b8d.png</url>
      <title>DEV Community: ChainHint</title>
      <link>https://dev.to/chainhint</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/chainhint"/>
    <language>en</language>
    <item>
      <title>How I Traced the Bybit $1.5B Hack On-Chain (And Built a Tool to Do It)</title>
      <dc:creator>ChainHint</dc:creator>
      <pubDate>Thu, 09 Apr 2026 20:58:57 +0000</pubDate>
      <link>https://dev.to/chainhint/how-i-traced-the-bybit-15b-hack-on-chain-and-built-a-tool-to-do-it-36ia</link>
      <guid>https://dev.to/chainhint/how-i-traced-the-bybit-15b-hack-on-chain-and-built-a-tool-to-do-it-36ia</guid>
      <description>&lt;p&gt;Every time a major crypto hack happens — Bybit ($1.5B), Ronin ($625M), WazirX ($235M) — the funds move on-chain in plain sight. The entire trail is public. Anyone can see it on Etherscan.&lt;/p&gt;

&lt;p&gt;But &lt;em&gt;following&lt;/em&gt; that trail across multiple hops, multiple chains, through mixers and bridges? That requires tools that cost $30K+/year.&lt;/p&gt;

&lt;p&gt;So I built ChainHint.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it does
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Multi-hop BFS fund tracing across 11 EVM chains + Bitcoin, Solana, TON&lt;/li&gt;
&lt;li&gt;Real-time OFAC sanctions screening via Chainalysis integration&lt;/li&gt;
&lt;li&gt;Mixer &amp;amp; Tornado Cash detection&lt;/li&gt;
&lt;li&gt;Entity resolution across 3.9M+ labeled addresses (CEX, DEX, bridges, known exploiters)&lt;/li&gt;
&lt;li&gt;AI-powered incident reports with MITRE ATT&amp;amp;CK threat mapping&lt;/li&gt;
&lt;li&gt;Wallet monitoring with automated alerts&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Frontend&lt;/strong&gt;: Lovable (React)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Backend&lt;/strong&gt;: Supabase (PostgreSQL + Edge Functions + pg_cron)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tracing&lt;/strong&gt;: Moralis BFS + Bitquery GraphQL V2&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Entity data&lt;/strong&gt;: Arkham Intel API + Dune Analytics + dawsbot/eth-labels&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;AI reports&lt;/strong&gt;: Claude API (Haiku) with MITRE ATT&amp;amp;CK prompting&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Payments&lt;/strong&gt;: NOWPayments (no Stripe in Ukraine)&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The hard parts
&lt;/h2&gt;

&lt;p&gt;The trickiest problem was entity resolution at scale. We ingest labeled addresses from multiple sources, normalize them (BTC addresses can't be lowercased — learned that the hard way), and resolve them in real-time during tracing.&lt;/p&gt;

&lt;p&gt;The second hard part: Arkham's API has aggressive rate limits. We ended up with a 3s timeout per request, max 10 concurrent lookups, and careful error distinction between timeouts and network errors.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;Free tier available at &lt;a href="https://chainhint.com" rel="noopener noreferrer"&gt;https://chainhint.com&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Happy to answer questions about the forensics approach, the BFS algorithm, or the Supabase edge function architecture.&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>security</category>
      <category>cryptocurrency</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
