Deep Dive Analysis
Mantle (MNT)
2026-09-25 16:00 UTC · Tomas Novak · 15,000 Portfolio
PRICE
0.00
0.00
52W HIGH
1.31
1.31
DRAWDOWN
-100.0%
-100.0%
STAGE
Unknown
Unknown
🔴 AVOID — DO NOT DEPLOY
Trend-Following System · HIGH Conviction · 1 Bull / 7 Bear Factors
Bullish factors: MACD+
Bearish factors: price < 50d, 50d falling, RSI weak (1.2), falling 1m & 3m, far below high, strong bear trend (ADX 94.7), distribution (OBV down, vol ratio 0.09)
MNT Price — 1 Year
1Y Ago: 1.00
Low: 0.00
Now: 0.00
Low: 0.00
Now: 0.00
Technical Snapshot
| RSI (14) | 1.2 | ADX (14) | 94.7 |
| 50d MA | 0.31 | 200d MA | 0.00 |
| Price vs 50d | ▼ Below | Price vs 200d | ▼ Below |
| Support | 0.00 | Resistance | 0.41 |
| ATR Volatility | 4946.82%/day | Trend | SELL |
Crypto Performance Comparison
| Asset | 1 Month | 3 Months | 6 Months | 1 Year |
| MNT | -99.8% | -100.0% | — | — |
| BTC | +5.4% | +31.0% | +8.4% | -11.7% |
| ETH | +9.7% | +44.8% | +26.6% | -18.6% |
| SOL | +18.0% | +62.8% | +41.2% | -16.3% |
Trend-Following Backtest
2-year simulation of 15,000 using 50d/200d MA crossover + RSI filter. Buy when price > 50d MA (rising) + RSI 40-75. Sell on death cross or RSI > 82.
FINAL VALUE
15,000
RETURN
+0.0%
MAX DRAWDOWN
0%
Strategy vs Buy & Hold
| Asset | Strategy | Buy & Hold | Max DD | Trades | Win Rate |
| MNT | +0.0% | +0.0% | 0% | 0 | 0% |
DCA vs Lump Sum (MNT)
If you had deployed 15,000 using different timing strategies over the past year.
| Strategy | Return | Value Today |
| Lump Sum (1y ago) | +0.0% | 0 |
| DCA — 4 buys | +0.0% | 0 |
| DCA — 6 buys | +0.0% | 0 |
| DCA — 12 buys | +0.0% | 0 |
MNT Deployment Plan — 15,000 Portfolio
Analysis by Tomas Novak (Momentum / Swing Trader). If you’re managing a 15,000 crypto allocation, here’s the plan:
| Position size | 3,750 (25% of portfolio) |
| Stop loss | -0.02 (-9264.0%) |
| Target 1 | 0.00 (-100.0%) |
| Target 2 | 0.00 (-100.0%) |
| Entry quality | Pullback |
| Max concurrent positions | 4 |
Cash reserve: keep 25% buffer. Deploy in 2 tranches. Portfolio style: Momentum / Swing Trader.
Backtest Trade Log
| Date | Action | Price | P&L |
Generated by BitcoinsNews.com Coin Analysis Engine · 2026-09-25 16:00 UTC
Trend-following methodology: 50d/200d MA crossover + RSI filter + ADX regime gate
Data via Yahoo Finance / CoinGecko · Not financial advice. For educational purposes only.
Trend-following methodology: 50d/200d MA crossover + RSI filter + ADX regime gate
Data via Yahoo Finance / CoinGecko · Not financial advice. For educational purposes only.
stop loss of -9264% is wild. at that point just set the alert to notify my next of kin
the -9264% stop loss lives rent free in my head. thats what happens when price feeds 0.00 into the risk math, some divisor somewhere went to zero
the stop math ran 0.00 entry against a 0.02 level the engine never had. garbage in, 9264 percent garbage out
div by zero producing a 4 digit stop loss is such an on brand bug. at least the AVOID verdict accidentally landed on the right answer, broken clock style
right, the engine no-oped its way to AVOID. would love to know if anyone actually deployed the 15k plan against a zero entry price
rent free here too lmao. 52w high of 1.31 next to a live price of 0.00, nobody QA checked that table before it went out
52w high of 1.31 next to a live price of 0.00 should have failed a basic sanity check. the SELL is right, the evidence is unusable
rent free for the entire comment section lmao. the risk engine computed a stop 92 times the entry and shipped it as a deployment plan
risk engine computed a stop 92 times the entry and the plan still printed a dollar figure. automation is a choice
RSI 1.2 on a -100% drawdown, this chart is a eulogy. AVOID earned
backtest finished +0.0% because the system never fired a single buy lmao. cleanest way to say a token is untradeable
ATR volatility of 4946% per day. even if that is a data bug, publishing an AVOID call on numbers this broken does nobody any favors
they list resistance at 0.41 with price showing zero. feed was dead before this published
right, and the 1Y ago row still shows 1.00 which means the feed died mid-stream this week, not at listing. wonder how long this sat in the queue before anyone noticed
the 1Y row showing 1.00 is the tell, MNT hasnt traded near a dollar all year. feed died, template kept rendering, nobody glanced at the output. at least the AVOID landed right side up by accident
right, MNT spent the year between 0.7 and 1.1 so a 1.00 print would be suspiciously convenient. dead feed is the only explanation that fits
if the feed recovers the 1Y row backfills, but the published SELL stays frozen. the archive never gets the correction
a SELL rating on MNT where the entry prints 0.00 and the stop is -9264%. the whole 15,000 deployment plan is fiction built on a dead feed
fiction with a deployment schedule. even the ATR row says 4946 percent, someone divided by zero three different ways and hit publish anyway
the 4946 percent ATR row is my favorite artifact of this whole thing. whoever owns that pipeline should publish a postmortem, zero sanity checks anywhere
curious whether the table backfills when the feed recovers or if 0.00 stays frozen in amber forever. either way the SELL aged into accidental correctness
MNT probably deserves the short, but nothing in a table where every price reads zero can prove it. verdict accidentally correct, writeup still unusable
SELL verdict on a table where entry reads 0.00 and the stop is negative nine thousand percent. the thesis aged fine, the evidence was never there
entry 0.00 with a -9264% stop and someone still asked the risk engine for 15k of deployment advice. QA is one if statement away
one if statement is generous. entry greater than zero is like the third check after feed alive and timestamp fresh
resistance listed at 0.41 against a live price of zero is my favorite sanity check nobody ran. SELL correct, table still fiction
the real story is the publish queue had no human eyes. a 4946 percent ATR sailed through to live and nobodys job was to look