Trade Strategies

The Trade Strategies section is used to define how the Futures module should look for trading opportunities and decide when a setup is suitable for entry.

Open this section when you want to build a repeatable trading process instead of reviewing instruments manually each time from scratch.

Why this section matters

Without a strategy, futures trading quickly becomes inconsistent. The same instrument can lead to different decisions on different days.

Trade Strategies help solve that problem by turning trading ideas into a structured set of rules. Instead of rethinking the setup every time, you define the logic once and then work with it in a more disciplined and repeatable way.

What users do in this section

In this section, users can:

• create a new strategy;
• edit an existing one;
• enable or disable a strategy;
• duplicate a strategy to create a variation;
• remove a strategy that is no longer needed;
• search, filter, and organize the strategy list.

Telegram is required to enable a strategy

A strategy can be enabled only when the Firedrake Notifications Telegram bot is connected to your profile — see Connect Telegram. Without the bot, a strategy does not open deals.

• If Telegram is not connected, switching a strategy on opens the Connect Telegram first window. Connect Telegram takes you to the connection page; Not now leaves the strategy off.
• Until Telegram is connected, the toolbar of the strategy list shows the warning "Telegram is not connected, so strategies cannot be enabled." with a Connect it link.
• Switching a strategy off is always possible. The requirement applies to enabling strategies only.

How a strategy decides

The platform checks every enabled strategy against every contract every few seconds. A contract triggers a deal only when all of the strategy's conditions are true at the same moment:

• Between blocks — AND. Funding, risk, every timeframe of every indicator — all must match.
• Inside a multi-select — OR. If you select several MRC zones for 15m, any one of them is enough.
• Empty means "any". A field you leave empty is not checked.
• Missing data means "no match". If an indicator is not available for a contract yet (for example a fresh listing without a cloud), the contract does not pass a condition that asks for a specific value. This is especially noticeable on 1d and 1w: indicators start from the coin's listing, so a recently listed coin has no values there for a long while, and a strategy with, say, a 1w cloud condition simply does not pick it. The MRC zone of a new listing needs history too — see MRC: a newly listed contract. The same applies to CoinMarketCap metrics (volume, turnover, risk): when CoinMarketCap has no data for a coin, the value is empty and the contract does not pass a filter with selected values — see Market Metrics.

Fewer conditions mean more deals; more conditions mean fewer, more selective deals.

How many contracts match right now

At the bottom of the form, next to Save and Cancel, the line "Contracts matching now: N of M" is always in view. It is recounted on every change of the conditions — before you save — and refreshes the market every minute.

• 0 — the line is highlighted with a hint: check whether the conditions contradict each other. Such a strategy will not open a single deal.
• More than half of the market — the conditions are probably too broad.
• The Open in screener link opens the screener in a new tab, already filtered by the form's conditions, so you can see exactly which contracts match.

It is a snapshot of "now", not a forecast. The counter does not take the strategy schedule into account (that is a condition on the whole strategy, not on a contract). If the bot's first order is a % of the deposit, the contract's minimum-order check is skipped.

The blocks of a strategy

The blocks below follow the sections of the strategy form.

General

• Name — your label for the strategy.

Leverage and funding

• Min leverage — only contracts whose maximum leverage is at least this value.
• Funding % — allowed funding levels.

Limits

• Max cycles — how many deal cycles the strategy may complete; 0 means no limit.
• Max active bots — how many deals the strategy may have open at the same time. While the limit is reached, no new deals are opened.

Risks

• Volume Weight — allowed 24h volume levels.
• Trade Score — allowed 24h turnover levels.
• Risk Score — allowed risk levels.
• Volatility Score — allowed volatility (coin activity) levels.
• Listing — the contract must have been listed within a range of days ago (for example "no earlier than 1 year, no later than 30 days").

Schedule

• Day, time from, time to — the strategy opens deals only within this window, in your profile time zone. Daylight saving time is taken into account: when your region moves its clocks, the window moves with them, so 09:00 stays 09:00 on your local clock. Outside the window the strategy simply waits.

Triggers

• Trading Pairs — limits the strategy to a list of contracts, or excludes a list. See Trading Pairs.
• Upper / lower price limit — the deal is opened only if, at the moment of the signal, the price is below the upper limit and above the lower limit. Each limit is a line built from an indicator (a moving average or an MRC line) shifted by an offset in percent, and refreshed on a schedule. It is checked only when a deal opens. See Price Limits with examples.
• Bot Settings — how a deal is managed after entry: order sizes, averaging, take-profit, stop-loss. See Bot Settings. The list shows only enabled bot settings and is refreshed each time you open the form. If none is enabled, the field shows No enabled bot settings with a hint: enable the bot you need in Bot Settings, or create a new one.
• Exclude announced delisting — skips contracts the exchange has announced to delist.
• Disable strategy on SL — switches the strategy off after a deal closes by stop-loss, so you can review what happened before it trades again.
• Only pairs listed on both exchanges — keeps only contracts traded on both Binance and Bybit.

