Pine-to-Python verification report
Real TradingView Pine scripts, run as Python.
PyneComp converts open-source Pine Script™ into Python. PyneCore runs the converted scripts on real market data, and this report compares plots and trades against TradingView's own output.
Every script in the corpus climbs the same four rungs. No cherry-picking — failures are published right next to the successes.
PyneComp converts the original Pine source into runnable Python, untouched by human hands.
PyneCore executes the converted script over 25,000+ bars of real exchange data without errors.
The run emitted numeric plot or trade data that can be checked. Drawing-only scripts are reported separately.
Plot and trade outputs are compared bar by bar and trade by trade against TradingView's own reference.
Indicators compared plot by plot, strategies trade by trade, against TradingView's own output. The headline counts are over the scripts that produce a comparable numeric reference; a plot PyneCore fails to reproduce counts as a divergence, never as "no reference". Corpus coverage and each script's full detail are in The Corpus below.
indicators clearing the ≥99% plot-match threshold
strategies clearing the ≥99% entry and exit timing threshold
of the compared plotted values were the identical IEEE-754 double
Reproducible by design. The manifest pins the exact source of every script with a SHA-256 hash — and TradingView keeps every published version forever, so anyone can re-run the comparison.
symbol = BINANCE:BTCUSDTtimeframe = 30 minexceptions = 8 scripts on their own marketbars = 25,000+ per scriptulp_limit = 64 (libm tier)rel_tol = 1e-9scale_floor = 1e-9 x series mediannet_tol = 2.0% of the larger netreference = TradingView exportsources = SHA-256 pinned manifest
A script enters the corpus only if it is published open source, written in a supported Pine version, and its header does not forbid reuse. The detected license is recorded in the manifest.
Only the manifest (name, author, link, license, version, SHA-256) is published. Pine sources are fetched locally, used for measurement, never re-hosted.
Reference plots and trade lists come from running the original script on TradingView itself, on the same symbol, timeframe and bar range.
Scripts that time out or hit harness limits are reported as-is. A proof you can't falsify is not a proof.
A percentage only says the outputs landed inside a band, and a band is something we chose. So each compared value is also placed on the one scale that is not ours to choose — the IEEE-754 double both engines store it in. Consecutive representable doubles are one step apart; that step is the finest distinction the type can make.
log, exp, pow,
the trig family. IEEE-754 requires + − × ÷ and
sqrt to be correctly rounded, and requires nothing of those, so
CPython's C library and TradingView's Java runtime can both be right and still land a
few representable values apart — which a long accumulation then carries forward.
The tier is capped at 64 representable values, chosen from measurement: across our own
reference corpus the widest such gap is 23. A script whose numbers sit inside that cap
but reaches no transcendental is not labelled this way; an explanation has to
explain something.
The two tiers sit under the Verified badge in the table, because that is what they are: the rung a verified script reached, never a verdict of their own. Anything else carries no tier line — it agreed within the published band, which is what the Verified badge above already says. The band itself is one number, not two — a relative tolerance. Near zero a relative test has nothing to be relative to, so it falls back on a floor taken from the series' own median magnitude; a fixed absolute floor would be unreachable for a series living at 100,000 and larger than the whole signal for one living at 0.000001.
Don't take our word for it. Every script is pinned by SHA-256, and TradingView keeps every published version. Pull the same script, run it on your own TradingView subscription, and compare it with PyneSys. The numbers are the numbers.
The most-liked open-source Pine scripts on TradingView, in order of community popularity (or whatever you sort the table by — the choice is remembered). Every name links to the original publication.
| Long-Only Opening Range Breakout (ORB) with Pivot Points | STRv6 | Verified | 100%12 plots | 100%565 / 565 | ✓100.000% | 27,617 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Tristan's Multi-Indicator Reversal Strategy | STRv6 | Verifiedbit-exact | 100%6 plots | 100%474 / 474 | ✓100.000% | 27,617 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Bollinger Bands Mean Reversion using RSI [Krishna Peri] | STRv6 | Verifiedbit-exact | 100%3 plots | 100%680 / 680 | ✓100.000% | 27,617 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| KALKI TFXBOT | STRv6 | Verifiedbit-exact | 100%2 plots | 100%373 / 373 | ✓100.000% | 27,617 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Two-Bar Fib Retrace Strategy [Futures] | STRv6 | Verifiedbit-exact | 100%1 plot | 100%166 / 166 | ✓100.000% | 27,617 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| RSI + MACD Multi-Timeframe Strategy | STRv6 | Verifiedbit-exact | 100%3 plots | 100%1 / 1 | ✓100.000% | 27,618 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| RSI Divergence Strategy | STRv6 | Verifiedbit-exact | 100%3 plots | 100%10 / 10 | ✓100.000% | 27,618 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Precision Confluence Trading Strategy [JOAT] | STRv6 | Verifiedbit-exact | 100%14 plots | 100%358 / 358 | ✓100.000% | 27,618 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Elite Strategy | STRv6 | Verifiedbit-exact | 100%2 plots | 100%518 / 518 | ✓100.000% | 28,307 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
| Fabio Valentini Pro Scalper [PickMyTrade] | STRv6 | Verifiedbit-exact | 100%16 plots | 100%1,183 / 1,183 | ✓100.000% | 27,619 | |
Accuracy
Run
Data window
Source
SHA-256 | |||||||
No scripts match the current filters.
Every script on this page was compiled by PyneComp and run by PyneCore. Both are live.
Try PyneComp Convert your first Pine script at pynesys.io