kaalketu
Smart Moves, Synced Minds, Built on Signal
Demo
About
The problem it solves ⚔️ The Problem It Solves Web3 doesn't suffer from a lack of alpha. It suffers from a lack of execution. Every day, real opportunities — stealth launches, new tokens, power-user strategies — get lost in noise. Communities discover signals, but can’t act: Alpha dies in Discord scrolls Coordination is scattered across tools No system rewards action or filters bullshit Everyone’s talking. No one’s moving. 🐉 What We Built: KaalKetu KaalKetu is a war-engine for alpha hunters. It’s a real-time coordination protocol where: Alpha is detected from token activity, mentions, or drops Signal is voted by real wallet rep, not fake hype Actions (Quests) are generated instantly — tweet, stake, raid, share Wallets track contribution → earn leaderboard status, rep, and rewards Communication flows through XMTP + Discord without switching tabs 💥 Why This Matters KaalKetu does what no Telegram group, Discord DAO, or Excel raid tool ever could: It brings coordination, reward, and execution under one roof — natively. It’s not another tool, It’s where Web3 armies launch ops.
How it's made
Challenges we ran into 🧱 Challenges I Ran Into 🔗 1. Dealing with Multiple Web3 APIs We had to integrate Dexscreener, Coingecko, XMTP, Base RPC, and Discord API — all with different auth models, rate limits, and data formats. Solution: Mapped out each API’s requirements. Where paid keys were needed (like OpenAI), we replaced them with freeer LLM APIs like Grok, and wrote wrappers for unstable endpoints. 🧪 2. Testing Without Breaking the Chain Running real token validation and reputation logic on live chains (Base, Ethereum) meant high risk of failures. Solution: Created a mock chain+wallet layer in local dev to simulate transaction flow and wallet reputations before going live. 🧰 3. XMTP Confusion & Compatibility XMTP’s SDK documentation lacked clarity around versioning and "notes" vs. "messages". Wallet-to-wallet messaging failed silently. Solution: Dug through XMTP GitHub issues + Discord. Eventually patched a workaround to force the correct content type and metadata. 🚧 4. Vercel Deployment Fails Vercel randomly failed project deploys (404 errors) without useful logs. It wasted time and broke momentum. Solution: Stripped unnecessary folders like .emergent, created a vercel.json, and built a clean export structure. If it failed again, we had a backup hosting plan on hand. 💰 5. AI Tooling with Budget Limits OpenAI/Claude APIs were too expensive for constant scoring logic in alpha detection. Solution: Integrated Groq API & Gemini free api, and pre-coded fallback logic to run in-browser scoring with local LLMs or mock alpha ranking.