A Telegram-native AI agent system automating the IDO launch lifecycle for an on-chain deal infrastructure platform — from curator onboarding through to post-TGE monitoring. Powered by OpenClaw and Hermes.


What Problem It Solves

The IDO launch process was entirely manual. Account managers and ops were spending significant time collecting project information, updating trackers, sending meeting recaps, chasing action items, and monitoring on-chain contracts — all by hand. With 3–5 parallel sales running at once, this wasn't scalable. CurAgent replaces that manual overhead with a structured, bot-driven workflow that handles the entire lifecycle automatically.


Who It's For


How It Works

CurAgent is architected as three purpose-built bots, each with a distinct role, user base, and permission scope. A single monolithic bot would create security and permission problems — curators would be exposed to internal ops discussions, and navigation across 7 feature domains would become unwieldy. Three scoped bots solves this cleanly.

The agent layer is powered by OpenClaw for orchestration and Hermes (NousResearch) for reasoning — the same personal CTO stack used across all of Ella's products, applied here to an internal ops context.

Bot 1 — Internal command center Handles the internal team workflow. New project initialization, IDO tracker management, kickoff deck generation, meeting recap processing via Fireflies API, timeline and conflict management across parallel sales, and post-mortem report generation. AM and ops only — curators never access this bot.

Bot 2 — Curator-facing interface The only bot curators directly interact with. Runs a guided intake wizard across 8 structured sections — project basics, token details, vesting, sale mechanics, compliance, marketing, operations, and design. Once intake is complete, activates as a live FAQ assistant grounded in per-project knowledge: questionnaire answers, meeting notes, kickoff deck, and any documents shared in the group. Project data is fully isolated — answers about one project never bleed into another.

Bot 3 — On-chain monitoring Polls ETH and ARB deposit contracts every 15 minutes during active sale periods. Fires threshold alerts to the ops channel when a contract exceeds a defined balance. Generates a pre-filled transaction reference artifact for ops review — read-only, never executes or signs anything. Posts a daily digest of all active contracts and their balances.

Hard constraint across all three bots: CurAgent surfaces data and generates artifacts only. All money-related actions remain 100% human-operated.