<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/f24d934fbc9848a6ba23bec1c43e2cde&quot; frameborder=&quot;0&quot; width=&quot;1894&quot; height=&quot;1420&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1420</height><width>1894</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1420</thumbnail_height><thumbnail_width>1894</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/f24d934fbc9848a6ba23bec1c43e2cde-66d765e71b955830-full.jpg</thumbnail_url><duration>371.722</duration><title>End-to-End Wallet Tracker Setup with Quicknode Streams 🟩</title><description>Hey team, I successfully deployed the streams-based wallet tracker locally and verified real-time ingestion with live EVM activity. I navigated some constraints by reusing a single stream and using a public Solana endpoint as a placeholder. The app is address-driven, so I suggest we improve the empty state to prompt users to add a wallet for activity visibility. I also encountered some issues with Prisma migrations that were resolved by adjusting the env file location. If useful, I can turn these notes into a small readme.</description></oembed>