Server-rendered summary

HOTBOT Meme Coin Risk Analysis & Trade Setup

Exact Solana mint: 8nnaeWCw8mUypcGAgbmSuzAT85uWx4UN12adDrMhXrGF

HOTBOT Risk Analysis and Trade Setup Summary

Overall Health Score: Hot Bot has an Overall Health Score of 36 out of 100.

Rug Risk Rating: Hot Bot has a low Rug Risk Rating. This reflects collected on-chain evidence and is not a safety guarantee.

HOTBOT Rug-Pull Risk Analysis

  • Three top wallets linked by direct token transfers collectively control ~10.5% of supply. All three have holding periods under 2 days, and two are classified as actively accumulating — coordinated exit risk is real.
  • Sell volume exceeded buy volume by ~1.75x over the past ~3.4 hours, with large-wallet sellers driving ~57% of sell-side volume. Price has fallen 22–28% across the past 1–6 hours.
  • At under 2 days old, HOTBOT has no demonstrated durability; all holder behaviour, cluster intent, and whale positioning must be treated as provisional with very low long-term confidence.

HOTBOT Risk and Health Signals

  • Both mint and freeze authorities are inactive with no dormant extension warnings, removing the two most dangerous unilateral supply/freeze controls.
  • Six whale wallets showed net positive inflows over the past 24 hours with a combined net whale inflow of ~12.7M tokens in the last day, suggesting some large holders are still adding rather than exiting.
  • On-chain data explicitly flags a worsening decentralisation trend; concentration is increasing, not spreading, which is structurally unfavourable for price stability.

HOTBOT Holder Distribution

Holder concentration: The top 10 non-pool holders control 26.4% of supply.

Is HOTBOT Safe?

  • Creator risk check: no blacklist match found.
  • Wash-trading check: no suspicious activity detected.
  • Copycat check: no match detected.
  • Sellability check: a sell route was observed.
  • Smart-money check: no tracked participation was observed.

HOTBOT Trade Setup, Entry Levels and Targets

Support and resistance context: 3 support areas and 2 resistance areas were identified from 1h market candles; nearest support: 0.0006311330206538118; nearest resistance: 0.0007692041813007058; Levels derived from 42 1h candles (~41 hours) of pool price history via swing-point clustering. History is too short for repeated-touch levels; some levels are derived from volume-profile nodes and the window high/low (lower confidence, untested). Heuristic zones, not trading advice..

HOTBOT Price and Market Data

Assessment: HOTBOT is a ~1.7-day-old PumpSwap memecoin with a $718K market cap and $93K in DEX liquidity (~13% of market cap), which is thin but not critically so for a token this age. Both mint and freeze authorities are revoked, removing the two most dangerous structural controls. However, the holder base is heavily concentrated: the top 20 non-pool wallets control ~35% of supply, 14 "whale" wallets collectively hold ~30.6%, and a confirmed cluster of three wallets (2XfpD…WZ3, 6D4EW…KAo, [redacted wallet]) sharing direct token transfers controls a combined ~10.5% — all with holding periods under two days. Sell pressure is acute: over the most recent ~3.4 hours, sell volume outpaced buy volume by roughly 1.75x ($47M vs $27M in token units), large-wallet sellers (>0.1% balance) drove ~57% of sell volume, and the price has shed ~22–28% over the past 1–6 hours. The token is too young (under 2 days) to judge structural durability, and the decentralisation trend is worsening; caution is warranted despite the clean authority profile.

Reason: Active large-wallet sell dominance, a confirmed coordinated cluster holding ~10.5% of supply, a worsening decentralisation trend, and under 2 days of history combine to make this a structurally fragile, high-risk token with no demonstrated durability.

Report limitations

  • This automated snapshot can be wrong, incomplete, or become outdated as on-chain and market conditions change.
  • It is informational analysis, not financial advice or a guarantee that the token is safe.

Read the MemeAssist methodology for evidence sources, scoring and known constraints.

Analyzed: