Pine Script
Built in v6. Tested until it breaks.
I build TradingView strategies in Pine Script v6 for my own systematic research. This page shows how I write and validate them, and where I can help.
Fixes and clean-ups
Repainting, wrong session times, orders that don't fire, inputs that do nothing. Find the bug, fix it, and explain what was wrong.
Upgrades to v6
Move older scripts to Pine v6 with the same logic, cleaner inputs and fewer surprises, checked trade by trade against the original.
Validation reports
An independent stress test of a strategy you already have: costs, slippage, unseen data and Monte Carlo, in one written report.
Opening soon. Services aren't open for orders yet. Questions are welcome at hello@badredge.com.
How a strategy gets tested
Most backtests are too kind. These aren't.
- Frozen rules. Settings are fixed before the test, so the result can't be tuned after the fact.
- Real costs. Commission per contract and at least one tick of slippage on every trade.
- Unseen data. Sized and tuned on earlier months, then judged on months it never saw.
- Stress tests. Doubled slippage, losses 50% bigger, winners 10% smaller.
- Many-tests check. When many variants are tried, results are corrected so a lucky one doesn't look like an edge.
- Independent replica. The Pine logic is rebuilt outside TradingView and compared trade by trade.
VALIDATION REPORT · structure
1 Summary and verdict
PASS · EXPLORATORY · INSUFFICIENT EVIDENCE
2 Rules as tested (frozen inputs)
3 Costs and fill assumptions
4 In-sample vs out-of-sample
5 Year-by-year stability
6 Stress: 2× slippage, smaller winners
7 Monte Carlo drawdown range
8 Prop-rule fit: pass and payout odds
9 Code review notes
What you won't get
Clear lines
No signalsNo trade calls, alerts or copy trading.
No performance promisesA test describes the past under stated assumptions. It doesn't predict profit.
No resold strategiesYour code stays yours and isn't shared or reused.
No adviceEngineering and testing only. Trading decisions are yours.