50 posts tagged with "strategies"

Your backtest shows 200% annual returns with a Sharpe ratio of 3.2. You wire up a live bot, fund it with real capital, and three weeks later it has lost 15% taking trades that make no sense given current market conditions. The strategy isn't broken — it never had an edge in the first place. You overfitted, and the historical numbers were always going to disappear the moment your bot encountered data the optimizer hadn't seen.

"RSI below 30 is oversold — buy" sounds like a complete strategy until you actually trade it. Run that single rule on BTC/USDT through the May 2022 capitulation and you'd have entered seven losing trades while RSI(14) sat below 30 for 41 consecutive days. The signal was working exactly as designed; the problem is that "oversold" is not the same as "about to bounce." This guide walks through building a real RSI mean reversion strategy in VolatiCloud — period selection, fresh-cross filtering, stop-loss configuration, and the backtests that tell you whether the edge is real before any capital is at risk.

A 30-second polling dashboard is fine until the moment your bot fills a trade at an unexpected price and you spend three poll cycles wondering whether the previous tick is real or just stale. VolatiCloud streams trade opens, closes, PnL changes, and runner status over a persistent WebSocket — every event arrives in under a second, and the equity curve redraws as soon as a position closes. No refresh, no polling, no waiting.

Connecting Claude to your trading account is the easy half. The hard half is knowing what to ask it — because most "AI for crypto" demos collapse the moment you want to do something real. This post is the practical half: five concrete workflows where the VolatiCloud MCP server turns multi-screen dashboard work into one conversation, plus copy-pasteable prompts and the trade-offs nobody warns you about.

Haven't connected MCP yet? Start with the MCP server setup guide — it covers configuration for Claude Code, Claude Desktop, and Cursor, and how the tool architecture works. Come back here once you're connected.

VolatiCloud's MCP server is live. Drop a four-line config into Claude Code, Claude Desktop, or Cursor and your AI assistant gets typed access to every operation in the VolatiCloud GraphQL API — list bots, run a backtest, fork a strategy, fetch live trades — directly from chat. No manual API calls, no copy-pasted tokens, no glue code, and no leaked credentials in .env files.

This post covers what MCP is, how the VolatiCloud server is built, and how to install and configure it in your editor. Once connected, see the companion post on practical AI trading workflows and example prompts.

You spend three days tuning an RSI mean-reversion strategy. The Sharpe ratio is finally where you wanted it. You change one parameter to test a hunch, hit save — and now the working version is gone, and you can't remember exactly what made it work. Every algorithmic trader has lived this moment. VolatiCloud's immutable strategy versioning makes it impossible: every save creates a new version, nothing is overwritten, and live bots stay pinned to the exact version they were created against.

A bot that misses a stop-loss because its container restarted is not just an inconvenience — it can convert a -3% planned exit into a -12% surprise. The hosting model under your bot is the second-most consequential decision in algorithmic trading after the strategy itself, and most traders pick it by accident on day one. This guide walks through the trade-offs between cloud-managed runners and self-hosted infrastructure so you can pick the right model deliberately.

A strategy with a 70% win rate and a 50% stake size loses two-thirds of an account on five consecutive losing trades — and five-loss streaks happen multiple times a year even at 70% accuracy. A 55% win-rate strategy with 5% stakes barely flinches at the same streak and keeps compounding. The signal logic gets all the attention, but it's the position-sizing rules underneath that decide whether your bot is around to take the next trade.

A strategy that returns 84% over two years on paper means nothing if you can't say what range of outcomes you might actually experience when you run it live. The single number is a starting point — what comes next is rigorous backtesting against years of OHLCV data, multi-pair stress tests, and risk-adjusted metrics like Sharpe and Sortino. VolatiCloud runs that pipeline on Freqtrade's production-tested engine, returns results in seconds to minutes, and surfaces every metric you need to decide whether the strategy survives contact with reality.

Most traders have legitimate strategy ideas. They know that RSI below 30 after a 200-EMA cross is a structurally interesting setup. They know that ATR widens before breakouts. They know that volume confirming a reversal matters more than the reversal alone. The bottleneck has never been the idea — it's the gap between knowing what you want and writing 80 lines of pandas to express it. The Visual Strategy Builder closes that gap. Indicator nodes, comparison operators, AND/OR/NOT logic trees, all visual, all generating Freqtrade-compatible Python automatically.