On Tradequix
Coming from TradingView
Bring an existing TradingView script to Tradequix: what runs unchanged, what to edit, and a checklist. Start with the checker.
Most Pine v6 scripts run on Tradequix unchanged. The differences come from three places: the data (an OTC candle feed), the engine (PineTS, which implements most but not all of Pine), and the platform (no libraries).
The fastest path#
- Paste the script into Will it run here?. It lists every line that needs attention.
- Fix the red items, read the yellow ones.
- Open it in the editor and press Add to chart.
What to change#
| On TradingView | On Tradequix |
|---|---|
import user/lib/1 | Not available. Paste the library's functions into your script. |
request.financial, earnings, dividends, economic | Return na. Remove them or treat them as optional. |
ticker.heikinashi(...) and other modified tickers | Refused. Compute Heikin Ashi in the script (cookbook). |
| Volume as traded size | Volume is a tick count. VWAP-style values are approximate. |
| Tick or sub-5-second timeframes | Not available. 5 seconds is the smallest. |
"W", "M" timeframes | Built from daily bars; history may be short. |
log.info and the Pine Logs pane | The calls run, but logs are not shown yet. |
| Session times and exchange hours | The feed is 24x7 on UTC. See Time and sessions. |
From older Pine versions#
v5 scripts usually run. Older ones need the usual conversions: study() becomes indicator(), security() becomes request.security(), rsi() becomes ta.rsi(), and so on. TradingView's editor can convert a script to v6 for you before you bring it over.
Things that are better here#
- Closed-source scripts run on the server, so selling access never ships your code.
- Every example in these docs runs in the page.
- The error index explains every console message.