Indicators (per timeframe: 1m, 5m, 15m, 30m, 1h, 4h, 1d, 1w)

These conditions are set in the Triggering Signals section of the form, under Indicators.

Block	What you set	How the indicator works
Price Zone (MRC)	one or more MRC zones	Mean Reversion Channel
Price Direction (SMA9)	Up / Down	SMA9
Relative Strength Index (RSI)	a range from–to; 0–100 means off	RSI
Clouds	Blue / Red / Disabled (= not checked)	Clouds
MRC width	one or more channel width classes	Market regime
Price vs cloud	Below cloud / Inside cloud / Above cloud	Market regime
Cloud phase	one or more phases	Market regime
Cloud width	one or more cloud width classes	Market regime
Divergence	one or both kinds: bullish, bearish	Divergence

In the form the blocks are arranged like this:

• RSI, SMA and Divergence — switches;
• MRC — a section: MRC source, Price zone, Width;
• Clouds — a section: Colour, Width, Phase, Price position.

A section's Open button shows its switches and Close hides them; a section with anything switched on is open from the start. The Configure › button next to a switch that is on (or a click on its summary) opens its values per timeframe on the right. If you switch an indicator on and move to another one without selecting anything in it, it switches itself back off — an empty indicator filters nothing. An empty timeframe means "any"; a contract whose regime class is not available yet (too little history) does not match a condition with values selected.

Divergence

The Divergence condition checks for a confirmed divergence between the price and the MACD-based oscillator. For each timeframe you pick one or both kinds:

• Bullish (confirmed) — a bullish divergence: the price makes a lower low, the oscillator a higher low. It warns of a possible reversal up.
• Bearish (confirmed) — a bearish divergence: the price makes a higher high, the oscillator a lower high. It warns of a possible reversal down.

Within one timeframe any of the picked kinds is enough; across timeframes, every timeframe you set must have one. Only a confirmed divergence counts — its candle has closed. It stays valid for 3 closed candles: the confirming one and the next two. A divergence that is still forming on the open candle is not taken into account, which is why the strategy has no "forming" options like the terminal's filter. In the strategy list, the Divergence row of the strategy shows ON when the condition is switched on.

MRC source — whose MRC data is checked: the contract's own (Native), or BTC / ETH for every contract. It applies to both the Price zone and the Width of the MRC section. Clouds always look at the contract itself. See MRC source.

You do not need to enable every signal. Turn on only the timeframes and indicators that matter for your idea — a focused strategy is easier to understand and maintain. A typical strategy uses one or two "trend" timeframes (1h, 4h, or 1d / 1w for the bigger picture) and one or two "entry" timeframes (5m, 15m).

When several contracts match

If more contracts match than the strategy may open (see Max active bots), the most active contracts (by volatility rank) are taken first. If several contracts have the same volatility rank, the one with the larger 24h volume goes first, then by pair name. The same contract is not opened twice by one strategy while its deal is still active.

Linked sections

A strategy does not work on its own. It is connected to other Futures sections that define how the strategy should be executed and supported.

• Bot Settings define how a trade is managed after entry: first-order logic, risk control, position protection, and grid behavior.
• Trading Pairs limit the strategy to a selected set of instruments.
• Price Limits add reusable price restrictions.
• Telegram Notifications deliver strategy and trade events outside the platform interface. A connected Telegram bot is also required to enable a strategy.

Typical setup workflow

1. Describe the idea in words: "buy dips in coins that are in an uptrend".
2. Create a strategy and give it a clear name.
3. Translate each part of the idea into a condition: "uptrend" → 1h cloud Blue and 1h cloud phase Established; "dip" → 15m MRC zone Below Lowband or Oversold; "not in chaos" → 15m MRC width without the Very wide and Anomalously wide classes. See Platform Indicators for what each indicator means.
4. Add the market filters: volume, risk, funding, volatility.
5. Add day and time restrictions if the strategy should not work continuously.
6. Link Bot Settings and, if needed, Trading Pairs and Price Limits.
7. Check the "Contracts matching now" line at the bottom of the form and, if needed, open the matching contracts in the screener. Too many — add conditions; none — loosen them.
8. Make sure Telegram is connected (without it the strategy cannot be enabled), set up Telegram Notifications, enable the strategy with small sizes, and review the results in the Dashboard.

How this section fits into the Futures workflow

• Trade Strategies define when and why a setup is considered valid;
• Bot Settings define how the trade will be managed after entry;
• Terminal is where you follow active bots, open positions, and recent trading activity;
• Dashboard is where you review results after trading has already taken place.

Summary

Use Trade Strategies when you want the Futures module to work according to a clear, repeatable, and organized set of rules. This section turns trading ideas into rules that can be linked to execution, notifications, and monitoring.