Why your strategies bleed live

Pine Script's backtest is optimistic.
So you lost money.

Pine fills you at prices you'd never get. Ignores spread. Treats one candle as one moment. Your strategies look profitable in TradingView — and bleed the day they go live. OneTickTrading's backtest engine models the realities Pine ignores.

Get the comparison report
No card. The founder runs the comparison personally for the first 100 requests.

Free: the Pine vs OTT comparison report

Same strategy, both backtesters. Reproducible code, real fills, real numbers. Direct from the founder.

No card. No sales call. The founder reads every reply personally.

Got it. Comparison coming your way.
The founder will email you within 24 hours with the report. If you included a story, expect a personal response.
The four shortcuts Pine takes

Why Pine Script's backtest lies to you.

It's not that Pine Script is bad. It's that its backtester takes shortcuts that hide real-world losses. By the time you discover it, you've usually paid for the discovery in real money.

Fills at impossible prices.

Pine assumes a limit order at the candle high gets filled if price ever touched the high — even for a millisecond. Real exchanges don't fill orders that touched-and-bounced. Your real fill is much worse, or it never happens.

Zero slippage modeling.

For market orders, Pine assumes you get the close price. In reality, on a fast move, you get walked through 5–20 levels of book. The slippage compounds across thousands of trades into a meaningful drag your backtest never showed.

No spread modeling.

Pine treats one price as both bid and ask. Real markets quote a spread. On instruments with wider spreads — any altcoin, any thinly-traded futures — your true round-trip costs far more than Pine's calculation.

No intra-candle path.

Pine sees only OHLC for the candle. If your stop-loss and take-profit both lie inside one candle, Pine has to pick which fired first — usually the one most generous to your strategy. Real markets don't reward optimism.

How OTT models reality

The same strategy. Three different truths.

Same Pine-Script-equivalent strategy. Pine Script's optimistic engine vs Sierra Chart's onetick-eval vs OTT's slippage-modeled Rust engine. The gap is the cost you've been paying in production without seeing it.

OTT's reproducible-code methodology means you can verify the numbers yourself. We hand you the Pine code, the OTT DSL code, and the historical data window — re-run both yourself.

VWAP mean-revert on BTCUSDT, 365-day window. [reproducible]
Pine Script+197%
Sierra Chart+118%
OTT (real)+12.3%
Pine fills at the candle high; OTT fills only when traversed.
Pine ignores spread; OTT subtracts time-of-day spread.
Pine has no slippage; OTT walks the historical depth book.
How OTT models reality

Six modeling decisions other platforms skip.

Touch-not-traverse for limits.

A limit order fills only if price genuinely traded through it, not if a wick brushed it. Models real exchange-fill behavior.

Slippage per instrument.

Market orders walk the book using historical depth snapshots when available; statistical fallback otherwise. Calibrated per-instrument from observed fills.

Spread per time-of-day.

Round-trip costs include the actual spread that was quoted at the time-bucket your trade fired in. Not a single average.

Intra-candle fill simulation.

Stop-loss and take-profit evaluated against the actual price path, sourced from finer timeframe data. No optimistic ordering.

Walk-forward + Monte Carlo.

Stitched out-of-sample windows. Randomized arrival times. Shuffled position sizing. The strategy's actual risk envelope, not its best-case headline.

Same DSL, backtest → live.

No re-implementing strategies in Python or C# to go live. Write once in OTT's DSL; backtest results are what you'll see live.

Side-by-side

Pine Script vs Sierra Chart vs OTT.

The three backtesting paths a serious crypto trader actually compares. None of the others ship realistic backtesting — for different reasons.

Pine ScriptSierra ChartOTT
Backtest models slippageNoPartial / criticizedYes
Intra-candle fill simulationNoPartialYes
Spread modeled per time-bucketNoNoYes
Walk-forward / Monte CarloNoLimitedYes
Same code: backtest ↔ livePine for both, live limitedSeparate ACSIL C++Yes — DSL on both
Native macOS / LinuxBrowser onlyWindows-only (Wine)Both
Live trading on Coinbase / Kraken / BybitLimited via brokersNoBybit live; CB+Kraken next
One flat price, no add-onsFree + paid tiers$26-56 + Denali + agreementsYes
Frequently asked

Skeptics, this part is for you.

Why does Pine Script overestimate so consistently?

Pine's backtester was designed to be fast on a free public charting platform — running tick-precise simulation for every user is computationally expensive. The shortcuts (fill-on-touch limits, no slippage, no spread, OHLC-only candles) make backtests run in seconds at the cost of accuracy. Useful for prototyping; dangerous as a deployment-decision tool.

Can I import my Pine Script strategy into OTT?

For most strategies, yes — OTT's DSL is Pine-Script-equivalent in expressiveness. Send your Pine code in the form above; the founder will port it and run it through OTT's engine for the comparison report. (For strategies using Pine-specific built-ins that have no equivalent yet, we'll be honest about the gap.)

What language do I write strategies in for OTT?

OTT's own DSL — designed to be Pine-Script-equivalent in look and feel. No Python, no C++, no NinjaScript. Strategies you write run natively in Rust under the hood, but you don't see Rust in your strategy code. Free playground in the trial.

What's included in the free trial?

30 days of full-feature access. No card required to start. Real-time crypto data on Bybit, backtesting on the full historical record, the DSL editor, walk-forward analysis. Live trading on Bybit testnet during trial; live trading on Bybit mainnet activates after subscription.

Why should I trust the comparison report?

Because the report includes the reproducible code. We hand you the Pine Script strategy, the OTT DSL strategy (functionally equivalent), and the historical data window — you can re-run both yourself. We're not asking you to take our word for it; we're asking you to verify.

Tell me your Pine Script story. I'll send the comparison.

Founder-run for the first 100 requests. Plain-language report, reproducible code, honest numbers.

Send me the comparison