MEXC Alert Performance
Central outcome tracking for alerts that actually fired through the MEXC router, followed by the broader Momentum Entry research ledger. This keeps phone alerts separate from general scanner rows.
Loading results…
How this is measured
Central fired alerts starts from mexc-alert-ledger.json, so it only tracks alerts that actually went through the final router. It joins those alerts to existing paper outcome ledgers and does not fetch fresh market data. Momentum Entry research below is broader: it tracks scanner ideas whether or not they became a phone alert.
| Category | Total | Matched | Open | Closed | Worked | Failed | Hit rate |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
| Alerted | Symbol | Action | Outcome | Entry | Stop | Target | Current R | Max R | Match | Note |
|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||
Read this first
Open and pending rows are visible but excluded from the target-hit denominator. A tiny closed sample can look ugly or brilliant by accident; treat the table as a review queue until more alerts mature.
Momentum Entry research model
The broader model assumes a paper review entry at the scanner’s entryRef when the signal appeared. It checks later MEXC candles for target hit, invalidation hit, max run-up, max drawdown and 1h/4h/1d/3d/7d returns. It does not include fees, slippage, position sizing, leverage, or whether you personally opened the chart in time.
| Setup | Total | Target | Stop | Open | Hit rate | Avg max R | Avg 7d |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
| Time | Symbol | Setup | Outcome | Entry | Stop | Target | Current R | Max R | 1d | 3d | 7d | BTC |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||||||