Token tracking
Under 🟢 Robinhood Coins, the bot can track any ERC-20 token on Robinhood Chain, Mosh launch or not. Set a token up in Buy Settings.
Buy and sell alerts
Section titled “Buy and sell alerts”🟢🟢🟢🟢🟢🟢$SYM BUY 🏅 Mosh Verified💵 $312 (0.1 ETH)🪙 356K SYM bought👤 0xabcd…1234 · ⬆️ Position +40%📍 Uniswap v4🧭 via Universal Router📊 Price $… · 📈 MC $… · 💎 FDV $… · 💱 24h Vol $… · 👥 Holders …- Emoji row: one emoji for every $50 bought (you can change the step), up to 40.
- Buyer line: shows 🤖 for a Mosh agent, 🆕 New holder for a first buy, or how much their position grew.
- Venue and route: which pool the trade hit (or a split across pools) and how it was routed.
- Buttons: 📈 Chart, 🛒 Buy, 🔎 Txn and 𝕏 Post to X.
Sell alerts look the same in red and are off by default.
What doesn’t get posted
Section titled “What doesn’t get posted”- Buys under the group’s minimum (default $10).
- Round trips and arbitrage where the token only passes through.
- Hops inside a multi-pool route. A trade split across pools posts once, at its full size.
- A buy by an agent wallet the group already gets agent alerts for.
Busy moments
Section titled “Busy moments”If a token gets more than 4 buys in the same group within 10 seconds, they’re combined into one post: N $SYM buys in 10s, with the largest marked 🐳.
Big buys
Section titled “Big buys”Buys over the big-buy threshold (default $1,000) use the group’s big-buy image or video instead of the normal one.
🏅 Mosh Verified
Section titled “🏅 Mosh Verified”The label means the bot checked on-chain that a real Mosh bundle launched this exact token. It follows the token back to its bundle and checks that the bundle came from a Mosh factory and names this token as the one it launched.
A copycat token with the same name and ticker won’t pass. If a check fails, the bot checks again later (about every 6 hours).
The label appears on buy alerts and on /price. Admins can hide it per token in Buy Settings.
Burn alerts
Section titled “Burn alerts”Any transfer of the token to the dead address (0x…dEaD) or the zero address.
🔥🔥🔥🔥🔥$SYM BURN🔥 1.2M burned · $…👤 0xabcd…1234💀 Dead address🧮 Total burned …💫 Circulating …Minimum burn to post defaults to $1. On by default for the first token a group adds.
Price, holders, burns and recap
Section titled “Price, holders, burns and recap”| Command | Card |
|---|---|
/price or $TICKER |
Price, 24h change, MC, FDV, liquidity, volume, holders, burned |
/holders |
Holder count with 24h, 7d and 30d change, concentration |
/burn |
Total burned, 24h and 7d burns |
/card |
24-hour recap image for X |
Market cap and FDV
Section titled “Market cap and FDV”- FDV = price × total supply.
- MC = price × circulating supply. For Mosh tokens, circulating excludes what the agents hold (in wallets and liquidity), the Pons locker and the bundle contract. This matches how mosh.trade counts it.
Where the numbers come from
Section titled “Where the numbers come from”| Data | Source | Refreshed |
|---|---|---|
| Price | mosh.trade, then DexScreener, then the last trade the bot saw | Every 30 s |
| 24h change, liquidity, volume, buy/sell counts | DexScreener | Every 60 s |
| Holders (Mosh tokens) | BPEPE’s Mosh indexer | Every 60 s |
| Holders (other tokens) | The bot’s own count from on-chain transfers | Hourly |
| Burned total | On-chain balances of the dead and zero addresses | Every 5 min |
| Trades, burns, deposits | Robinhood Chain, live | As they happen |