Skip to main content

​
Why this page matters

Trinigence is built to deliver fast, consistent strategy creation and backtesting - but your experience depends on market coverage, historical data availability, and current platform limits. This page helps you set the right expectations before you spend time iterating.
Trinigence focuses on strategy creation + backtesting first. Execution support depends on your environment and enabled integrations.

​
What’s supported (high-level)

​
Asset class focus

  • Crypto markets (primary focus in the current phase)

​
Strategy types

  • Long-only, short-only, or combined long/short strategies
  • Indicator-based conditions (TA-Lib style)
  • Fixed risk rules (TP/SL in %)
  • Filters such as trading schedule (days) and basic time logic (where supported)

How Trinigence works

See the end-to-end flow from idea to backtest.

Strategy structure overview

Learn how entries, exits, risk and schedules fit together.

​
Markets & instruments

​
Crypto pairs

Trinigence supports common crypto symbols such as:
  • BTC/USDT, ETH/USDT, and other major pairs (availability depends on the exchange/data source).
If a specific pair is not available, ATI will typically suggest the closest supported symbol or ask you to pick an alternative.

​
Spot vs Futures

  • Futures-style logic (long/short) is supported at the strategy level.
  • Instrument availability depends on data coverage (spot/futures) in your current environment.
If you’re testing a futures strategy, verify the symbol and data source are aligned (spot vs perpetual can behave differently).

​
Timeframes

Trinigence supports multi-timeframe backtesting where data is available. Commonly used:
  • 15m, 1h, 4h, 1D
Timeframe support depends on historical data coverage for that symbol and source. If the required timeframe is unavailable, ATI may suggest a nearby timeframe (e.g., 30m instead of 15m) or ask you to choose.

​
Backtest data coverage

Backtesting requires historical candles (OHLCV). Coverage depends on:
  • symbol
  • timeframe
  • data source (exchange/provider)
  • start date you request
If you request a backtest range that exceeds available data, Trinigence will backtest the maximum available range and surface the effective start date in results (or ask you to adjust).

How backtesting works

Learn what’s included in Trinigence backtests and how results are computed.

​
Indicators

Trinigence supports:
  • TA-Lib indicator set (broad coverage)
  • Custom indicators (Trinigence-specific additions)
You can define:
  • indicator parameters (e.g., MACD(12,26,9), RSI(14), Supertrend(10,3))
  • indicator-based conditions (crosses, thresholds, trend changes, etc.)
Indicator availability can differ by environment/version. If you use a niche indicator, ATI may propose an alternative or request a substitution.

Indicators & Logic overview

Understand supported condition types (cross, trend change, thresholds).

Writing better trading ideas

Learn how to express indicators and logic clearly.

​
Execution (automation) limitations

Trinigence can generate execution-ready logic, but actual live trading depends on:
  • enabled integrations
  • your account permissions
  • connection status
  • execution rules supported in your environment
If you’re here primarily for backtesting and strategy design, you can ignore execution details and focus on iteration.

​
Known limitations (today)

The most common limitations in the current phase:
  • Market scope: primarily crypto-focused during early rollout
  • Data availability: some symbols/timeframes may have shorter historical ranges
  • Complex logic: ultra-complex multi-layer rules may require clarification prompts
  • Indicator edge cases: some indicators behave differently across libraries/providers
  • Execution parity: not every backtest feature automatically maps 1:1 to live execution in all environments
Natural language can be ambiguous (e.g., “trend reversal”, “breakout confirmation”). ATI asks questions to ensure your strategy is deterministic and backtestable.
Common causes include timeframe mismatch, strict entry conditions, schedule filters, or insufficient data range. Check the requested backtest period, symbol, and timeframe first.

​
Best practices to avoid surprises

  • Start with major pairs (BTC/USDT, ETH/USDT) on 1h / 4h / 1D
  • Keep the first version of a strategy simple
  • Add complexity only after you confirm baseline behavior
  • Always verify:
    • symbol
    • timeframe
    • backtest start date
    • TP/SL definitions

Your first strategy in 5 minutes

Follow the fastest path from idea to backtest.

​
Troubleshooting

If something doesn’t look right, start here:

FAQ & Troubleshooting

Common issues: missing trades, unexpected results, indicator mismatch.

Backtest pitfalls

The most common reasons strategies behave differently than expected.

​
Need help?

If you’re blocked by a missing market, timeframe, or indicator, contact support and include:
  • the exact strategy text you used
  • symbol + timeframe
  • requested backtest range
  • what you expected vs what happened

Contact support

Email us and we’ll help you validate the setup.