Concept Dual SuperTrendSimple SuperTrend indicator giving you the option to display two SuperTrends on a single script plus additional customization features. Dual setup inspired by Income Sharks 🦈
Komut dosyalarını "crypto" için ara
Auto Fibonacci From Previous High & Low w/ Percentages & AlertsAUTO FIBONACCI FROM PREVIOUS D/W/M/Q/Y HIGH & LOW WITH PERCENTAGES & ALERTS
This is an auto fibonacci level generating indicator that uses the high and low from the previous day, week, month, quarter or year. It also has a table with real time updates of how far away the nearest fibonacci levels are above and below the current price, represented in percentages. It includes alerts for each level as well if you want to be notified of price crossing fibonacci levels without watching the chart.
***HOW TO USE***
Fibonacci levels are also known as the golden ratio and are popular levels for traders to use as support and resistance levels. Expect price to bounce off of these levels regularly.
The previous high and low are marked as white lines. These are very important levels so make sure to pay attention when price reaches these lines.
Make sure to check out the higher timeframes for major levels.
Each fibonacci line retracement and extension up to the 3.272 level in each direction is displayed as red or green depending on whether price is above or below that level.
The retracement levels used are: previous high, .117, .236, .382, .5, .618, .786, .883, previous low, 1.272, 1.618, 2, 2.272, 2.618, 3 and 3.272.
The extension levels used are: .272, .618, 1, 1.272, 1.618, 2, 2.272, 2.618, 3 and 3.272.
In the indicator settings input tab you can quickly change the timeframe used, turn lines on/off, upper line colors, lower line colors, previous high and low line colors, line width, turn percentage table on/off, change the color of the percentage table and move the percentage table to a different location on the chart.
The indicator includes alerts for each fibonacci level as well, just set your fibonacci timeframe on your favorite ticker and turn on tradingview alerts for alert() calls.
***MARKETS***
This indicator can be used as a signal on all markets, including stocks, crypto, futures and forex.
***TIMEFRAMES***
This auto fibonacci indicator can be used on all timeframes.
***TIPS***
Try using numerous indicators of ours on your chart so you can instantly see the bullish or bearish trend of multiple indicators in real time without having to analyze the data. Some of our favorites are our Buy & Sell Pressure Colored Candles, Directional Movement Index + Fisher Transform, Volume Profile W/ Buy & Sell Pressure Labels, Auto Support And Resistance and Money Flow Index in combination with this Auto Fibonacci. They all have real time Bullish and Bearish labels or percentage gap info as well so you can immediately understand each indicator's trend and how far away major levels are in percentages.
HODL LINE [AstrideUnicorn]This indicator determines periods of bull market when a buy-and-hold investor can hold the asset, and bear market periods when they should avoid holding it. Though it was designed primarily with cryptocurrencies in mind, it can be successfully used for any market.
Technically, the indicator is an asymmetric trend filter aimed to account for the fact that market sell-offs tend to be sharper than up-trends. The algorithm has two regimes – with and without price smoothing.
HOW TO USE
The step-like line is the main trend filter. It is colored green in an uptrend and red in a downtrend. When the smoothing is on, in addition to the trend filter, the indicator plots a purple line. It is a Hull Moving Average (HMA) of the price. In this case, the indicator uses this line instead of the price to find crossings with the trend filter.
When the price or the smoothed line crosses the trend filter above, it is an uptrend signal. The indicator marks such crossings with green circles. It also colors the chart background green in an uptrend. The price or the purple line crossing the trend filter below means a downtrend signal. Downtrend signals show as red circles. The chart background in a downtrend turns red.
SETTINGS
Sensitivity – a dropdown list that allows the user to choose an averaging period of the indicator. Users can select a value for sensitivity from a predetermined set that better suits their investment horizon.
Use Smoothing – turns on and off smoothing of the price with HMA. With the smoothing turned on, the indicator responds slower to price changes, but at the same time produces less amount of false signals.
Relative Strength Index JoaScript desarrollado para RSI
Modificado para una correcta entrada y salida de los mercados Cryptos
Fukuiz TrendThis indicator base on RSI of 2 different periond.
#A brief introduction to RSI #
The relative strength index (RSI) is a momentum indicator used in technical analysis that measures the magnitude of recent price changes to evaluate overbought or oversold conditions in the price of a stock or other asset. The RSI is displayed as an oscillator (a line graph that moves between two extremes) and can have a reading from 0 to 100. The indicator was originally developed by J. Welles Wilder Jr. and introduced in his seminal 1978 book, “New Concepts in Technical Trading Systems.”
Traditional interpretation and usage of the RSI are that values of 70 or above indicate that a security is becoming overbought or overvalued and may be primed for a trend reversal or corrective pullback in price. An RSI reading of 30 or below indicates an oversold or undervalued condition.
#In this indicator#
I see that you can use 2 RSI with different periond to suggest Bullish trend and Bearish trend.
#Conditions between short and long RSI crossing#
Crossover = Bullish trend (blue zone)
Crossunder = Bearish trend (red zone)
Runners & Laggers (scanner)Firstly, seems to me this may only work with crypto but I know nothing about the other sectors so i could be wrong. I was trying to think up a good way to find moving coins(other than by volume bc theres holes in the results when using it this way). Thought this was an interesting concept so decided to publish it as I've seen no others like it (though i did not extensively search for it. We need to start with a little Tradingview(TV) common knowledge. When there is no update of trades/volume in a candle TV does not print the candle. So when looking at (let's say) a 1 second chart, if the coin being observed by the user has no update from a trade in the time of that 1 sec candle it is skipped over. This means that a coin with a ton of volume might fill an entire 60 seconds with 60 candles and conversely with a low volume coin there could be as little as 0 1-second candles. BUT even for normally low volume coins, when a pump is beginning with the coin it could literally go from 0 1-second candles within a minute to 60 1-second candles within the next minute. ***NOTE: This DOES NOT show ANY information if the coin is going up or down but rather that a LOT more trading volume is occurring than normal.*** What this script does is scans (via request.security feature) up to 40 coins at a time and counts how many candles are printed within a user set timespan calculated in minute. 1 candle print per incremented timeframe that the chart is on. ie. if the chart is a 1 min chart it counts how many 1 min candles are printed. So, (as is in the captured image for the script) if you wanted to count how many 5 second candles are printed for each coin in 1 min then you would have to put the charts timeframe on 5sec and the setting titled 'Window of TIME(in minutes) to count bars' as 1.0 (which bc it's in minutes 1.0m = 60sec and bc 60s / 5s = 12 there would be 12 possible values that each coin can be at depending on how many bars are counted within that 1min/60sec. *** I will update to show an image of what I'm talking about here. Now, the exchange I'm scanning here is Kucoin's Margin Coins. There are 170 something coins total but I removed a few i didn't care for to make it a round 40 coins per set (there being 4 sets of 40 coins total=160 coins being scanned). To scan all 4 sets the indicator must be added 4 times to the chart and a different 'set' selected for each iteration of the script on the chart. Free users can only scan 3 at the most. All others can scan all 4 sets. In the script you can change the exchange and coins as necessary. If there done so and there are not 40 coins total just put '' '' in the extra coins spots that are not filled and the script will skip over these blankly filled spots. The suffix (traded pair) for the tickerID on all Kucoin's Margin Coin's is USDT so that's what i have inputted in the main function on line 46 (will need to be changed if that differs from the coins you want to scan. Next in the line of settings is 'Window of TIME(in minutes) to count bars' which has already been discussed. Following that is the setting "Table Shows" which the results are all in a table and the table will present the coins that have either "Passed" or "Failed" depending on which you choose. The next setting determines what passes or fails. If there are 12 possible rows for the coins to be in (as described above) then this setting is the "Pass/Fail Cutoff" level. So if you want to show all the coins that are in rows 11 and 12 (as in the image at top) then 11 should be selected here. At this point you will see all the coins that have a lot of volume in them. Finding coin names in the table that are usually not with a ton of volume will present your present movers. NOTE: coins like BTC and ETH will almost always be in these levels so it does not indicate anything different from the norm of these coins. Last setting is the ability to show the table on the main window or not. Hope you enjoy and find use in it. BTW this screener format is the same as the others I have published. If you like, check those out too. If you find difficulty using then refer to those as well as they have additional info in them on how to use the scanner and its format. Lastly, in the script is the ability to print the plots and labels but I commented them out bc its really just a jumbled mess. In the commented out sections there is a Random Color Function (provided by @hewhomustnotbenamed which was developed on the basis of Function-HSL-color by @RicardoSantos. All right, peace brothers....and sisters.
**** Also, I see how the "levels" could be confusing so I will put them into a % format soon (probably not today) so that the "Pass/Fail Cutoff" can be in % format so that if "passed" is chosen and 50% is chosen (in the new setting that will be changed) then it'll show you all the coins that have more than 50% of the bars printed within the time window chosen. Goodluck in all your trading adventures. ChasinAlts out.
Momentum With Bullish & Bearish LabelMOMENTUM WITH BULLISH AND BEARISH SIGNALS
This is a momentum oscillator that paints red or green depending on whether Momentum is above or below the zero line. It includes a label on the right hand side that will reflect the bullish or bearish direction of the current momentum by changing colors to red or green and text telling you Bullish or Bearish.
***HOW TO USE***
When Momentum is above zero, it is bullish. When Momentum is below zero it is bearish.
A label on the right side will update in real time to tell you if momentum is Bullish or Bearish for faster recognition of the trend.
When momentum is above the zero line(Bullish) but trending downward, a second label will show up in purple to notify you of a change in momentum direction.
When momentum is below the zero line(Bearish) but trending upward, a second label will show up in purple to notify you of a change in momentum direction.
This indicator was built to help you quickly identify the Bullish or Bearish nature of the current Momentum using colors as well as a live color changing label so you can glance at the label and understand it's direction without analyzing the indicator data.
***MARKETS***
This indicator can be used as a signal on all markets, including stocks, crypto, futures and forex.
***TIMEFRAMES***
This momentum indicator can be used on all timeframes.
***TIPS***
Try using numerous indicators of ours on your chart so you can instantly see the bullish or bearish trend of multiple indicators in real time without having to analyze the data. Some of our favorites are our Auto Fibonacci, Directional Movement Index, Volume Profile, Auto Support And Resistance and Money Flow Index in combination with this Momentum Oscillator. They all have real time Bullish and Bearish labels as well so you can immediately understand each indicator's trend.
Volatility ChannelThis script is based on an idea I have had for bands that react better to crypto volatility. It calculates a Donchian Channel, SMMA-Smoothed True Range, Bollinger Bands (standard deviation), and a Keltner Channel (average true range) and averages the components to construct its bands/envelopes. This way, hopefully band touches are a more reliable indicator of a temporary bottom, and so on. Secondary coloring for strength of trend is given as a gradient based on RSI.
[Nekonyam] Auto Select Currency Binance Open InterestDisplays open interest in crypto currencies.
It automatically changes the open interest displayed according to the virtual currency displayed on the chart.
It works even if you are viewing an exchange other than Binance.
It shows open interest according to the base currency, so it works with BTCEUR and other currencies.
ETHBTC, for example, shows the open interest in ETH.
If you are viewing a currency that does not provide open interest from Binance to TradingView, it will not work.
It will not work if ETFs, CME futures, etc. are displayed. (such as GBTC or BTC1!)
仮想通貨のオープンインタレストを表示します。
チャートに表示している仮想通貨に合わせて自動で表示するオープンインタレストを変えます。
バイナンス以外の取引所を表示していても使えます。
ベース通貨に合わせてオープンインタレストを表示しているので、BTCEURなどでも使えます。
ETHBTCなどはETHのオープンインタレストが表示されます。
BinanceからTradingViewにオープンインタレストが提供されていない通貨を表示している場合は使えません。
ETFやCME先物などを表示している場合は使えません。(GBTCやBTC1!など)
MACRO BTC HEALTH 1WThis indicator is used as MACRO tool to view the outlook of BTC on the 1W time frame to illustrate (BLX chart works best)
BTC's price action and where it's at, it helps provide an indication of the crypto market's current health as BTC health is an overall indicator in the crypto market as a whole.
This indicator uses historic data to fit between 4 bands fitted to MA, top(red) when BTC is overheated, 2 bands in middle(yellow) when BTC in fair value, and bottom band(blue) when BTC is oversold
I combined MA that fit BTC 1W chart precisely to show when BTC looks overheated vs over sold using historic data.
When BTC is in the top bands historically overheated.
When BTC is in the middle it is fighting at fair value with the 2 yellow lines in the middle, bullish when above yellow lines, as they act as support, and in downtrend when price is below yellow lines and can act as resistance.
Historically the 200W MA is where BTC finds support at an oversold level at the bottom blue line.
When two yellow lines in middle cross downwards historically results in a downtrend to the bottom oversold line (blue). and when two yellow lines cross up and BTC holds them as support bullish trend continues until it is overheated passed the red band.
This indicator is not meant for day trading but is meant to illustrate a MACRO view of BTC current situation from a zoomed-out view, and to help illustrate to investors where things are at so they leave emotions out of the market and can make decisions based on BTC current levels using Historic data. Pro tip use bottom line(blue, oversold) as an opportunity to buy in and top line red(overheated) to scale out of positions, LONG TERM CRYPTO IS BULLISH BUT GREAT TO GET AN OUTLOOK OF THE CURRENT STATE OF BTC, WHILE ALSO USING MACRO ECONOMIC SENTIMENT IRL, FUNDAMENTAL ECONOMIC DECISIONS, ECONOMIC CONDITIONS/ENVIRONMENT, ECONOMIC HEALTH ,FED DECISIONS, INTEREST RATE ENVIRONMENT AND OF COURSE LOOKING AT CRYPTO ADOPTION.
Hope this indicator helps leave emotions out of the market by providing a good guide of BTC sentiment, and its current health to make decisions accordingly. NFA but good to envision the MACRO BTC HEALTH at the 1W timeframe.
Volatility indicator based on ATR Hello,
I'm sharing to you a volatility indicator I've done in the last few weeks based on ATR. There is multiple functionalities on this indicator, the first one is an overlay displaying when an asset is in an "overvolatily zone"
(displayed with red cross) and when we are in an "undervolatily zone" (displayed with green cross). You can change the sensibility of the signals in the parameters if you wish to have more or less greedy signals
(it will only modify the overvolatility signals). By the way those signals are not working for week-ends because volatility works differently on week-ends and it's not a good idea to count week-ends in the calculations, so do not worry if you see no signals on weekends.
Second part of the indicator is something I called "Atr bands" it's an equivalent to the famous Bollinger-Bands but based on ATR. I haven't backtested them yet but they seems really interesting in low ut
(15 mins seems to be the best ut for those) and they seems pretty bad in high ut so they can maybe be useful for low ut scalping.
Last thing, there is a parameter allowing you to display bands on the week-ends so you can easily see where the indicator won't give signals.
I would be really happy if I could have some feedsback if you try the indicator :)
Have a wonderful day
HighTimeframeTimingLibrary "HighTimeframeTiming"
@description Library for sampling high timeframe (HTF) historical data at an arbitrary number of HTF bars back, using a single security() call.
The data is fixed and does not alter over the course of the HTF bar. It also behaves consistently on historical and elapsed realtime bars.
‼ LIMITATIONS: This library function depends on there being a consistent number of chart timeframe bars within the HTF bar. This is almost always true in 24/7 markets like crypto.
This might not be true if the chart doesn't produce an update when expected, for example because the asset is thinly traded and there is no volume or price update from the feed at that time.
To mitigate this risk, use this function on liquid assets and at chart timeframes high enough to reliably produce updates at least once per bar period.
The consistent ratio of bars might also break down in markets with irregular sessions and hours. I'm not sure if or how one could mitigate this.
Another limitation is that because we're accessing a multiplied number of chart bars, you will run out of chart bars faster than you would HTF bars. This is only a problem if you use a large historical operator.
If you call a function from this library, you should probably reproduce these limitations in your script description.
However, all of this doesn't mean that this function might not still be the best available solution, depending what your needs are.
If a single chart bar is skipped, for example, the calculation will be off by 1 until the next HTF bar opens. This is certainly inconsistent, but potentially still usable.
@function f_offset_synch(float _HTF_X, int _HTF_H, int _openChartBarsIn, bool _updateEarly)
Returns the number of chart bars that you need to go back in order to get a stable HTF value from a given number of HTF bars ago.
@param float _HTF_X is the timeframe multiplier, i.e. how much bigger the selected timeframe is than the chart timeframe. The script shows a way to calculate this using another of my libraries without using up a security() call.
@param int _HTF_H is the historical operator on the HTF, i.e. how many bars back you want to go on the higher timeframe. If omitted, defaults to zero.
@param int _openChartBarsIn is how many chart bars have been opened within the current HTF bar. An example of calculating this is given below.
@param bool _updateEarly defines whether you want to update the value at the closing calculation of the last chart bar in the HTF bar or at the open of the first one.
@returns an integer that you can use as a historical operator to retrieve the value for the appropriate HTF bar.
🙏 Credits: This library is an attempt at a solution of the problems in using HTF data that were laid out by Pinecoders in "security() revisited" -
Thanks are due to the authors of that work for an understanding of HTF issues. In addition, the current script also includes some of its code.
Specifically, this script reuses the main function recommended in "security() revisited", for the purposes of comparison. And it extends that function to access historical data, again just for comparison.
All the rest of the code, and in particular all of the code in the exported function, is my own.
Special thanks to LucF for pointing out the limitations of my approach.
~~~~~~~~~~~~~~~~|
EXPLANATION
~~~~~~~~~~~~~~~~|
Problems with live HTF data: Many problems with using live HTF data from security() have been clearly explained by Pinecoders in "security() revisited"
In short, its behaviour is inconsistent between historical and elapsed realtime bars, and it changes in realtime, which can cause calculations and alerts to misbehave.
Various unsatisfactory solutions are discussed in "security() revisited", and understanding that script is a prerequisite to understanding this library.
PineCoders give their own solution, which is to fix the data by essentially using the previous HTF bar's data. Importantly, that solution is consistent between historical and realtime bars.
This library is an attempt to provide an alternative to that solution.
Problems with historical HTF data: In addition to the problems with live HTF data, there are different issues when trying to access historical HTF data.
Why use historical HTF data? Maybe you want to do custom calculations that involve previous HTF bars. Or to use HTF data in a function that has mutable variables and so can't be done in a security() call.
Most obviously, using the historical operator (in this description, represented using { } because the square brackets don't render) on variables already retrieved from a security() call, e.g. HTF_Close{1}, is not very useful:
it retrieves the value from the previous *chart* bar, not the previous HTF bar.
Using {1} directly in the security() call instead does get data from the previous HTF bar, but it behaves inconsistently, as we shall see.
This library addresses these concerns as well.
Housekeeping: To follow what's going on with the example and comparisons, turn line labels on: Settings > Scales > Indicator Name Label.
The following explanation assumes "close" as the source, but you can change it if you want.
To quickly see the difference between historical and realtime bars, set the HTF to something like 3 minutes on a 15s chart.
The bars at the top of the screen show the status. Historical bars are grey, elapsed realtime bars are red, and the realtime bar is green. A white vertical line shows the open of a HTF bar.
A: This library function f_offset_synch(): When supplied with an input offset of 0, it plots a stable value of the close of the *previous* HTF bar. This value is thus safe to use for calculations and alerts.
For a historical operator of {1}, it gives the close of the *last-but-one* bar. Sounds simple enough. Let's look at the other options to see its advantages.
B: Live HTF data: Represented on the line label as "security(){0}". Note: this is the source that f_offset_synch() samples.
The raw HTF data is very different on historical and realtime bars:
+ On historical bars, it uses a flat value from the end of the previous HTF bar. It updates at the close of the HTF bar.
+ On realtime bars, it varies between and within each chart bar.
There might be occasions where you want to use live data, in full knowledge of its drawbacks described above. For example, to show simple live conditions that are reversible after a chart bar close.
This library transforms live data to get the fixed data, thus giving you access to both live and fixed data with only one security() call.
C: Historical data using security(){H}: To see how this behaves, set the {H} value in the settings to 1 and show options A, B, and C.
+ On historical bars, this option matches option A, this library function, exactly. It behaves just like security(){0} but one HTF bar behind, as you would expect.
+ On realtime bars, this option takes the value of security(){0} at the end of a HTF bar, but it takes it from the previous *chart* bar, and then persists that.
The easiest way to see this inconsistency is on the first realtime bar (marked red at the top of the screen). This option suddenly jumps, even if it's in the middle of a HTF bar.
Contrast this with option A, which is always constant, until it updates, once per HTF bar.
D: PineCoders' original function: To see how this behaves, show options A, B, and D. Set the {H} value in the settings to 0, then 1.
The PineCoders' original function (D) and extended function (E) do not have the same limitations as this library, described in the Limitations section.
This option has all of the same advantages that this library function, option A, does, with the following differences:
+ It cannot access historical data. The {H} setting makes no difference.
+ It always updates at the open of the first chart bar in a new HTF bar.
By contrast, this library function, option A, is configured by default to update at the close of the last chart bar in a HTF bar.
This little frontrunning is only a few seconds but could be significant in trading. E.g. on a 1D HTF with a 4H chart, an alert that involves a HTF change set to trigger ON CLOSE would trigger 4 hours later using this method -
but use exactly the same value. It depends on the market and timeframe as to whether you could actually trade this. E.g. at the very end of a tradfi day your order won't get executed.
This behaviour mimics how security() itself updates, as is easy to see on the chart. If you don't want it, just set in_updateEarly to false. Then it matches option D exactly.
E: PineCoders' function, extended to get history: To see how this behaves, show options A and E. Set the {H} value in the settings to 0, then 1.
I modified the original function to be able to get historical values. In all other respects it is the same.
Apart from not having the option to update earlier, the only disadvantage of this method vs this library function is that it requires one security() call for each historical operator.
For example, if you wanted live data, and fixed data, and fixed data one bar back, you would need 3 security() calls. My library function requires just one.
This is the essential tradeoff: extra complexity and less robustness in certain circumstances (the PineCoders function is simple and universal by comparison) for more flexibility with fewer security() calls.
Mayer Multiple StrategyCreated by Trace Mayer, the Mayer Multiple is calculated dividing the current price of Bitcoin by its 200-day moving average. This simple script allows to backtest strategies based on Mayer Multiple levels, which can be easily adjusted. It can be tested on any chart and any timeframe.
Percentile Major Move Indicator This indicator is a powerful tool for understanding how big of a move a product, crypto, or currency has recently had.
Anything inside of the green bars is a standard move with a 68% chance of happening based on your chart timeframe.
Any move that touches the red lines to the upside or downside has a 2%+ chance of happening in either direction.
This is a powerful indicator but just one point of data and should be used as such.
sma RSI & sudden buy and sell Strategy v1This strategy uses mostly three things:-
1. average RSI (sma rsi over a period)
2. sudden buy and sudden sell (usually to infer the change in trend or direction)
3. various EMAs ( used as a filter)
I mostly build it to work on a 3min crypto chart but it should work on any timeframe or any symbol.
Settings - Length -RSI length (hardly needed to be changed but sometimes it doubles the net profit)(+/-2)
instant length - a sudden increase or decrease in the price calculated by the length of RSI (+/-10)
Bars - No of candles to verify before starting /closing the strategy (+/-20)
Lookbackno2 - another variable to verify ema opening/closing (hardly needed to change)
emas - values of different EMAs (you can change if you want but I don't recommend it though)
over40 and over60 - the value of overbuying and overselling(+/-10)
In future, I will probably add ADX or use machine learning to filter out results
It works well considering 0.05% commission per entry and exit (total of 1% per trade)
you can message me for any query or suggestions.
Combo Ichimoku + CDC Action Zone by fukuizThis indicator combines the famous indicators Ichimoku and CDC ActionZone.
#A brief introduction to Ichimoku #
The Ichimoku Cloud is a collection of technical indicators that show support and resistance levels, as well as momentum and trend direction. It does this by taking multiple averages and plotting them on a chart. It also uses these figures to compute a “cloud” that attempts to forecast where the price may find support or resistance in the future.
#A brief introduction to CDC ActionZone #
CDC ActionZone is a very simple system, utilizing just two exponential moving averages. The 'zones' in which different 'actions' should be taken are highlighted in different colors. Calculations for the zones
They are based on the relative position of price to the two EMA lines and the relationship between the two EMAs.
The CDC ActionZone was developed by Piriya333, a Thai technical analyst.
#How to use #
The basic method for using Ichimoku+CDC ActionZone is to follow the green/red color and the cloud.
Buy condition
-Buy when the bar closes in green and closes above the cloud
Sell condition
-sell when the bar closes in red.
multicolor Bollinger Bands (BB <-> KC)Concept:
After every low volatile phase comes a high volatile phase and after every high volatile phase comes a low volatile phase.
If the Bollinger bands are smaller then the Keltner channel (colored red), the price action is low in volatility… meaning a breakout (colored green) will happen soon.
If Bollinger band is bigger than the Keltner channel = green
If Bollinger band is smaller than the Keltner channel = red
Displaying the Keltner Channel is optional
If multicolor BB is disabled, BB color = blue (default color)
Customise colors to your liking under settings -> style
-----------------------------------
To get alerts for all coins
1. visit » tradingview.com/crypto-screener
2. set the filter to »
Bollinger Upper Band (20) below Keltner Channels Upper Band (20)
Bollinger Lower Band (20) above Keltner Channels Lower Bands (20)
3. add your own custom filters, like: exchange, marketcap, etc…
4. choose the timeframe you want
5. enable alerts
Bollinger Stop StrategyClassic trading strategy using the Bollinger Bands indicator.
Strategy
Only stop orders are used to enter and exit the market.
If the price crossed the upper boundary of the Bollinger Bands, then enter into a long position (and close a short position).
If the price crosses the bottom of the Bollinger Bands, then enter short (and close a long position).
Short positions can be disabled (optional).
For
Crypto-currency market
Preferably coin/fiat (BTC/USD, ETH/USDT, etc)
Timeframe 1 day only
Settings
The original settings for the Bollinger Bands indicator are set by default.
Perhaps a better result will be if you use non-original price source.
Works well with OHLC4 and HLCC4.
The Weekend Line: line from end of Friday to end of Sunday v5This script draws a line from the start of the weekend at the end of Friday and projects the line to the end of Sunday to view the opening levels for weekend trading. Particularly useful in markets that trade over the weekend such as Forex and Cryptocurrencies. For accurate use, the time frame should be set to 1h or lower.
McDonald's Pattern [LuxAlgo]Tradingview asked, we delivered. This script fits a cubic Bezier curve using tops/bottoms in order to approximate a McDonalds pattern, a popular meme pattern in the crypto trading community.
Traditionally the McDonalds pattern is described by an M pattern with deep retracement (> 50%), forming a McDonalds logo.
Please note that this indicator is a meme & should not be taken seriously. Some aspects of this indicator are not real-time and meant for descriptive analysis alongside other components of this script, in this case, for entertainment purposes. We suggest looking through our other open-source scripts if you’re looking for more serious tools.
🔶 USAGE
The script fits Bezier curves using specific tops/bottoms as control points. When the distance between tops and bottoms values is relatively small, the user can more easily identify the pattern.
A score is shown on the top right of the chart, aiming to return how close the returned pattern is to the original logo.
A regular Mcdonalds pattern would return a red background, while an inverted pattern would return a green one.
🔶 SETTINGS
Length: Sensitivity of tops/bottoms detection. The method does not make use of pivot points, using rolling maximums/minimums instead.
Use First Bar As Vertex: Use the price and bar index of the last bar as vertex.
StableCoin MC vs Total MC by Crypto5Max In this indicator you will find the sum of all stable coins (market cap) divided by the total crypto market cap.
I believe there's a positive correlation between stable coins issuance and BTC's(and other coins) price appreciation. Or shortly put, to me the rising levels of stable coins represent increased levels of buying power (and adoption) waiting on the sidelines.
Here, I am taking the total market cap of all stable coins and dividing it by the total crypto market cap to get a ratio. Note, only ~85% of all stable coins are calculated (rest are not on TV), however, it should still be a fairly good representation. Some of the stable coins are already locked in smart contracts for yield farming and what not. I'd also say, there's interesting 2-year long channel that's developing currently. That said, take this indicator with a grain of salt as we still have a limited set of data.
Yours truly
