SOL is not a security, says the Solana Foundation

Blockchain

The Solana Foundation took to Twitter to address for the first time the U.S. Securities and Exchange Commission’s classification of its native token, Solana (SOL), as a security. 

“The Solana Foundation disagrees with the characterization of SOL as a security,” reads a statement from June 10, noting that it welcomes the engagement of policymakers to achieve legal clarity in the digital assets space.

Solana’s ​​native and utility token was publicly launched in March 2020. SOL holders stake the token in order to validate transactions through its consensus mechanism. The token can also be used to receive rewards, pay transaction fees, and enable users to participate in governance.

The SEC has labeled the SOL token as a security in two separate lawsuits filed on June 5 and June 6 against crypto exchanges Binance and Coinbase, respectively. The classification is based on several factors, including the expectation of profits derived from the efforts of others, as well as how the tokens are being used and marketed.

“This classification is significant because it subjects Solana and associated activities to a different set of regulations and compliant requirements. […] we are actively engaging with legal experts and are in communication with the SEC to understand and address their concerns,” stated the Foundation in a letter to its community.

Along with SOL, the SEC listed other nine cryptocurrencies to the securities’ classification on Binance’s lawsuit: BNB (BNB), Binance USD (BUSD), Solana, Cardano (ADA), Polygon (MATIC), Cosmos (ATOM), The Sandbox (SAND), Decentraland (MANA), Axie Infinity (AXS) and COTI (COTI). In its Coinbase suit, the SEC named 13 cryptocurrencies, doubling down on the newly classified tokens and adding six more: Chiliz (CHZ), Flow (FLOW), Internet Computer (ICP), Near (NEAR), Voyager Token (VGX) and Nexo (NEXO).

According to the SEC, the term “security” includes an “investment contract,” as well as other instruments such as stocks, bonds, and transferable shares. “A digital asset should be analyzed to determine whether it has the characteristics of any product that meets the definition of “security” under the federal securities laws,” the regulator states in its guidance for analyzing digital assets as investment contracts.

The Solana Foundation did private sales of tokens in the past years, which means that it sold securities for institutional investors and venture firms. Its private sales were reportedly performed under a simple agreement for future tokens (SAFT), which is a security issuance for the eventual transfer of digital tokens from crypto developers to investors. Under token sales through a SAFT, Solana also filed private offering forms with the SEC, and investors were subject to lockups.

A public sale of SOL tokens was held during Solana’s initial coin offering (ICO) in March 2020, allocating 8 million tokens to the public, or 1.6% of its initial token supply. This sale of tokens raised $1.76 million for the Solana Foundation, at $0.22 each.

In an opinion piece about the recent developments, legal expert and Bloomberg’s contributor Matt Levine noted that previous securities offers of SOL should not make the token a security now. “The fact that those tokens now trade publicly, with less disclosure and fewer investor safeguards than the SEC would like, is, from the SEC’s perspective, unfortunate. But it’s not exactly Solana’s fault, or rather it is Solana’s fault but in a perfectly legal way,” he stated.

Magazine: Crypto regulation — Does SEC Chair Gary Gensler have the final say?

Articles You May Like

Coca-Cola CEO says McDonald’s E. coli outbreak won’t hurt beverage company’s sales
Industrial AI play Dover falls on a noisy quarter. Here’s why we’d buy the dip
US reportedly have been declining to change language when discussing Taiwan independence
Israel strikes on Iran don’t look designed to minimize the chance of retaliation
Euro Gains as Inflation Data Strengthens Hawkish Case for ECB

Leave a Reply

Your email address will not be published. Required fields are marked *