Our P73 Signal system just issued something that has not happened before - signals based on the monitoring of the weekly timeframe.
Let us remind you that the system automatically "runs through" the TOP-200 crypto assets by market capitalization using the P73 Trend & Target Dynamics indicator. Across different timeframes.
In the weekly and monthly timeframe - exclusively signals for investment decisions, not for trading. Because after a signal to transition to a stable uptrend according to our indicator on the weekly timeframe, the price, conditionally, can drop -40% on some altcoin. But then, over the long term, it will, again conditionally, rise +500%.
Example - the same BTC, one can see how the previous bull run was worked out. Now the bull run is in position, let's follow the trend change and it will be essential to cover positions in time. Fully or partially. On the same signals of potential highs on this timeframe.
What did P73 Signal send this first time? On the occasion of the first time, we will announce it fully:
- Potential high on the weekly timeframe:
-- #BTC (yes, just like that, but there will be a remark after the list),
-- #DOGE,
-- #RAY (also for it - Strong signal),
-- #MEW,
-- #BDX,
-- #VIRTUAL.
An important remark regarding BTC and other assets - IF the assets transition to a stable uptrend on the weekly timeframe in the next three weeks (including the current one) - then the signals of potential highs on this timeframe will be broken. Simply because a bull run will begin. If not - this is potentially bad news for the crypto market as a whole. At least a range period for a couple of weeks instead of the beginning of a pre-New Year rally.
- Transition to a stable downtrend (suddenly) on the weekly timeframe:
-- #KAS. Targets on the screen. However, we think that if an active bull market begins, none of the targets will be reached. One should consider the inertia of the indicator here.
Why did the signals for the weekly timeframe come now, on Friday, and not at the beginning of the week?
Unfortunately, because there was a frustrating and silly mistake in the code. We just found it, luckily it was in the first week of active growth. By the way, we found it thanks to our subscriber.