First trade from a PyneCore bot on https://t.co/NRngf7wmWJ (demo) today.
Pine Script → Python, runtime by PyneCore. Broker access via an external plugin — extensible to any broker.
Still WIP, public dev branch. Forward testing next...
@garrytan Used to be normal. In Hungary TVs and radios shipped with the circuit diagram glued inside the back panel — you were expected to be able to fix it. Commodore openly published the C64 schematics in the Programmer's Reference Guide. Closed-by-default is the recent invention.
Pine Script automation today = webhook spaghetti. Alerts to a 3rd party, hoping it fires. PyneCore runs Pine natively in Python. No webhooks, no middleman. Same ta.rsi(), same strategy.entry(), same numbers as TV. FreqTrade integration examples 👇
Needed a logo for my startup. Instead of Figma or an AI prompt, I opened the Pine Editor and wrote it as a TradingView indicator.
Turns out #PineScript's plotcandle() is basically pixel art if you stop thinking in OHLC.
Full code and breakdown → https://t.co/i9Zvln54xX
Respect for doing this by hand — that's how you really learn what's going on behind the indicators.
For anyone who wants the same result as TradingView without the manual conversion: PyneCore (https://t.co/Elyb4O3pMW) is an open-source Python framework built to run Pine Script-style code natively. And PyneComp (https://t.co/DiWxcjDIoW) can auto-convert your Pine scripts to clean, readable Python.
@AlgoTradingxAI@Truecrypto If a backtest looked too good, the author either used lookahead for visual analysis and mistakenly treated it as a live signal — or didn't understand what they enabled. That's on the script, not the platform. TV's backtester is deterministic and correct.
@AlgoTradingxAI@Truecrypto Pine Script's execution model makes accidental repainting nearly impossible. It runs bar-by-bar — each bar only sees data available up to that point. lookahead_on is a deliberate tool for retrospective analysis, you have to explicitly opt in.
Building out the PyneCore plugin system 🔧
CLI plugins ✅ Data & live provider plugins ✅ Broker plugin — in progress
The idea: one unified plugin architecture. Data sources, brokers, CLI tools — all drop-in. Community can build their own exchange connectors while we focus on the core.
Next up: bot execution. Things are moving. 🐍
@masked_stat@daytradingrauf We built this for exactly that pain — Pine Script → Python compiler, automated. Not AI-generated guesswork, deterministic compilation.
Runtime: https://t.co/HjHgfUFVRI (open source) Compiler: https://t.co/DMro9cSoVQ 🐍
@Anemoia38 Exactly. That's why a real compiler exists — PyneSys compiles Pine Script to Python with full semantic accuracy, not AI guessing. It understands the execution model, not just the syntax.
@rcktwit@techie_41 And that 80% accuracy covers the easy 20% of the work. The real challenge — Pine Script's execution model, series handling, persistent state — is the other 80% that AI simply can't get right.
@rcktwit@techie_41 That's exactly why we built a dedicated compiler. AI gets ~80% right but can't handle Pine Script's execution model (series, bar-by-bar evaluation, persistent state). We wrote about this in detail:
https://t.co/vmNmwqTHaF
PyneCore v6.4.1
Bar Magnifier — LTF sub-bars resolve TP/SL fill order. calc_on_order_fills + varip support with proper var rollback.
Verified against TradingView.
#algotrading#PyneCore#PineScript
https://t.co/xaBOIojF5G
🚀 PyneCore v6.4.0 — https://t.co/5FD1piScl1() support is here.
Multi-symbol & multi-timeframe analysis, true multicore parallelism via separate OS processes.
https://t.co/zfx1VlXnsJ
#algotrading#PineScript#Python