The problem Snappy solves

Snappy is an infoFi agent powered by XMTP's decentralized protocol, designed to simplify social media research—privately and instantly.

Problems Snappy Solves
Decentralized Messaging Network: Snappy uses XMTP for end-to-end encrypted, user-owned conversations.

Social Media Complexity: Skip APIs and JSON—just ask Snappy for insights like “Show me top tweets of @shanemac”

Tool Fragmentation: Combines AI, social analytics, and Web3 tools into one wallet-connected interface.

Use Cases:

• Social Media Intelligence: Analyze influencers, tweets, and followers.
• Web3 Community Building: Identify valuable members and partners.
• Networking: Find and research relevant industry contacts.

Snappy turns crypto Twitter noise into actionable insights—securely, simply, and smartly.

This is just a prototype, we are aiming to combine this with messaging in our existing flagship product TrendSage: https://trendsage.vercel.app for projects to securely DM KOLs and collaborate.

Challenges I ran into

One of the main challenges I faced was integrating XMTP protocols initially. I struggled to get started, but the example code provided in the XMTP GitHub repository was extremely helpful. By referring to those, I was able to understand the basics and gradually build a working implementation.

Another issue was message synchronization. Messages originated solely within the app were not consistently syncing with xmtp.chat, especially when using agent wallets/inboxes alongside user wallets/inboxes. This inconsistency made debugging a bit tricky.

To resolve this, I spent more time studying the XMTP documentation and experimenting with different configurations. Over time, I gained a better understanding of how the protocol handles conversations and identities, which helped me improve reliability and consistency in message syncing.