INDICATOR UPDATE:
Background: I've been working on an indicator for the Vector Candle Reversals I talk about. Many of you know they're a key part of my strategy.
If you've been following me for a while you'll know how powerful these Vector Reversals can be
Background: I've been working on an indicator for the Vector Candle Reversals I talk about. Many of you know they're a key part of my strategy.
If you've been following me for a while you'll know how powerful these Vector Reversals can be
So the indicator is almost good to go - it's 99% finished
However that's not the cool part.
The cool part is setting up alerts to send instantly to Telegram (with charts) whenever they occur. I have different groups for timeframes and type of reversal - ie 1hr/4hr, bear/bull.
However that's not the cool part.
The cool part is setting up alerts to send instantly to Telegram (with charts) whenever they occur. I have different groups for timeframes and type of reversal - ie 1hr/4hr, bear/bull.
BUT there are 16 possible conditions for alerts to fire.
Aaaaaand 400 allowable alerts / 16 conditions = would only allow for this to be set up on 25 coins max 🤦♂️
Because of this I had to implement some tricks to get around the 400 alerts limit allowed by TV 🤔
Aaaaaand 400 allowable alerts / 16 conditions = would only allow for this to be set up on 25 coins max 🤦♂️
Because of this I had to implement some tricks to get around the 400 alerts limit allowed by TV 🤔
However, with the original coding and outside service i'm using to send the alerts to Telegram there was an issue.
The alerts would fire correctly on all timeframes set... but could only ever send a 15m chart to Telegram 😭
So then I had to come up with another solution...
The alerts would fire correctly on all timeframes set... but could only ever send a 15m chart to Telegram 😭
So then I had to come up with another solution...
...to attach the right chart as per what timeframe the alert appeared on.
But i'm glad to say the solution I came up with WORKS! 🥳
This is huge because now instead of 25 coins I can now potentially have up to 400 coins alerting on all timeframes.
But i'm glad to say the solution I came up with WORKS! 🥳
This is huge because now instead of 25 coins I can now potentially have up to 400 coins alerting on all timeframes.
And it's huge not only because of that but because a Vector Candle Reversal (VCR) is a more powerful signal the higher the timeframe you go.
Ie, 15m you can scalp, 4hr there's potentially a good swing move to be had, and 1 day there's the possibility of a big dump.
Ie, 15m you can scalp, 4hr there's potentially a good swing move to be had, and 1 day there's the possibility of a big dump.
Soooo what i'm doing right now is setting up the alerts to send to Telegram into different channels based on the timeframe and type of VCR (ie bull or bear).
This will be massive, because if you see an influx of bear alerts and few bull then you could expect a dump coming
This will be massive, because if you see an influx of bear alerts and few bull then you could expect a dump coming
But this is a time consuming process because i'm having to test it to make sure it works correctly and then when i'm happy it does I would then have to set it up on each and every coin individually making edits to the code for each one.
The goal is to start with 100 coins.
The goal is to start with 100 coins.
I will make a post on the website (which still needs to be finished) explaining all of this and how it can best be utilised, but as for now i think I need another week of testing at least and then time to set up on 100 coins.
In the meantime here's a teaser:
In the meantime here's a teaser:
The indicator:
Note: These labels that are on this chart are NOT REPAINTED.
They print instantly. It isn't an indicator which sees how the following candles play out first.
It prints it as it sees it when the candles close and a Vector Reversal candlestick pattern has occurred.
They print instantly. It isn't an indicator which sees how the following candles play out first.
It prints it as it sees it when the candles close and a Vector Reversal candlestick pattern has occurred.
Telegram Alerts:
Image 1: Alert
Image 2: Chart at time of Alert
Image 3: Chart after alert
Image 1: Alert
Image 2: Chart at time of Alert
Image 3: Chart after alert
Another day, another bug fix.
Having to go in and re-do the code for all the tests I set up and start the testing again. No biggie.
On the plus side I think i've fully fixed another issue where some alerts weren't being pushed through to Telegram.
Having to go in and re-do the code for all the tests I set up and start the testing again. No biggie.
On the plus side I think i've fully fixed another issue where some alerts weren't being pushed through to Telegram.
The VCRs that have played out on Bitcoin
Here's a thread with a number of examples of VCRs and what this indicator points out.
The Telegram will have alerts for VCRs as soon as they happen.
The Telegram will have alerts for VCRs as soon as they happen.
https://twitter.com/Crypto_MM_/status/1485698300783337482?s=20
Shill me your favourite coin and tell me why I should include it in the first 100 coins I add to the Telegram alerts.
Best reason gets their coin included.
*Must be listed on Binance or FTX.
Best reason gets their coin included.
*Must be listed on Binance or FTX.
Damn bro, this why I NEEDED this indicator and the automatic alerts set up. Just adding $Avax into the system and see this.
Look at this shit on Avax. 3 Day VCR caught the top PERFECTLY.
Look at this shit on Avax. 3 Day VCR caught the top PERFECTLY.
No one?
Ok i'll just add in $HNT then seeing as it's one of the few coins positive in the Tokyo session
Ok i'll just add in $HNT then seeing as it's one of the few coins positive in the Tokyo session
Got a bug on one of the timeframes where it doesn't always alert. Annoying, but having the dev take a look at it to see what could be the issue 🧐
Dev has found the issue and implemented a fix.
Potentially promising.
I think with this fix the code will be good to go and I can go full blown with the testing! 🥳
Potentially promising.
I think with this fix the code will be good to go and I can go full blown with the testing! 🥳
• • •
Missing some Tweet in this thread? You can try to
force a refresh
