dapps.co
Invest in communities on a bonded curve
About
The problem it solves **Monetizable, Secure Messaging for Web3 Communities** **Our XMTP-powered DM system solves three critical problems for our 16,000+ users:** 💰 **Creator Monetization:** Traditional platforms don't let creators monetize their time. Our paid DM feature enables users to set ETH-based pricing for direct messages (configurable rates for followers/following/others), creating a new revenue stream. Messages cost 0.001 ETH by default, with automatic refunds if recipients don't reply within 7 days. **🔒 True Privacy:** Unlike centralized platforms that can access your messages, we provide end-to-end encryption via XMTP protocol. Your conversations are truly private - not even we can read them. **⚡ Seamless Web3 UX:** Users enjoy instant messaging with optimistic UI updates, real-time delivery via SSE, media sharing, and mobile-first design. The crypto complexity is hidden - it feels like WhatsApp but with Web3 superpowers. **🎯 Real Impact: Our existing community of crypto enthusiasts, traders, and creators can now:** Monetize their expertise through paid consultations Have private, secure conversations about sensitive trades Build micro-economies around exclusive access Bridge Web2 social experiences with Web3 financial rails This transforms messaging from a cost center into a revenue-generating, privacy-first communication layer for the onchain economy.
How it's made
Challenges we ran into **SSE Authentication in Production:** The biggest hurdle was implementing real-time messaging. XMTP handles message delivery, but we needed instant UI updates. Our Server-Sent Events initially failed in production due to CORS and cookie domain mismatches between frontend and API. *Solution:* We discovered that using our existing Vite proxy (/api/sse/messages) instead of direct API calls eliminated CORS issues entirely. The proxy automatically handles authentication cookies, making SSE work seamlessly. **Optimistic Messaging Performance:** Users expected instant message sending, but waiting for XMTP confirmation created 200-500ms delays. *Solution:* We implemented true optimistic updates - messages appear instantly in the UI while XMTP processes them in the background. We carefully handled message deduplication to prevent flickering when server confirmations arrive. **Mobile Layout Complexity:** Making conversations work perfectly on both desktop browsers and mobile apps required different positioning strategies (fixed vs relative) while maintaining the same codebase. *Result: *A messaging experience that feels native across all platforms while leveraging XMTP's decentralized infrastructure.