HTX DAO (HTX)
0.00
0.00
-0%
Stage 4 (Downtrend)
Bearish factors: 50d falling, MACD bear cross, RSI weak (0.0), falling 1m & 3m, far below high, breakdown below lower band, vol 2.62x on down day
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.26%/day | Trend | HOLD |
Crypto Performance Comparison
| Asset | 1 Month | 3 Months | 6 Months | 1 Year |
| HTX | -14.6% | -14.6% | -14.6% | -14.6% |
| BTC | +11.0% | +36.4% | +11.3% | -3.9% |
| ETH | +7.8% | +45.7% | +29.2% | -8.1% |
| SOL | +17.8% | +65.7% | +41.5% | -5.1% |
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.
Strategy vs Buy & Hold
| Asset | Strategy | Buy & Hold | Max DD | Trades | Win Rate |
| HTX | +0.0% | -14.6% | 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.6% | 25,611 |
| DCA — 4 buys | -14.6% | 25,611 |
| DCA — 6 buys | -14.6% | 25,611 |
| DCA — 12 buys | -14.6% | 25,611 |
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 |
Trend-following methodology: 50d/200d MA crossover + RSI filter + ADX regime gate
Data via Yahoo Finance / CoinGecko · Not financial advice. For educational purposes only.
RSI of 0.0 and ADX of 100 at the same time? those numbers are literally impossible on live data. feed is broken, someone should pull this chart before people trade off it
ADX maxes out at 100 and this feed printed exactly 100.0 while RSI sat at absolute zero. whoever wires the data in should add a guard that refuses to publish when every single field rounds to zero
a range check on ingest would have caught this in one line. ADX printing exactly 100 with RSI pinned at 0 is impossible on live data, even a NaN guard would flag it
a NaN guard AND a range check, one line each. the verdict banner still firing means nobody ever tested a dead feed path in the pipeline
@satswend_99 ADX maxes at 100 like rsi floors at 0, seeing both pegged means one candle window. feed is definitely dead
agreed, and the -14.6% table entry proves the feed died mid write, not that the token is flat. publish gate first, verdict engine later
publish gate first, agreed. half the comments on this page are better qa than whatever pipeline let price 0.00 reach a verdict banner
exactly, RSI zero and ADX 100 together means the dataset is null. the seven red factors are just the broken feed screaming
lol the bot still says HOLD with price 0.00 and stop loss nan%. bold strategy
diane has a point, whole template filled with zeros. the only real number i see is -14.6% vs SOL +65.7% and that alone tells you to stay away from HTX
the nan% stop loss is my favorite risk management feature. right up there with hope and vibes
hope and vibes lmao. honestly the nan percent stop loss is the most honest thing an auto generated analysis has ever printed
@btfddiane HOLD with stop loss nan is honestly the correct rating for a coin the data feeds forgot. safest call the bot ever made
bold is one word for it. the one live number it did print, -14.6 against SOL +65.7, and the verdict still couldnt say SELL lol
stop loss nan percent is my favorite part. the bot cant even compute risk on a broken feed and still votes HOLD lmao
7 bear factors against 0 bull and the verdict is still HOLD with 15% position size. the engine needs a sanity check between score and recommendation
agreed, a weighted score that outputs HOLD at 15% size while all seven trend factors are red means the verdict layer is completely disconnected from the scoring layer. fix the plumbing first
score and verdict drift apart when all seven factors are trend based and momentum is already dead, nothing left to score. still agree the engine should never show WAIT on the banner and HOLD in the verdict, pick one
a 30k deployment plan got published on a token with no readable price. that should have stopped the whole piece before anyone argued about WAIT vs HOLD
a WAIT verdict on a token printing price 0.00 and RSI 0.0 is honestly the most sane output this engine has ever produced. stage 4 downtrend with 2.62x volume on down days, no thanks
RSI 0.0, ADX 100, price 0.00 and a 30k deployment plan. whoever let this through the pipeline should be on janitor duty for a month
price feeds showing 0.00 while the bot still prints a verdict is peak autoplay analysis. hold rating on a null dataset, love it
price feeds breaking right as the verdict engine runs is such a quiet failure. whoever publishes these should gate the template when price reads zero
-14.6 percent vs SOL +65.7 and the engine still prints HOLD at 15 percent size. the verdict layer needs a circuit breaker for dead feeds
the table showed minus 14.6 against sol plus 65.7 and the banner still printed hold. whoever wires the verdict layer to the factor data needs to look at this one and wince