HotCoinLabReal-time crypto movers
Telegram

Smart alert event record

COOKIE Crypto Price Surge Reason and Alert Record

Review the COOKIE price surge detected on Bithumb KRW-COOKIE: 5M +2.65%, evidence, cause status and follow-up outcomes.

View all alerts
BithumbCookie DAOCOOKIE/KRW · KRW-COOKIE
Reversed

Ticker-matched multi-venue observation

KRW-COOKIE · upward move detected

This section explains why the alert fired. Each price-change figure appears only once in the table above.
Signal confidence99/ 100

Price changes at alert time

Upward move detected

Each value compares the alert-time price with the price at the stated time earlier. A missing value means it could not be calculated at the alert time and will not be backfilled.
5 min2.65% up
30 min0.72% up
1 hour6.61% up
4 hours15.51% up
24 hours8.40% up
Alert price₩15.49
Recorded current price₩14.84
Highest price since alert₩15.77
Actual price move since alert4.20% down
Trading activity29/100
Price-move strength100/100

Why the alert fired

Market-data evidence

  • The price movement over the previous 5 minutes prompted the alert. The exact figure is shown in the table above.
  • Real trading activity was also strong at the same time, so this was not a price-only move.
  • The current record also shows observations from 2 exchanges. These may include information added after the first alert.

External-cause status

Surge cause analysis (beta)

BetaSurge Cause Analysis
Verdict: Volume-driven surge with no news (estimated)Confidence: Low

No confirmed official catalyst.

No confirmed news catalyst. The move appears volume- and liquidity-driven; a short squeeze is unverified without derivatives data.

  • Direct newsNot identified
  • 추가 확인 필요:
  • A direct news catalyst
  • Derivatives position data
  • On-chain data such as wallet inflows

Automated data-driven verdict (beta). Not investment advice; surges without sufficient evidence are honestly labeled “no confirmed news catalyst”.

Follow-up outcomes

Recorded 5m, 15m and 60m outcomes

5M2.78% downRecorded
15M…Pending
60M…Pending

Event timeline

5 recorded state updates

  1. Reversed

    Alert status update

    The status changed to “Reversed”. This change was added to the same alert record.
  2. Retracing

    Alert status update

    The status changed to “Retracing”. This change was added to the same alert record.
  3. Retracing

    Alert status update

    The status changed to “Retracing”. This change was added to the same alert record.
  4. Surge confirmed

    Alert status update

    The status changed to “Surge confirmed”. This change was added to the same alert record.
  5. Observing

    Alert status update

    The status changed to “Observing”. This change was added to the same alert record.