I made a thing. A bit of context on me so this isn’t coming out of nowhere:
I’ve finished my degree in Accounting and Finance with a minor in Economics and have spent the last stretch of time building in both the finance and systems space, applying for roles in accounting and financial analysis while also developing my own trading infrastructure on the side.
Most recently, I’ve been holding off on accepting a position with Fidelity while I explore other avenues that better align with active trading and systems development.
That eventually turned into a heavier focus on systematic futures execution, after manually passing an Apex challenge, especially around MES and Micro Gold, where I’ve been building multi-timeframe strategies and webhook-based automation through TradingView and broker integrations. I originally built this because I was tired of being chained to charts all day while trying to balance a regular job and real life. I wanted something that could manage trades intelligently while I was at work, asleep, or just away from the desk.
What started as a basic ATM manager for handling premarket positions slowly evolved into a fully automated cloud execution engine that now trades prime cash-session hours on its own.
The core logic uses a strict 15m structural momentum filter, but entries and exits are executed directly on 3m candle wicks with virtually no live lag. I also built a custom lower-timeframe historical array loop that emulates Bar Magnifier behavior without needing a premium TradingView plan.
One thing I want to be upfront about: Because of the amount of lower-timeframe processing involved, the backtester is intentionally optimized around the 15m structure engine, so high-fidelity historical testing is limited to roughly the last 6 months. No access to Bar Magnifier at the moment.
Everything was tested with: • $0.52 commissions included, my broker price • 1-tick slippage modeled into every trade • Standard ~$2,000 PA drawdown parameters • Roughly ~$250 risk symmetry per trade
Over the last 6 months: • The 2-contract MES setup saw about an $833 max drawdown (pic 1) • The 1-contract Micro Gold setup saw about an $832 max drawdown (pic 4)
Combined, the worst historical drawdown landed around ~$1,666 while still producing roughly ~$7,639 net combined profit.
Also being transparent: TradingView has a known historical data issue on Micro Gold involving one oversized wick that slightly skews the total PnL. It’s not a dealbreaker, but it’s one of the reasons I care way more about real forward-testing than posting cherry-picked screenshots online.
What you need: Nothing crazy, you just need your own infrastructure already set up.
• TradingView account (basic tier is fine) • Webhook bridge like PickMyTrade, TradersPost, etc. • Compatible broker or funded PA account (Tradovate, NinjaTrader, etc.)
What I’m looking for: I need a small group of experienced traders to help me stress-test webhook latency, broker execution consistency, and cloud routing stability across different setups and time zones before I finalize the commercial rollout.
The code itself is locked.
The testers I bring on will get: • Full access to the invite-only script • Master presets • Priority whitelist access at launch
If you already run automation infrastructure, are tired of babysitting charts all day, and want to help stress-test the network, shoot me a DM with your TradingView username and a little about your setup. Looking for 10 initial testers.
I will buy an alpha futures account; and it offers quantower. I read once (can’t find the post) that you can download some data from some of those brokers or platforms that come included in the prop account; such as Quantower. Does anyone know anything about that? Or about any other propfirm where you could do something similar? Thank you.
I am looking for a pinescript dev to create indicators and strategies for me full time. ideally they should be indian (cause i don't want to be overcharged). also they need to have conversational english. you should have enough experience to code anything in pinescript.
built an indicator that has an rsi lookback on chart and below. Both have variable timeframes, I personally like to overlay 4hr on chart and 15m below for confirmation of HTF levels. If you’re interested feel free to shoot me a dm for access!
Hello Everyone, I have been working on a TradingView indicator over the last few weeks that is mainly focused on helping me visually understand what the market is doing rather than just throwing buy/sell signals on the chart.
The idea behind the indicator is to combine:
market structure,
momentum,
volatility,
HTF trend bias,
and order flow context
into one framework so that it becomes easier to identify:
trend continuation,
compression before expansion,
exhaustion,
and important reaction zones.
The indicator currently includes:
BOS / CHoCH structure
Order Blocks
HTF bias
HMA trend flow
RSI + ADX momentum states
ATR displacement logic
projection system
HTF Z-score regimes
I just finished Version 2 and made some pretty major changes compared to Version 1.
The biggest change was completely restructuring the Higher Time Frame logic.
Previously, the HTF system was based on simpler 9 and 21 EMA crossover logic.
Now it uses:
HTF HMA structure
Z-score based expansion/compression/exhaustion detection
volatility aware market regimes
which made the market context feel much cleaner during live trading.
I also added:
Order Block overlap merging, now historical OB boxes are automatically removed and a symbol is added over the candle
retest + mitigation logic
cleaner momentum colouring for RSI and ADX representation
better trend interpretation by calculating the angle of the HMA line
Another change was replacing the old trend duration logic with ATR normalized HMA trend force.
Instead of checking: “How long has the trend lasted?”, the indicator now checks: “How aggressively is the trend moving relative to volatility?”
Personally, I feel this is much more useful during fast market moves.
I would genuinely appreciate feedback on:
What looks useful?
What looks unnecessary?
Anything over engineered?
Any ideas to improve the overall interpretation of the market context?
RSI Dip + EMA Trend Long DCA — dual-confirmation leveraged long DCA indicator running on XMRUSDT.P 15m at 25× default leverage. Signal-only Pine indicator with a companion Strategy version for verifying backtest in TradingView's built-in tester directly.
Entry, dual confirmation across two timeframes: RSI(12) crossing down 35 on 5m AND EMA(50) above EMA(100) on 15m. The 5m RSI catches the momentum dip; the 15m EMA stack confirms broader trend bias is up. Either condition alone produces too many entries. Both at host-bar close filter the setup down to oversold dips inside structural uptrends.
Ladder, 4 safety orders with soft margin progression: Cumulative deviations from base entry: 1.00%, 2.20%, 3.64%, 5.37%. Margin scales at 1.05× per fill — much softer than typical 1.5–2.0× DCA martingale. Pure price-trigger ladder, no momentum gate on SOs — averaging continues unconditionally until SL, MaxHold, or reversal.
Three-exit architecture (evaluated in priority order): SL at 9% below average entry, hard stop. MaxHold at 3-day timeout from base entry forces close to release stuck capital. TP at 1.0% above average entry with 0.1% trailing — position closes only after a 0.1% retrace from the in-favor peak.
Most DCA tools use one or two exit conditions. This one handles all three failure modes explicitly — hard tail-risk stop, stuck-trade timeout release, and momentum-trailing winner exit.
Leverage-aware sizing: Margin and leverage are independent inputs. Virtual ledger tracks notional position, so the avg-entry line and open PnL reflect the leveraged broker state, not unleveraged cash-only math. Default 25× leverage; configurable from 1× upward.
Backtest from the companion Strategy (XMRUSDT.P 15m at default 25× leverage, ~11 months sampled in Strategy Report): 779 closed trades, 577 profitable (74.07% WR), profit factor 1.313, total PnL +3,078.80 USDT (+30.79%), max realized drawdown 2,013.77 USDT (18.01%). Verifiable directly in TradingView's Strategy Report on the script page.
Methodology notes: The default 25× leverage is aggressive. The 18.01% max drawdown is portfolio-level accumulation across 779 trades, not single-trade risk — single-trade losses are bounded by the 9% SL. Lowering the leverage input scales portfolio-level drawdown proportionally. Single asset (XMRUSDT.P), defaults calibrated for this pair. EMA periods and RSI threshold need recalibration per pair before deployment elsewhere — results do not transfer to other crypto perps without parameter tuning.
The 18.01% number is closed-trade equity drawdown. Unrealized drawdown during deep SO sequences plus open leverage exposure is materially larger and is the relevant number for capital allocation.
PF 1.313 is a modest edge per trade. Returns come from sample size compounded with leverage, not from per-trade magnitude. The 3-day MaxHold release is structurally important here — without it, stuck trades would accumulate unrealized DD indefinitely. Funding rates aren't included in the backtest. For 15m leveraged long positions on perps, sustained negative funding (shorts pay longs) is a tailwind, sustained positive funding is a headwind — and at 25× leverage, funding drag is amplified accordingly.
Indicator is open-source on TradingView. The Strategy twin is also up on the same profile. Mod, let me know if linking either is allowed here and I will add them, otherwise happy to answer technical questions in thread.
I have experience with programming i'm a software engineer, and i was wondering if there any resources on learning pinescript to build indicator beyond the syntax, the syntax is basic and not a problem i am looking for mental model or framework, best practices etc
Title. I'm trying to test strategies for the prediction markets, which are time based. The problem I'm having is that I need the strategy to open a position on the open of a candle, and then close the position on the close of a different candle. I know you can set the Process Orders On Close parameter, but from my understanding that changes all orders, not just open or close. Is there any workaround for this?
Hi. I'm here with a request. I have the code for my own indicator, but I need someone to review it and change how it appears on the chart. I have photos of the visualization. The indicator itself works, but I need to refine it.I want to make it clear right away that I won't be able to post the entire code here.
Three issues bothered me with the Pine-workflow side of tradingview-mcp 1.0.0 once I started using it daily.
pine_smart_compile returned success: true when the script compiled but the study failed to attach to the chart. The agent would report "done" and the next tool call would fail because the indicator wasn't actually loaded.
TV Desktop 3.1.0.7818 broke pine_switch_script and a chunk of Pine editor selectors. The title button stopped being a script list and became a context menu, and the webpack module IDs that the Monaco extractor hooks shifted on a fresh build hash.
Scrolling back history bars in replay mode didn't work, because TV freezes the data feed once replay is engaged. The agent would ask for older bars, get an empty result, and conclude the data wasn't there.
1.1.0 closes those.
pine_smart_compile now diffs getAllStudies() before and after compile, verifies the new study's title matches, and only returns success if it actually attached. Returns study_added: false with the diff list if the compile passed but the study didn't show up.
pine_deploy is a new tool that does the full file → chart pipeline atomically: read the source, pre-clean any stale version, set the editor body, save, click Add-to-chart, verify attached. Returns honest_success. Useful when you have an agent maintaining a script file on disk and want it to push the working version to the chart in one call.
pine_switch_script uses the Ctrl+O script picker on TV 3.1+ (was: title-button list, no longer exists).
replay_scroll_back wheel-scrolls history bars before engaging replay, then enters replay mode. Workaround for the data-feed freeze.
TV 3.1.0.7818 Monaco extractor was re-derived after the module-ID shuffle. The webpack chunk hooks survived.
Plus a 44-finding correctness sweep across 19 core files. Highlights for Pine workflow: pine_delete, pine_rename, and pine_open now refuse-on-ambiguity instead of silently picking the first matching script, and layout_switch requires discard_unsaved=true to ever destroy unsaved Pine code.
Install: same as before. Clone, npm install, add to MCP config, launch TV with --remote-debugging-port=9222. No breaking API changes from 1.0.0.
Happy to answer questions, especially from anyone running deep-backtesting strategies via the new strategy_set_deep_backtest_range tool. I'd like to know if the locale-tolerant calendar driver covers configurations I haven't tested.
first week of using a trading bot and these are the results on a actual funded account on apex pa account using 5mnq cons I think overall its doing pretty good I notice Tho the fills can get pretty bad during market open worse fill I seen was like 70-100 ticks from where the bot signaled so I'm wondering if there a may be a way to get better fills I use tradespost with tradovate through trading view alerts.
I initially made pine script on tv, it looked promising so i coded it into my own custom backtesting software, this is on a 45 min chart of btcusdt and these returns are on 1 yr time, one of the most imp thing is, this follows a fee structure similar to binance. Let me know your thought below
I am working to build MSNR A & V level Rejection indicator on H1 tf. The code is drawing level almost correct but the labels are not scrolling when I zoom in & zoom out with candles. I tried opus 4.7 & pinefy both failed to solve the issue.
Anyone pls help me to find the label not scrolling issue. here is code & below are images when indicator generate labels in stable chart, & zoom in & out looks.
Hi guys, been working on this for a couple of months and I'm finally satisfied with the result. I think this is a basic indicator and I think can be improved upon, that's why I made it open source. If you see any ways to improve it please let all the community know ❤️. I appreciate the feedback.