SEC dismisses securities violation case against Helium

CryptoBreaking
HNT0,59%
TOKEN4,08%

The U.S. Securities and Exchange Commission (SEC) has rejected a lawsuit against Helium, a blockchain-powered network for the Internet of Things (IoT). The lawsuit alleged that Helium’s native token, HNT, was a security and required registration with the SEC.

However, the SEC’s dismissal of the lawsuit is a positive outcome for Helium and the crypto community. The SEC stated that HNT does not qualify as a security under U.S. federal securities laws, citing the token’s utility and functionality within the Helium network.

This decision sets a precedent for other blockchain projects and provides clarity on the regulatory status of cryptocurrencies in the U.S. It highlights the importance of considering a token’s use case and function when determining its classification under securities laws.

Despite the dismissal of the lawsuit, regulatory uncertainty remains a challenge for the crypto industry. Projects must continue to work closely with legal experts to ensure compliance with evolving regulations and avoid potential enforcement actions in the future.

The post SEC dismisses securities violation case against Helium appeared first on Crypto Breaking News.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
GateUser-ff73150dvip
· 2025-04-11 01:22
Just go for it💪
View OriginalReply0