Where LocusBot is, and where it's going.
The beta: a free test with the real group that built the track record the launch was based on.
Beta launched to the group
doneBundle/rug screen, cost safeguards, risk disclaimer, and the new card format (pair + platform + icons) all live.
Infra reliability pass
doneThe crash-recovery + always-on setup work from launch day is complete, now running as a registered Windows Scheduled Task, not a manually-launched window.
/todayscalls + a faster, honestly-unfiltered /trending
done"locus todays calls" shows every call made so far today without scrolling back through the chat. /trending was redesigned around real feedback that it was too slow. It no longer applies the main scan's filters at all (by design: it's a quick pulse-check on the day's narrative, not a shortlist) and now returns in ~15s instead of taking a while to land.
Alert card always sends in full, even with a banner
doneTokens with a DexScreener banner used to get a shortened, truncation-prone caption instead of the full stat card. Now the banner is purely decorative: the same complete card (with chart/tweet buttons) always follows it as its own message, matching the no-banner case exactly.
/start rewritten + cooldown tightened to 5s
done/start now gives a real introduction to what the bot actually watches/checks, plus plain-language notes that commands run one at a time chat-wide and that there's a cooldown between requests. That cooldown itself was tightened, now that the daily cap carries more of the anti-abuse job on its own.
Paste a CA, no command needed
doneAny message containing a real-looking contract address (pasted alone, or just mentioned mid-sentence) now gets auto-scanned exactly like typing /ca. No "/ca" or "locus ca" required at all.
Chat bot: ask it anything with "locus ..."
done"locus what are liquidity pools"-style questions now get a real, personality-driven answer instead of "Unknown command," built to deliberately skip the expensive X-search tool (plain per-token cost only) and gated by the same cooldown/daily-cap as every other paid command.
Cost investigation
doneTraced a real spend spike to an internal setting that had crept up over time, and brought it back down. Also switched on live per-call usage logging, since there was previously no way to see real spend short of the provider's own dashboard.
Real launchpad identification
doneAlerts now name the actual platform a token launched on, not just wherever it currently trades.
Weekly Calls redesign
doneThe Weekly Calls view has been rebuilt.
Permanent audited call ledger + win rate
doneA permanent, audited call ledger and a true win-rate calculation are built and tested. The public win-rate command itself is temporarily off by request, but the underlying tracking keeps running regardless.
Peak tracking now checks every pool, not just the busiest
doneTracking a token's peak price now checks every real trading pool it has instead of only the busiest one, closing a gap that could undercount a token's true peak.
/rescan now names what's actually new
done/rescan now tells you exactly which tickers were already sent versus which ones are new, instead of re-listing everything every time.
Alert card reordered
doneThe alert card's layout was reordered so its narrative read and its verdict present in a clearer sequence.
Existing commands updated
doneNo new commands added. The focus was on making the commands we already have better instead of adding more.
Legal/liability framing
doneLegal and liability framing is in place, going beyond the in-bot risk disclaimer the free beta started with.
Low market cap tokens
doneCoverage now includes lower market cap tokens, so Locus can catch plays even earlier.
LocusBot is out of beta and open to everyone. Everything here landed before launch. The theme going forward: every future filter change gets justified by a real backtest, not a hunch, and existing features get tightened before anything new is added.
Public launch
doneLocusBot is live on the open market. Anyone can join on Whop, not just the original beta group.
Upgrade bundle/rug detection to a trustworthy paid API
doneThe current DIY on-chain check is real and live, but two paid options are already scoped: one ships an actual bundle-detection flag directly, and another gives fuller holder-map data across both chains. Either would tighten a known edge case in the current check further.
Backtest the call ledger for the most profitable setups
doneEvery tracked call already has a called price, a verified peak, and an outcome. This turns that into the actual evidence base for every filter decision going forward, including whether the two liquidity tiers perform differently. Confirmed staying: the two-tier system itself isn't in question, only what the audited data says to tighten or loosen next.
A direct feedback channel to the dev
doneA feedback button/flow so users can flag a bad call, request a feature, or report something confusing directly, instead of that only happening informally in chat. Feeds the same backtest-and-adjust loop above.
What's being worked on now that Locus is live.
Always-on hosting
top priorityLocus will be moving to always-on hosting.
A call ledger that verifies itself
top priorityToday every call is checked by hand. The goal is a ledger that verifies each call on its own, with nobody needing to be there to check it.
Continue tuning filters from the audited report
recurringThe backtest process, continued: mcap tiers, liquidity bands, and the bundle-concentration band all keep moving as real outcome data accumulates.
Keep tuning the command cooldown/daily cap against real demand
first tuning pass done, watchingHow it works today: every command that costs money to run (scans, pasted contract addresses, "locus ..." questions) is limited two ways: a short cooldown between requests, and a daily cap on how many can run in total. Commands also run one at a time across the whole chat, so no one person can flood the queue.
First pass, done: the cooldown was cut to 5 seconds, and the daily cap took over more of the job of stopping abuse. Normal use feels faster, while spamming still hits a ceiling.
Next pass: watch the first 2-4 weeks of post-launch usage, then adjust. Two newer features count against the same cap (auto-scanning any pasted contract address, and chat-bot questions), so people may reach it sooner than before. If normal use keeps hitting the cap, it goes up. If it's getting abused or costs spike, it gets tighter.
Where Locus goes from here.
Locus in multiple groups at once
futureRight now Locus runs in one group. Later, it will run in several groups at the same time.
Scale to 1,000+ users
Become the most-used, top-picked memecoin scanner, built on an audited track record, not a pitch.