Deep Dive Analysis
HTX DAO (HTX)
2026-09-25 15:01 UTC · Marcus Reid · 30,000 Portfolio
PRICE
0.00
0.00
52W HIGH
0.00
0.00
DRAWDOWN
-0%
-0%
STAGE
Stage 4 (Downtrend)
Stage 4 (Downtrend)
🟡 WAIT — No Clear Edge
Trend-Following System · LOW Conviction · 0 Bull / 6 Bear Factors
Bearish factors: 50d falling, MACD bear cross, RSI weak (0.0), falling 1m & 3m, far below high, breakdown below lower band
HTX Price — 1 Year
1Y Ago: 0.00
Low: 0.00
Now: 0.00
Low: 0.00
Now: 0.00
Technical Snapshot
| RSI (14) | 0.0 | ADX (14) | 100.0 |
| 50d MA | 0.00 | 200d MA | 0.00 |
| Price vs 50d | ▼ Below | Price vs 200d | ▼ Below |
| Support | 0.00 | Resistance | 0.00 |
| ATR Volatility | 1.19%/day | Trend | HOLD |
Crypto Performance Comparison
| Asset | 1 Month | 3 Months | 6 Months | 1 Year |
| HTX | -14.1% | -14.1% | -14.1% | -14.1% |
| 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 30,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
30,000
RETURN
+0.0%
MAX DRAWDOWN
0.0%
Strategy vs Buy & Hold
| Asset | Strategy | Buy & Hold | Max DD | Trades | Win Rate |
| HTX | +0.0% | -14.1% | 0.0% | 0 | 0% |
DCA vs Lump Sum (HTX)
If you had deployed 30,000 using different timing strategies over the past year.
| Strategy | Return | Value Today |
| Lump Sum (1y ago) | -14.1% | 25,763 |
| DCA — 4 buys | -14.1% | 25,763 |
| DCA — 6 buys | -14.1% | 25,763 |
| DCA — 12 buys | -14.1% | 25,763 |
HTX Deployment Plan — 30,000 Portfolio
Analysis by Marcus Reid (Long-term HODLer). If you’re managing a 30,000 crypto allocation, here’s the plan:
| Position size | 4,500 (15% of portfolio) |
| Stop loss | 0.00 (nan%) |
| Target 1 | 0.00 (nan%) |
| Target 2 | 0.00 (nan%) |
| Entry quality | Unknown (R:R None) |
| Max concurrent positions | 8 |
Cash reserve: keep 15% buffer. Deploy in 3 tranches. Portfolio style: Long-term HODLer.
Backtest Trade Log
| Date | Action | Price | P&L |
Generated by BitcoinsNews.com Coin Analysis Engine · 2026-09-25 15:01 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.
every number on this chart is 0.00. price, support, resistance, all of it. they still wrote 800 words around it lol
52w high of 0.10 is my favorite detail. that is not a market, that is a 404 with a verdict column bolted on
price shows 0.00 across the whole table and we still got a full 30k backtest writeup lol
dead data feed, RSI 0.0 and ADX pinned at 100. garbage in garbage out, the WAIT call is doing heavy lifting here
RSI 0 and ADX 100 have shown up on a few of these writeups now, not just HTX. at some point the HOLD verdict is the model shrugging when the feed dies
RSI 0 and ADX 100 across multiple writeups means feed breaks get templated into verdicts. HOLD is the engine shrugging in print
ADX pinned at 100, maximum possible trend strength, on a token with no price. the engine was very confident about absolutely nothing
confidence of 100 on a price of 0.00 should be a null check, not a verdict. ship a proper data guard before the next 30k writeup goes out
null check plus a staleness timestamp would kill 90 percent of this. ship the empty state page and save the verdict column some dignity
adx 100 on a 0.00 price is the funniest contradiction on the page. trend strength pinned to max on a token the feed cant even price. print DATA ERROR and go home
garbage in garbage out and yet the verdict column still rendered fine. whoever wired the template to publish on feed failure owes the whole comment section an apology tbh
RSI 0.0 with ADX 100 at the same time should be impossible. whoever feeds this data pipeline needs to fix their feed, this is noise presented as analysis
dead feed feeding an indicator stack, the engine never had a chance. a HOLD verdict on literally zero data is a coin flip in a suit
HTX -14.1% while BTC printed +31 over the same window. that comparison table is the whole thesis, skip it
BTC +31 while HTX bled -14 and the verdict is still WAIT. holding through that gap is a slow exit with extra steps
the WAIT call makes sense once you realize the engine cant compute anything off a zero price. its not patience, its a shrug rendered as a verdict
a shrug rendered as a verdict is the best description yet. WAIT with a 0.10 52w high and zeros everywhere is the engine punting
WAIT as the engine shrugging is right. a 0.00 price feed should fail closed, printing a verdict anyway is worse than nothing
a whole 30k deployment plan built on a table of zeros is wild. even the 52w high reads 0.10, that is the API screaming, not the market
0.10 on the 52w high is the tell, an API error nobody caught because the template still rendered fine
a 0.10 52w high on a token that traded real volume, and nobody QA’d this before shipping. wild
0.10 as a 52w high should have failed a basic sanity check. one range validation on the feed kills this whole class of writeup before it publishes
one sanity check on the feed kills a whole class of these writeups. a 52w high of 0.10 passing through review is wild
-14.1 percent for HTX while BTC ran +31 over the same window. the comparison table buried under all the zeros is the only honest part of this writeup
love that the drawdown column survived when the price didnt. whoever wired this pipeline should push an empty state page instead of publishing
HTX minus 14 while BTC did plus 31 and the verdict is WAIT off a zero table. even the shrug is generous
the one honest row is the comparison table, HTX minus 14 while BTC ran plus 31. that gap is the whole review, zeros or not