Monte Carlo for discretionary zone and event traders
Understand what resampling closed trades can reveal about losing runs, account pressure, and sizing assumptions when your entries depend on zones or events.
Read article →Stratifyre blog
Trading insights, grounded in practice
Practical guides to building, testing, and automating strategies across crypto, equities, and futures.
How corporate actions change a running backtest
Why splits, renames, membership removals, and mergers require coordinated changes to positions, orders, lots, quotes, and strategy memory.
Read article →
Why historical trading universes require more than ticker lists
The engineering behind dated index membership, instrument identity, coverage checks, and reproducible universe backtests.
Read article →
How to verify a point-in-time backtest from data to portfolio
Independent financial controls, preserved failures, real reference corrections, and frozen reruns that test the complete backtesting path.
Read article →
Turn a plain-English trading idea into backtest rules
Replace vague trading instructions with precise entries, exits, sizing, and timing, then audit the generated rules and one historical trade.
Read article →
From hypothesis to evidence: autonomous strategy research with MCP
Use an AI assistant and Stratifyre MCP to preserve rules, backtest IDs, trade evidence, and rejected hypotheses in one bounded research workflow.
Read article →
Build a trading strategy that remembers a setup and waits for confirmation
Model a three-hour confirmation window with no-code state rules, then inspect why a setup entered, expired, or exited in a real backtest.
Read article →
Build a crypto breakout scanner around a watchlist you can review
Define a prior-channel breakout, choose venue-specific pairs, and make scanner matches a manageable review queue.
Read article →
Backtest to paper trading: a checklist for validating your trading bot
Check signals, order handling, market-data timing, recovery, and risk limits before treating a paper trading result as operational evidence.
Read article →
Backtest and paper trading disagree? Check the first comparable decision
Find the earliest defensible difference in inputs, decisions, orders or fills—and recognize when a backtest and simulated session cannot yet be compared.
Read article →
Slippage stress tests: how much cost can your backtest tolerate?
Fix your strategy assumptions, vary execution costs, and find the range where net profit disappears without mistaking a scenario for a fill forecast.
Read article →
How to test an Ethereum Bollinger Band breakout strategy
Turn an ETH band breakout into explicit entry and exit rules, compare nearby settings, and inspect the false breakouts that a headline return can hide.
Read article →
Turn scanner matches into useful Discord or webhook alerts
Design an alert that explains the market, rule, and next check; distinguish saved scanner conditions, recorded triggers, and actual notification receipts.
Read article →
Fixed-size vs. risk-based positions: compare sizing without changing your signals
Separate position allocation from planned loss at a stop, calculate shares and contracts correctly, and compare sizing policies without confusing size with entry quality.
Read article →
Crypto perpetual backtests: funding, margin and liquidation costs
Build a timestamped perpetual funding ledger, keep leverage and notional separate, and audit which costs a spot backtest actually accounts for.
Read article →
Gold futures session backtests: compare hours without changing your setup
Define two gold-futures entry windows, control costs and overnight exposure, and check whether a session restriction survives later data.
Read article →
S&P 500 backtests: historical members versus today's stocks
Avoid carrying today's S&P 500 stock list into the past: check membership dates, delisted data, and what your strategy could have known.
Read article →
Multi-timeframe backtesting: when is the hourly candle usable?
Audit a five-minute entry with an hourly filter by checking completed candles, source coverage, and actual fill timestamps before comparing returns.
Read article →
Build a stock breakout scanner with an explicit relative-volume rule
Define the breakout, volume baseline, session, and alert timing so your stock scanner answers one precise question.
Read article →
Regular vs. extended hours: why stock backtests disagree
Separate indicator history, entry windows, order fills, and overnight exposure before comparing stock backtests.
Read article →
Does your strategy behave differently in high volatility?
Compare one unchanged strategy across conditions known at entry, using explicit volatility labels, real trade counts, and careful timing.
Read article →
Walk-forward backtesting example: one rule, three folds
Choose strategy settings on earlier data, test them on the next window, and combine the results without double-counting dates or confusing capital with position carry.
Read article →
Parameter sensitivity: check the neighborhood around your best backtest
Define a small neighborhood around one strategy, diagnose fragile settings, and keep sensitivity checks separate from untouched test data.
Read article →
No-code backtesting software: test your rules before choosing
Compare documented workflows in Stratifyre, TrendSpider, Composer, and TradingView, then use a saved-rule and trade audit to evaluate your own strategy.
Read article →
How to backtest a Bitcoin moving-average crossover without coding
A real Bitcoin EMA crossover backtest: the saved rules, 24 trades, a losing account result, and the cost checks to make before trusting it.
Read article →
Grid versus random search: budget your strategy tests first
Count parameter combinations, compare searches at a matched trial budget, and separate historical candidate selection from later validation.
Read article →
Futures trailing drawdown: what proves a loss-floor breach?
Check the active loss floor against marked account equity. Learn why profitable closing trades and a low drawdown report cannot prove prop-evaluation compliance.
Read article →
How to backtest an ES opening-range breakout with explicit rules
Define a completed cash-open range, one daily entry, false-breakout exits, and contract costs before judging an ES opening-range backtest.
Read article →
NQ vs MNQ backtests: points, ticks, and dollar risk
Convert Nasdaq futures stops into dollars, compare equal contract counts with matched stop risk, and account for rounding and costs.
Read article →
Combining trading strategies: drawdown and shared capital
Align trading losses before combining strategies, then check simultaneous positions, idle cash, sizing, and a real SPY–QQQ shared account.
Read article →
A profitable backtest with a few huge winners: inspect the concentration
Find which trades, instruments, and periods made your backtest profitable—and distinguish a concentration diagnostic from a new portfolio simulation.
Read article →
VWAP reclaim backtest: define the trigger and audit the fills
Define a VWAP reclaim with explicit session, exit, and sizing rules, then inspect a real SPY backtest's losing trade and unresolved fill timing.
Read article →
Does your Bitcoin strategy behave differently on weekends?
Test a weekday-only entry rule without confusing weekend entries, weekend exits, and the risk of holding Bitcoin through Saturday and Sunday.
Read article →
One-second vs one-minute backtests: why your stop and target change places
Diagnose intraday fill differences by separating candle detail, signal timing, and fill assumptions before trusting a finer backtest.
Read article →
Backtest an Order-Block Retest With Rules You Can Inspect
Define an order block’s formation, bounds, and invalidation, then inspect a real hourly Bitcoin retest, its confirmation timing, and a failed trade.
Read article →
How to backtest an RSI pullback strategy on SPY
Separate oversold readings from recovery signals, define next-session execution, and compare an SPY RSI rule with a consistent buy-and-hold baseline.
Read article →
Monte Carlo drawdown: what changing trade order tells you
Shuffle an executed trade list to inspect losing streaks and drawdown, compare bootstrap methods, and separate conditional scenarios from forecasts.
Read article →
Continuous futures backtests: what happens at contract rollover?
Separate continuous futures signals from tradable contracts, roll-gap adjustments, and the fills and costs needed to calculate rollover P&L.
Read article →
Crypto backtest fees: calculate the move needed to break even
Calculate a spot trade's break-even move, distinguish maker and taker fills, and check fees, spread, slippage, and turnover before trusting net results.
Read article →
Backtest one ETF trend filter across SPY, QQQ, and IWM
Keep a moving-average rule fixed across three ETFs, then compare drawdowns, time invested, trading costs, distributions, and idle cash.
Read article →
Win rate, profit factor and expectancy: why winning often can still lose money
Reconcile winning and losing trades, costs and dollar expectancy with a real Bitcoin backtest—and see why an 80% win rate can still produce a loss.
Read article →
Backtest a crude-oil trend strategy with ATR stops
Compare a fixed crude-oil stop with an ATR-based initial stop, freeze the entry rules, and translate price distance into CL or MCL contract risk.
Read article →
How to backtest a trading strategy: your first run and what to check
Define a small first backtest, save its assumptions, inspect the report and one trade, then choose the next check using a real Bitcoin example.
Read article →
Adjusted vs. unadjusted stock backtests: splits, dividends, and double counting
Diagnose artificial stock-price gaps, keep signals and fills on consistent scales, and count dividend cash once.
Read article →