WireTap

Demo

About

The problem it solves ### Automatically snap up new tokens from social accounts you follow — before regular schmucks even know they’ve launched. --- # Introducing WireTap by *The Firm* In the current market, token launches are dominated by insider cliques, high-speed snipers, and tightly coordinated back-room cabals. The average trader is left chasing the crumbs - relying on questionable social algorithms to surface opportunities long after the real action is over. If you’re not in the right Telegram, on the right X thread, at exactly the right time (and preferably on a T1 connection), you’ve already missed it. **WireTap changes that.** --- ### 💼 How WireTap Works Developed internally at The Firm’s Walls Street H.Q., WireTap links token deployments directly to the social accounts behind them. By combining real-time on-chain monitoring with a proprietary database mapping wallet addresses to Farcaster and X accounts, WireTap allows everyday users to automatically buy into token launches the moment they happen—not hours later, not after the pump, and not after the Chairman’s nephew already tripled his stack. You choose the social accounts you trust. WireTap watches them for you—around the clock, across time zones, *no Adderall required.* **The moment a token launches, WireTap executes. **No refresh wars. No Discord detective work. No CAs whispered over martinis in Midtown. --- ### 💼 Initial Release We’re launching with Clanker for our MVP, indexing tokens deployed via Clanker 3.1, and rapidly expanding to support: - Additional deployers - On-chain behavior detection - Real-time CA extraction from social feeds --- ### 💼 Still Early WireTap puts early access on autopilot. It’s The Firm’s first release, and far from the last. “Getting in early” starts today: https://wiretap.thefirm.biz

How it's made

Challenges we ran into ### Time constraints and product evaluation You plan, you architect, you build. Everything has to happen fast, with little time to reflect or test if what you’re building is right. As the UI came together, particularly later on, we had real concerns over onboarding friction, whether we needed an explainer carousel, and whether the data we’d indexed for the Discover page was useful at all. A growing list of other improvements became obvious, but time constraints made it almost impossible to pause and change course. ### Technical compromises We had to balance building for a Buildathon while keeping things stable and resilient. Sometimes we got that balance wrong- like adding tracing to the real-time token deployer indexer instead of just making it fast. We also under-anticipated complexity. Just because you think your scope is narrow and hackathon-friendly doesn’t mean it actually is. ### Third parties Our product has external dependencies: Clanker (on-chain token deployments), Neynar (Farcaster user data & mapping creators to social accounts), and Glider (trade execution layer). We were the first users of Glider’s API - and ran into bugs and nuances at every step, from session key accounts to trade execution. Their team were incredibly supportive and we worked through it all together; it’s the start of a strong partnership. Third parties also create product constraints - Glider doesn’t support smart wallet signatures, which meant our app couldn’t support smart wallets. You'll notice some entirely unused Zerodev kernal session key account logic in the codebase. ### Late scares The front trifecta of external wallet, connection library + and wagmi became a quadfecta with the introduction of minikit—it was often hard to isolate where a platform-specific (i.e. Farcaster frame) issue was coming from. 24 hours before submission, we thought our SIWE cookie-based auth wouldn’t work inside the Farcaster iframe (turned out to be cookie security settings).