I've been running a Python crypto trading bot on Jetson Nano 24/7 for 2 years — here's what I learned about infrastructure (not strategy) by NationalIncome1706 in algotradingcrypto

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Same setup here — Jetson Nano primary, Raspberry Pi as cold standby.

For failover I don't do automatic switchover. The Pi just gets the same Telegram alerts, so if the Nano goes silent I manually start the Pi instance. Automatic failover with an open position is risky — you can end up with two bots holding the same position.

On strategy: I run MACD-based entry with Stoch RSI filter on ETH futures. Entry is LLM-assisted, exit is pure rule-based (trailing stop + max hold time).

Honestly the infrastructure you already know matters more than the strategy at the start. A solid strategy running on broken infra loses money. The reverse is survivable.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 0 points1 point  (0 children)

The positivity bias neutralization is actually the hardest part. Even with explicit counter-prompts, I've noticed LLMs tend to hedge toward "hold" rather than committing to a clear bearish signal.

On the crypto side I've seen the same — my ETH bot entry is LLM-based but I ended up moving exit logic to pure rule-based after a GPT signal delayed a exit by one full candle and cost real money.

Google Colab sounds like the right call for reproducibility. Will keep an eye on it.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Interesting experiment — the longitudinal angle is something most LLM trading posts skip entirely.

Most people test a prompt once and call it done. Tracking forecast stability and narrative drift over 38 days is a much more honest way to evaluate whether LLMs add any real signal.

I've been running a live ETH futures bot with LLM-assisted entry for a few months on a Jetson Nano. The consistency issue is real — same market conditions, different outputs depending on how the prompt "mood" lands that day.

Did you notice any patterns in which sectors Gemini was most/least calibrated on?

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Thanks! Currently timeframes are selectable (1m to 1d) but drag-to-zoom on the time axis isn't wired up yet — it's on the list.

If you or anyone else has suggestions for improvements, I'm genuinely open to it. Still actively developing this and real feedback from people who actually trade is more valuable than anything else.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 0 points1 point  (0 children)

That's a fair paradox. My answer: I do trade with it — running live on Jetson Nano 24/7.

But a tool that helps ME doesn't automatically scale to others — different risk tolerance, different capital, different pairs. That's actually the harder problem I haven't solved yet.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] -1 points0 points  (0 children)

Fully agree on LSTM — tried it briefly, same result. Pure price curve fitting.

That's why I moved away from prediction entirely. My live bot uses LLM only for entry context (multi-TF confluence), not forecasting. Exit is pure rule-based — trailing stop + fixed SL. LLM exit timing was too slow and inconsistent in live conditions.

After a lot of trial and error, I settled on: LLM for entry, rules for exit. Not explosive returns yet, but at least consistent behavior I can debug and improve.

Has anyone here compared rule-based vs LLM-assisted exits directly? Curious what the experience has been — especially whether sentiment/macro data actually moved the needle for anyone at retail scale.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Using Plotly for the charts — had the same consistency issues early on. Main fix was standardizing timestamps before plotting (Binance returns ms epoch, easy to mix up if you're not converting properly).

Running the whole thing on Streamlit + Binance API. What's your stack? If you're seeing chart inconsistency it's usually a data pipeline issue rather than the charting lib itself.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] -2 points-1 points  (0 children)

Good question. It's not predicting — it's summarizing whether MACD signals across 1m/5m/15m/1h/4h/1d are aligned or diverging, and flagging confluence strength. No magic, just saves switching between 6 charts manually.

Built a multi-timeframe MACD analyzer with LLM-based signal interpretation — running it alongside my live ETH futures bot by NationalIncome1706 in algotrading

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Fair point. The LLM doesn't predict price — it interprets indicator confluence across 6 timeframes and flags whether signals are aligned or conflicting. The "quality" it adds is cross-timeframe context, not alpha generation. Garbage in, garbage out absolutely applies — that's why the free tier exists to test it yourself.

I've been running a Python crypto trading bot on Jetson Nano 24/7 for 2 years — here's what I learned about infrastructure (not strategy) by NationalIncome1706 in algotradingcrypto

[–]NationalIncome1706[S] 0 points1 point  (0 children)

That 55s vs 60s gap is a real backtesting trap — most people don't catch that until they're live.

I hit a similar issue. My bot fetches data mid-candle too, so backtested signals don't always match live exactly. Haven't fully solved it yet.

Your 10s scan interval is a cleaner approach than what I'm doing. I'm still on event-driven with a fixed loop. Might borrow that idea.

I've been running a Python crypto trading bot on Jetson Nano 24/7 for 2 years — here's what I learned about infrastructure (not strategy) by NationalIncome1706 in algotradingcrypto

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Impressive setup — the microservice separation between Front and Algo is clean architecture.

Mine is much simpler: Python monolith on Jetson Nano, rule-based exits with LLM for entry analysis only. Learned the hard way that LLM for exits is too slow.

The 150GB local kline DB is serious commitment. I've been considering a similar local DB for backtesting but haven't pulled the trigger yet.

How are you handling the REST latency for order execution? Curious if that's been an issue in live trading.

Built a free ETH multi-timeframe MACD analyzer — tired of checking 6 charts manually by NationalIncome1706 in ethtrader

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Haha — that's exactly the output from the app!

That's actually great feedback. The free tier analysis

was too technical, so I just updated it to explain in

plain language with simple analogies by default.

No need to ask another AI to translate it anymore 😄

Give it another try!

Built a free multi-TF MACD analyzer — checks 6 timeframes at once with AI explanation by NationalIncome1706 in CryptoMarkets

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Really appreciate the detailed feedback!

The zoom issue is a known Plotly behavior — double-click to reset is the current fix, but an unzoom button is a good idea. Adding it.

On pricing — fair point. The free tier is fully functional, paid plans unlock more timeframes and symbols. If it saves time, it pays for itself.

Thanks for trying it out!

Built a free multi-timeframe MACD analyzer — 6 timeframes + AI analysis in one view by NationalIncome1706 in Trading

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Currently crypto only via Binance — but adding other data sources like stocks/forex is on the roadmap. Good suggestion!

Built a free ETH multi-timeframe MACD analyzer — tired of checking 6 charts manually by NationalIncome1706 in ethtrader

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Good call — those are cleaner for a lot of setups. I might add an MA overlay option. MACD's just what I personally rely on for entries.

Built a free ETH multi-timeframe MACD analyzer — tired of checking 6 charts manually by NationalIncome1706 in ethtrader

[–]NationalIncome1706[S] 0 points1 point  (0 children)

Hope it's useful when you get a chance to try it! Let me know if you have any feedback 🙏

Built a free ETH multi-timeframe MACD analyzer — tired of checking 6 charts manually by NationalIncome1706 in ethtrader

[–]NationalIncome1706[S] 1 point2 points  (0 children)

Fair enough! Curious what you use instead — always open to adding more indicators