A recent decision by Binance has once again sparked a major discussion about risk sentiment across the crypto market. According to multiple reports, the exchange has added four altcoins to its “Monitoring Tag” list, which is usually seen as an early warning sign of a token’s future delisting risk.
[Source](Binance Monitoring Tag Alert Triggers Sharp Drop in AEUR, PYR, SCRT and VANRY Tokens)
The list includes four projects that Binance is monitoring—Anchored Coins AEUR, Vulcan Forged PYR, Secret SCRT and Vanar Chain VANRY.
The market reacted quickly after the announcement. The PYR and SCRT tokens in particular suffered a sharp drop of almost 11% in a short period of time. Many investors quickly exited their positions as the delisting panic spread among investors, which further increased the selling pressure.
On the other hand, not all tokens reacted in the same way. VANRY was relatively stable and even saw a slight increase. AEUR was again almost flat, as it is a euro-pegged stablecoin that is relatively immune to market volatility.
Binance typically evaluates its listed projects on a few key criteria—such as development activity, liquidity, community engagement, and regulatory compliance. If a project falls short on these criteria, it risks being delisted after being added to the Monitoring Tag.
[Source](Binance Monitoring Tag Alert Triggers Sharp Drop in AEUR, PYR, SCRT and VANRY Tokens)
Another important aspect of this tag is that users have to complete a risk assessment quiz every 90 days and accept new terms in order to continue trading. This essentially acts as an additional layer of security to alert investors.
Previously, some tokens first received the Monitoring Tag and then faced direct delisting. As a result, the current situation is being viewed as an “early warning signal” by many.
Overall, this incident is yet another reminder that not only the popularity of a project in the crypto market, but also the exchange's policies and consistent performance play a major role in determining the future of a token.
Posted Using INLEO
