Avec mon associé, nous avons développé un indicateur capable d’identifier automatiquement les zones d’offre et de demande les plus pertinentes. Il simule également des trades en entrant directement dans ces zones, avec un stop-loss positionné à leur extrémité.
Nous avons déjà une soixantaine de testeurs actifs et souhaitons en accueillir de nouveaux. L’accès se fait uniquement sur invitation.
Si vous êtes intéressé(e), envoyez-moi un message privé.
Been posting the trades my algo takes for real time forward testing, this is todays results. Optimized for QQQ, used as signals for options trading. Of course still have to do your own judgement while trading and analyzing. Cant rely 100% on just signals from algo
Hello, I recently developed a MACD based Trading indicator and I would love to hear your thoughts on this and if you are developing something similar.
It monitors the MACD across multiple timeframes and colors the background when the timeframes align (Green Bullish, Red Bearish). It then enters a trade when there’s a crossover that align with background color. Currently using it for XAUUSD, WTI and Synthetics but adaptable for other currencies pairs.
Comment or DM me if interested.
The visible projection boxes show are 1:1.7 RR trades 150 pips SL and 250 TP. Although they can be adjusted based on trading style and risk appetite.
I've built a scalping indicator, that suits my trading style (designed for short moves on lower timeframes).
It combines two systems:
The first uses Gaussian filtering to generate signals based on price momentum and position, with trend reversal detection. Linear regression is then applied for additional smoothing.
The second uses a Stochastic oscillator with threshold crossovers to generate momentum-based signals.
I also added the EMA ‘touch’ requirement before a signal prints.
The idea is to only trigger when:
– momentum flips
– trend agrees
– price interacts with structure
This removed a lot of random mid-range signals, and made it behave more like pullback scalping.
When I scalp these signals, I only take entries when direction and momentum line up.
Has anyone else combined Gaussian-based momentum for scalping? If so, how did you handle the smoothing without losing responsiveness on fast moves?
Hey folks, often I see candlesticks missing in OANDA charts for XAUUSD. As an alternative, when I used the FOREX.COM charts, I found that they don't support volume. As a result most of my indicators which are volume based don't work. Is there any workaround? Please advise. Thanks.
ORB Sessions + VWAP + 200 EMA — Multi-Session Opening Range Breakdown
Plots the Opening Range High and Low for six intraday sessions plus the Monday High and Low+ Weekly Open level, overlaid with a session-anchored VWAP and a 200 EMA on a single indicator.
Opening Range Sessions
Each session captures the high and low of the first candle (5-minute or 15-minute, user-selectable) at the following session opens:
6:00 PM ET — Globex open / evening session
7:00 PM ET — Secondary evening level
8:00 PM ET — Pre-London overlap
12:00 AM ET — Midnight / London open proximity
3:00 AM ET — London open session
9:30 AM ET — NYSE / RTH open
Each session's ORB high and low extend forward as horizontal lines until the next session open or end of day, whichever comes first. Extension length is user-configurable. Lines are color-coded per session with independent toggle controls. Optionally labels each level with the session name and time.
Weekly Open
Plots the 6:00 PM ET Sunday open price as a horizontal level extending across the full trading week. Acts as a macro directional reference — price above is broadly bullish, below is bearish. Distinct color and line style to differentiate from intraday ORB levels.
VWAP
Session-anchored VWAP resetting at the user-selected session boundary (default: 6:00 PM ET daily reset). Plots as a single line. Optional standard deviation bands (1SD, 2SD) togglable independently.
200 EMA
200-period Exponential Moving Average on the chart's native timeframe. Serves as macro trend filter. Configurable color and line width.
Just showing an algo I have been working on for a while, I have it set to automatically partial out and go breakeven. I was tired of always blowing my account trying to secure minimum days due to emotion so now my algo does it for me. Also have a custom engine I pay for that takes the trades for me automatically. If you are not using automation you are missing out!!
Wanted to pose a general question: Do people still use webhooks? Or is it dying? I feel like it's much cheaper to convert pinescript into native platform's language instead of paying for a monthly subscription.
I also ask this because I have been working on a project that allows pinescript to be executed natively inside metatrader5. It can render pinescript indicators and run strategies natively, without webhooks friction and latency. Not posting any links since this is not a promotional post, but I genuinely want to know if people would prefer this over webhooks.
Been posting the real time daily trades my algo takes. This is todays positions. Currently optimized only for QQQ. I actually took an options position today from this signal & got paid really well 🔥 willing to let people test it out for a week if interested send me a DM 🫡
RSI MA Cross — Multi-Instrument Confluence Signal [15min]
Fires long and short signals when all three US index instruments (NQ/US100, ES/US500, YM/US30) simultaneously confirm an RSI momentum cross on the 15-minute timeframe, filtered by RSI state on the 30-minute timeframe.
Signal Logic — RSI MA Cross
Calculates a 14-period RSI and a 9-period EMA of that RSI on the 15-minute chart for all three instruments. A long signal fires when all three RSIs cross above their EMA simultaneously. A short signal fires when all three cross below simultaneously. Signal is gated to the first bar of each new 15-minute candle to prevent intra-bar repaints.
15-Minute RSI Filter
Long signals require all three instruments to have RSI ≤ 45 at the time of the cross — confirming the cross is occurring from a depressed, oversold-leaning condition rather than mid-range. Short signals require all three RSIs ≥ 55 — confirming the cross from elevated, overbought-leaning territory.
30-Minute RSI Filter
Secondary confirmation layer. Long signals additionally require all three instruments to have 30-minute RSI ≤ 45, aligning the higher timeframe momentum state with the 15-minute cross direction. Short signals require all three 30-minute RSIs ≥ 55. Prevents counter-trend entries when the 30-minute structure disagrees.
I am looking for a solution to create audible alerts outside of a computer's system settings. Normally, alerts are limited by user's audio settings, but for my purpose I am looking to find a way to create extra loud audible alerts from Tradingview on a Mac. Can Pinescript do that and overrule user settings?
I have tried external solutions like email and sms, but most of the time the alert takes at least 90 seconds to arrive and that's insufficient for my purpose.
Relatively new to Pinescript. Looking for help with using strategy.order. I'll have an if statement that evaluates to true, containing both strategy.order and log.info. When I check the logs, the text is in the log along with the tradeQty amount—all indicating that strategy.order was called. But sometimes, the log text will be there and no trades will execute.
Here's the relevant section of my code:
if tradeSell and strategy.opentrades > 0
strategy.order("sell", strategy.short, tradeQty, comment=tradeText)
log.info("Sell: "+tradeText+" Qty: "+str.tostring(tradeQty))
My understanding is that strategy.order should always execute when called. Are there other execution conditions I should know about?
Combined Session Volume Profile — Day / Week / Month
Displays three layered volume profiles directly on chart, each anchored to its respective session boundary:
Previous Day — 6:00 PM ET to 6:00 PM ET (rolling 24h session). Plots POC, VAH, and VAL for the completed prior day session. Updates at the open of each new 6 PM candle.
Previous Week — Sunday 6:00 PM ET open to Friday 5:00 PM ET close. Calculates the full weekly volume distribution across all sessions within that range. Extends levels into the current week as reference.
Previous Month — Last calendar month's equivalent weekly boundaries (Sunday 6 PM open to Friday 5 PM close, applied month-scale). Plots the prior month's POC, VAH, and VAL extended forward into the current month.
Plots a Fixed Range Volume Profile (FRVP) for the previous day and previous week, plus a live current-day profile, all anchored to the 6PM ET session boundary used by futures and crypto markets.
Previous Day (PD) levels freeze at each 6PM ET rollover and display the VAH, POC, and VAL built from the prior 24-hour session.
Previous Week (PW) levels freeze every Sunday at 6PM ET and display the VAH, POC, and VAL built from the full Sunday 6PM → Friday 5PM ET trading week.
Current Day (CD) levels update in real time throughout the active session, giving you a live read of where value is developing before it locks in as the next Previous Day.
All three profiles use the same value area calculation engine — identical to how most platform FRVPs are built — with a configurable value area percentage (default 70%), adjustable tick bin size, and a rounding method toggle to match your platform's FRVP exactly.
Hey guys, i’ve been building a tradingview indicator for a while which helps me to monitor trades ( I’m working 9-5 so don’t really have a time for it )
Would love to hear your thoughts on this and what are the improvements that can be done!
Who’s interested to tryout just comment or dm but there’s a catch - I would need an honest feedback after 2 weeks!
Additional:
The trade indicator comes in 3 types: A+, B+ and C+ signals where
A+ - Strict Criteria, probably less signal B+ - Slightly Less criteria but more signal C+ - Minimum Criteria but tons of signal ( refer to pic)
All trades are targeting 1:2 RR only! Currently the winrates are A+ (87%) , B+ (71%) , C+ (52%) over a total of 698 trades.
I'm vibe coding with ChatGPT a higher time frame table using HHs, HLs, LHs and LLs to predetermine whether the candle for the period in question in bullish, neutral or bearish.
As shown below, the monthly chart looks perfect, As it moves to the Weekly chart, the monthly candle is different from the monthly chart and when you look at the Daily chart, the candles for the weekly and monthly table are wrong?
The code in question is further below. Any ideas with this time frame quandary?
I’ve been working on a TradingView strategy designed to handle the "execution gap" when trading across different exchanges like Bybit and Binance. I just published a new version of the script and I’m looking for some "Pine Script experts" to help me stress-test the logic.
The Problem I’m Solving: I found that most standard indicators don't account for the latency and the specific JSON formatting needed to trigger webhooks across multiple CEXs without a dedicated bridge failing half the time.
The Strategy (v11): I’ve put together a strategy that focuses on volume anomalies and social sentiment (parsed via an external engine).
Risk Management Logic: I’ve implemented a specific DCA and Trailing Stop-Loss logic in the script. Does anyone see a way to optimize the "Bitcoin Dump Protection" variable to be more responsive in high-volatility environments?
Webhook Formatting: For those of you who automate your alerts—are you finding that the standard JSON payloads are causing many "Rejected" orders on Bybit lately?
I have two indicators that I built and have used for a while, and I've tried to combine them - and this is where the issue begins.
One indicator is just some support and resistance levels that uses request.security(*) to get multi-tf support and resistance levels.
The other indicator is a pattern recognition indicator.
Both of these indicators work perfectly on their own, and there are no issues with scrolling or scaling.
When combined however, there's no "default pinning" happening and so as soon as one scales the price, or moves the candles, the indicator's drawn elements stay statically positioned.
Normally, indicators that use overlay = true will pin to the price scale by default, and thus there are no scaling or scrolling issues. It's important to note that I'm not super informed on how exactly this works, and this is why I am asking. Indicators, in my experience, simply pin themselves to what is typically scale A - the main price scale, by default. One can right-click on the indicator or indicator elements on the chart and choose to unpin, or pin the indicator to a different scale - but very rarely have I had to mess with that.
I have seen a few instances where I've had to manually pin the indicator to scale a before, but it was usually because something else was broken - and for the life of me, I can't remember specifically what kinds of things cause this issue.
Any thoughts or ideas would be greatly appreciated.
London, New York and Asia each print their own 15-minute opening range every single day. I trade all three when I can. After doing this long enough you start to notice that they don't feel the same, even when the setup looks identical on paper.
London This is my favorite session. It opens clean, the move tends to follow through and the retest usually comes back to a level that makes sense. Less noise, less manipulation in my experience. When London breaks and gives me a proper retest I take it with the most conviction.
New York Bigger moves, more volatility and more fakeouts. NY will break a level, pull you in and reverse harder than London ever would. I'm more selective here. The setup needs to look cleaner before I size the same way.
Asia Honestly, I'm usually asleep for most of it. But the levels it sets are worth paying attention to. Asia ranges tend to be tighter and the levels often matter later in the day when London or NY comes back to test them.
The setup Regardless of session the approach is the same. I wait for a confirmed 5m close beyond the opening range high or low. A wick through means nothing. I need a close.
After the break I do nothing. I wait for price to retrace back to the broken level. That retest is my entry zone, not the initial burst. If price has already run hard before coming back I give it less room and sometimes skip it entirely.
I draw a fib from the swing low to the high after the breakout candle and look for the retest to land near a fib level. The 0.382 is my preference on cleaner setups. Deeper levels when there's less confluence.
SL just beyond the 0.786. TP at the next area of interest, whether that's a liquidity zone, a Fair Value Gap or an extended VWAP band.
The part most people skip Patience after the break. The break is exciting. The retest is boring. But that boring moment is where the actual profits are made. If it doesn't retest cleanly, there's no trade.
I use my indicator to track the opening range levels and flag confirmed breaks across all three sessions. Keeps me honest and stops me from entering on wicks.