Back to Feed
Agents / Benchmarks & Evals

Checking LLM Generated Trading Strategy Reliability

Original: FIDES: A Concordance Protocol for LLM-Generated Trading Strategies

Listen to the summary

Uses a voice available on your device

Audio options
On this page 4 sections
Related concepts 3 concepts

Key Takeaways

  • Most LLM-generated trading strategies are poorly calibrated, with only a 3.1% hit rate for claimed market edges.
  • Out of 40 generated strategies, 32 claimed to outperform a buy and hold benchmark, but only one actually succeeded.
  • The research tested four specific models: gpt-4o-mini, gpt-4o, gpt-4.1-mini, and qwen-2.5-7b-instruct.
  • Infrastructure limitations in the inference catalog restricted the breadth of models the team could successfully evaluate.

Summary & Methodology Analysis

The FIDES protocol aims to bridge the gap between an LLM's natural language rationale, its executable code, and actual market outcomes. The methodology employs dual delivery where a single prompt triggers the generation of both a strategy logic description and a self-contained strategy function. This code is then executed within a sandbox environment, and researchers perform a lag-one out-of-sample backtest to prevent look-ahead bias, ensuring that model positions are calculated using only prior market data rather than future information. Finally, the system measures concordance by scoring the alignment between the model's intent, the actual code execution, and the final empirical result.

The study evaluated four distinct models, including gpt-4o-mini, gpt-4o, gpt-4.1-mini, and qwen-2.5-7b-instruct, using a single seed at a temperature of 0.2. The team faced significant infrastructure constraints during the evaluation process, as many targeted models, such as Claude, Gemini, DeepSeek, Llama-70B, and Qwen-72B, were inaccessible through their inference catalog. Due to these limitations, the authors emphasize that they report observed effects rather than statistical confidence intervals based on their sample size of 40 strategies.

Key technical limitations were identified throughout the study, particularly regarding the validation tools. The researchers attempted to implement a runtime future-information probe intended to detect if code was gaming the backtest, but the probe failed to trigger on both clean and injected code samples. This failure is categorized by the authors as a limitation of the probe itself rather than evidence that the generated code was clean. Additionally, the small sample size and reliance on a single specific inference setup restrict the generalizability of these findings, though they provide a concrete look at the current reliability of LLMs in financial logic generation.

Interactive System Flowchart

Click diagram to expand and zoom

Cross-Examination & FAQs

A deeper dive clarifying mechanics, constraints, and baseline evaluations.

Q1. What is the core problem this paper addresses?

The paper addresses the lack of a standardized protocol to verify whether LLM-generated trading strategies, their underlying code, and their claimed market performance are consistent.

Q2. Do LLMs successfully generate profitable trading strategies?

In this study, the models performed poorly, with only one out of 40 strategies successfully realizing a claimed market edge.

Q3. How many models were tested in this research?

The researchers tested four models: gpt-4o-mini, gpt-4o, gpt-4.1-mini, and qwen-2.5-7b-instruct.

Q4. What is the hit rate of the strategies tested?

The hit rate is 3.1%, representing exactly one successful strategy out of 40.

Q5. What specific temperature setting was used for the models?

The models were evaluated using a temperature setting of 0.2.

Q6. Why did the authors only test a small number of models?

The authors encountered infrastructure limitations where several models, including Claude, Gemini, DeepSeek, Llama-70B, and Qwen-72B, returned a not-found error on their inference catalog.

Q7. Did the runtime future-information probe work as intended?

No, the probe failed to trigger on both clean and injected code, which the authors identify as a limitation of the probe itself.

Q8. How many strategies claimed to beat a buy-and-hold benchmark?

A total of 32 out of the 40 strategies generated by the models claimed to beat a buy-and-hold approach.

Q9. Are the results presented with confidence intervals?

No, because the sample size is limited to 40 strategies, the authors report the observed effects rather than confidence intervals.

Flag an issue

What is wrong with this summary?

What is wrong?