Get started

Community ideas

BTCUSD| Bitcoin’s Historic Parabolic Pattern🔥 Parabolic Pattern | Institutional COINBASE:BTCUSD Demand Mirrors Gold ETF Era 🔥 COINBASE:BTCUSD vs SP:SPX vs TVC:GOLD The market is whispering something big — and it's not retail noise this time. For the third straight quarter, listed corporations have outpaced ETFs in Bitcoin purchases, a seismic shift that echoes one key moment in history: the launch of the Gold ETF. Companies like NASDAQ:MSTR contiune to buy and others are following. Will NASDAQ:AAPL NASDAQ:META and NASDAQ:GOOG be next ? Let me know in the comments who you think will be next to buy? Back then, companies rushed to gold as a hedge against inflation and a store of value as fiat cracks widened. Fast forward to now — we're seeing the same institutional footprints in Bitcoin. The buy-the-dip narrative isn't just alive — it's being driven by corporate balance sheets. Rumors are circulating that the U.S. government plans to buy 1 million BTC — a move that would shake the global financial system to its core. If true, this isn’t just bullish — it’s historic. The last time governments got this aggressive with a hard asset was during the Gold Reserve buildup. Bitcoin isn’t just digital gold anymore — it’s becoming sovereign-level collateral. 📈💥 💬 Drop your thoughts below. Is this the beginning of the next parabolic era? In this episode, we break down the parabolic pattern forming on the chart, why it may signal the next explosive leg up, and how history is repeating with BTC playing the role of digital gold. 📊 Technical breakdown. On-chain behavior. Smart money moves. Don’t blink. Parabolas end in fireworks. I've been trading for 17 years 👍 If you found this useful, drop a like. 💬 Got questions or thoughts? Leave a comment below — I always respond and happy to help. 👍 Best Regards MartyBoots
COINBASE:BTCUSDLong
by MartyBoots
31
EURUSD Bullish Setup: Watching for a Break and Retest📈 Looking at EURUSD right now, we’re in a strong bullish structure 🔼 — but it’s clearly overextended 🚀 As we head into the end of the week, there’s still potential for more upside today ⬆️ — but ⚠️ be cautious, since Fridays often bring retracements as we move into the weekly close 🕒📉 🔍 I’m watching for a bullish opportunity if we get a break above the current equal highs, followed by a retest and failure to break back below 🧠📊 If that setup doesn’t materialize, we’ll simply step aside and abandon the idea 🚫 💬 Not financial advice — always trade at your own risk.
Long
by fxtraderanthony
Ethereum: Eyeing New Highs?Ethereum has surged recently and continues rising in turquoise wave B. The next target is a break above the June high, with potential upside to resistance at $4,107. A direct breakout above this level (27% probability) would suggest green wave alt. ended in April. However, our main scenario expects a reversal below $4,107, with turquoise wave C likely dragging ETH into the Long Target Zone between $935.82 and $494.15 to complete wave . 📈 Over 190 precise analyses, clear entry points, and defined Target Zones - that's what we do.
BINANCE:ETHUSDLong
by MarketIntel
Intel - The rally starts!Intel - NASDAQ:INTC - creates a major bottom: (click chart above to see the in depth analysis👆🏻) For approximately a full year, Intel has not been moving anywhere. Furthermore Intel now trades at the exact same level as it was a decade ago. However price is forming a solid bottom formation at a key support level. Thus we can expect a significant move higher. Levels to watch: $25.0 Keep your long term vision! Philip (BasicTrading)
NASDAQ:INTCLong
by basictradingtv
21
Debugging Pine Script with log.info()log.info() is one of the most powerful tools in Pine Script that no one knows about. Whenever you code, you want to be able to debug, or find out why something isn’t working. The log.info() command will help you do that. Without it, creating more complex Pine Scripts becomes exponentially more difficult. The first thing to note is that log.info() only displays strings. So, if you have a variable that is not a string, you must turn it into a string in order for log.info() to work. The way you do that is with the str.tostring() command. And remember, it's all lower case! You can throw in any numeric value (float, int, timestamp) into str.string() and it should work. Next, in order to make your output intelligible, you may want to identify whatever value you are logging. For example, if an RSI value is 50, you don’t want a bunch of lines that just say “50”. You may want it to say “RSI = 50”. To do that, you’ll have to use the concatenation operator. For example, if you have a variable called “rsi”, and its value is 50, then you would use the “+” concatenation symbol. EXAMPLE 1 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ //@version=6 indicator("log.info()") rsi = ta.rsi(close,14) log.info(“RSI= ” + str.tostring(rsi)) Example Output =>  RSI= 50 Here, we use double quotes to create a string that contains the name of the variable, in this case “RSI = “, then we concatenate it with a stringified version of the variable, rsi. Now that you know how to write a log, where do you view them? There isn’t a lot of documentation on it, and the link is not conveniently located.  Open up the “Pine Editor” tab at the bottom of any chart view, and you’ll see a “3 dot” button at the top right of the pane. Click that, and right above the “Help” menu item you’ll see “Pine logs”. Clicking that will open  that to open a pane on the right of your browser - replacing whatever was in the right pane area before. This is where your log output will show up.  But, because you’re dealing with time series data, using the log.info() command without some type of condition will give you a fast moving stream of numbers that will be difficult to interpret. So, you may only want the output to show up once per bar, or only under specific conditions.  To have the output show up only after all computations have completed, you’ll need to use the barState.islast command. Remember, barState is camelCase, but islast is not! EXAMPLE 2 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ //@version=6 indicator("log.info()") rsi = ta.rsi(close,14) if barState.islast  log.info("RSI=" + str.tostring(rsi)) plot(rsi) However, this can be less than ideal, because you may want the value of the rsi variable on a particular bar, at a particular time, or under a specific chart condition. Let’s hit these one at a time. In each of these cases, the built-in bar_index variable will come in handy. When debugging, I typically like to assign a variable “bix” to represent bar_index, and include it in the output. So, if I want to see the rsi value when RSI crosses above 0.5, then I would have something like: EXAMPLE 3 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ //@version=6 indicator("log.info()") rsi = ta.rsi(close,14) bix = bar_index rsiCrossedOver = ta.crossover(rsi,0.5) if rsiCrossedOver log.info("bix=" + str.tostring(bix) + " - RSI=" + str.tostring(rsi)) plot(rsi) Example Output =>  bix=19964 - RSI=51.8449459867 bix=19972 - RSI=50.0975830828 bix=19983 - RSI=53.3529808079 bix=19985 - RSI=53.1595745146 bix=19999 - RSI=66.6466337654 bix=20001 - RSI=52.2191767466 Here, we see that the output only appears when the condition is met. A useful thing to know is that if you want to limit the number of decimal places, then you would use the command str.tostring(rsi,”#.##”), which tells the interpreter that the format of the number should only be 2 decimal places. Or you could round the rsi variable with a command like rsi2 = math.round(rsi*100)/100 . In either case you’re output would look like: bix=19964 - RSI=51.84 bix=19972 - RSI=50.1 bix=19983 - RSI=53.35 bix=19985 - RSI=53.16 bix=19999 - RSI=66.65 bix=20001 - RSI=52.22 This would decrease the amount of memory that’s being used to display your variable’s values, which can become a limitation for the log.info() command. It only allows 4096 characters per line, so when you get to trying to output arrays (which is another cool feature), you’ll have to keep that in mind. Another thing to note is that log output is always preceded by a timestamp, but for the sake of brevity, I’m not including those in the output examples. If you wanted to only output a value after the chart was fully loaded, that’s when barState.islast command comes in. Under this condition, only one line of output is created per tick update — AFTER the chart has finished loading. For example, if you only want to see what the the current bar_index and rsi values are, without filling up your log window with everything that happens before, then you could use the following code: EXAMPLE 4 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ //@version=6 indicator("log.info()") rsi = ta.rsi(close,14) bix = bar_index if barstate.islast log.info("bix=" + str.tostring(bix) + " - RSI=" + str.tostring(rsi)) Example Output => bix=20203 - RSI=53.1103309071 This value would keep updating after every new bar tick. The log.info() command is a huge help in creating new scripts, however, it does have its limitations. As mentioned earlier, only 4096 characters are allowed per line. So, although you can use log.info() to output arrays, you have to be aware of how many characters that array will use. The following code DOES NOT WORK! And, the only way you can find out why will be the red exclamation point next to the name of the indicator. That, and nothing will show up on the chart, or in the logs. // CODE DOESN’T WORK //@version=6 indicator("MW - log.info()") var array rsi_arr = array.new() rsi = ta.rsi(close,14) bix = bar_index rsiCrossedOver = ta.crossover(rsi,50)  if rsiCrossedOver     array.push(rsi_arr, rsi) if barstate.islast     log.info("rsi_arr:" + str.tostring(rsi_arr))     log.info("bix=" + str.tostring(bix) + " - RSI=" + str.tostring(rsi)) plot(rsi) // No code errors, but will not compile because too much is being written to the logs. However, after putting some time restrictions in with the i_startTime and i_endTime user input variables, and creating a dateFilter variable to use in the conditions, I can limit the size of the final array. So, the following code does work. EXAMPLE 5 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ // CODE DOES WORK //@version=6 indicator("MW - log.info()") i_startTime         = input.time(title="Start", defval=timestamp("01 Jan 2025 13:30 +0000")) i_endTime           = input.time(title="End", defval=timestamp("1 Jan 2099 19:30 +0000")) var array rsi_arr = array.new() dateFilter = time >= i_startTime and time <= i_endTime  rsi = ta.rsi(close,14) bix = bar_index rsiCrossedOver = ta.crossover(rsi,50) and dateFilter // <== The dateFilter condition keeps the array from getting too big if rsiCrossedOver     array.push(rsi_arr, rsi) if barstate.islast     log.info("rsi_arr:" + str.tostring(rsi_arr))     log.info("bix=" + str.tostring(bix) + " - RSI=" + str.tostring(rsi)) plot(rsi) Example Output => rsi_arr: bix=20210 - RSI=56.9030578034 Of course, if you restrict the decimal places by using the rounding the rsi value with something like rsiRounded = math.round(rsi * 100) / 100 , then you can further reduce the size of your array. In this case the output may look something like: Example Output => rsi_arr: bix=20210 - RSI=55.6947486019 This will give your code a little breathing room. In a nutshell, I was coding for over a year trying to debug by pushing output to labels, tables, and using libraries that cluttered up my code. Once I was able to debug with log.info() it was a game changer. I was able to start building much more advanced scripts. Hopefully, this will help you on your journey as well.
AMEX:SPYEducation
by mwrightinc
5
July Doesn't Disappoint - S&P Nasdaq Dow Russell All RunningS&P All Time Highs Nasdaq All Time Highs Dow Jones closing in on All-Time Highs (and outperforming both S&P and Nasdaq recently) Russell 2000 playing catch up and moving higher This is melt-up at its finest Since US/China Trade Agreement and Middle East Ceasefire Agreement, markets have used these two events as further catalysts to continue the upside runs Stochastic Cycle with 9 candles suggesting a brief pause or pullback in the near-term, but a 3-5-10% pullback is still an opportunity to position bullish for these markets I'm only bearish if the markets show that they care with price action. The US Consumer isn't breaking. Corporate Profits aren't breaking. Guidance remains upbeat. Trump is Pro Growth and trolling Powell on the regular to run this economy and market HOT demanding cuts (history says that's a BUBBLE in the making if it's the case) Like many, I wish I was more aggressive into this June/July run thus far, but I'm doing just fine with steady gains and income trades to move the needle and still having plenty of dry powder on the sidelines for pullbacks Markets close @ 1pm ET Thursday / Closed Friday for 4th of July Enjoy the nice long weekend - back at it next week - thanks for watching!!!
SP:SPX
by ChrisPulver
BTCUSD 7/3/2025Come Tap into the mind of SnipeGoat, as he gives you a Wonderful update to his 7/1/2025 call-out which PLAYED OUT PERFECTLY!!!! If you are not convinced by now, what are you doing... _SnipeGoat_ _TheeCandleReadingGURU_ #PriceAction #MarketStructure #TechnicalAnalysis #Bearish #Bullish #Bitcoin #Crypto #BTCUSD #Forex #NakedChartReader #ZEROindicators #PreciseLevels #ProperTiming #PerfectDirection #ScalpingTrader #IntradayTrader #DayTrader #SwingTrader #PositionalTrader #HighLevelTrader #MambaMentality #GodMode #UltraInstinct #TheeBibleStrategy
BITSTAMP:BTCUSD
by TheeSnipeGoat
GBPUSD politics and the upcoming NFPFX_IDC:GBPUSD trading was influenced by politics in UK. The pair recovered half of the losses, but the downside risk still remains. NFP could be a trigger. Let's dig in. MARKETSCOM:GBPUSD Let us know what you think in the comments below. Thank you. 77.3% of retail investor accounts lose money when trading CFDs with this provider. You should consider whether you understand how CFDs work and whether you can afford to take the high risk of losing your money. Past performance is not necessarily indicative of future results. The value of investments may fall as well as rise and the investor may not get back the amount initially invested. This content is not intended for nor applicable to residents of the UK. Cryptocurrency CFDs and spread bets are restricted in the UK for all retail clients.
by Marketscom