preloader icon

Recent blog

blog

Is a Digital Asset a Security or … Is It Not?

Earlier this month, and after much petal plucking, the SEC’s Division of Corporate Finance released a long-awaited – yet “unofficial” – staff guidance on the treatment of digital assets. As acknowledged by the Commission, the framework is not intended to be a comprehensive overview of the laws, but rather a mere framework offering a number of questions intended to help market participants assess whether the federal securities laws apply to the offer, sale, or resale of a particular digital asset.

The framework is neither a rule, regulation, legal advice or even a statement of the Commission itself. When you get to the meat and potatoes, it’s clear that the framework is nothing more than 13 pages of “staff views” and disclaimers that prompt more questions than it supplies answers.

According to Drew Hinkes, general counsel at Athena Blockchain, attorney at Carlton Fields, and law professor at the New York University, “for those clamoring for certainty, the framework doesn't create the “one checklist to rule them all” that so many have been clamoring for, as this appears to be nothing more than just another statement by a regulator. It’s not a rule, law, ordinance, or even guidance. It is more likely another tool for lawyers to use to analyze offerings and make legal arguments, leaving it for courts ultimately to decide whether a particular token is or isn’t a security.”

Not surprisingly, the SEC’s framework sets forth facts and circumstances to be considered in applying the Howey Test in determining whether or not a digital asset is a security. The Howey Test, which emanated out of the 1946 Supreme Court case SEC v. W.J. Howey Co., lays out a three-prong approach for judging whether or not something can be classified as a security: “an investment contract for purposes of the Securities Act means a contract, transaction or scheme whereby a person [1] invests his money in [2] a common enterprise and [3] is led to expect profits solely from the efforts of the promoter or a third party.”

The third prong of Howey is where things get particularly dicey.

In its framework, the SEC sought to elaborate on the persons included in the third prong of the Howey Test and offered a new, broader definition of a “third party” by introducing the term: “Active Participant (AP).” The definition provided for AP is so broad that it may include any entity involved in a token sale, including managers, promoters, sponsors or any other third party with the potential to impact the possible success of an enterprise.

According to Hinkes, “As Active Participant is not clearly defined, it may be argued that an Active Participant is anyone who makes representations on behalf of the issuer about the offering that buyers rely upon when making an investment decision. In addition to possible first amendment implications, this overly broad definition could become a treasure trove for securities litigators who may see a number of new potential defendants joined into litigation matters as alleged Active Participants.”

On the very same day that its framework was published, the SEC also issued a no-action decision in response to a letter from TurnKey Jet, Inc. seeking guidance for a proposed token sale. The SEC responded by declaring that TurnKey’s loyalty token program for its members was NOT a security. 

As if anyone had any doubts.

The TurnKey token is no more a security than the kale salad I just ate for lunch.

Even SEC Commissioner Hester Peirce (aka Crypto-Mom) has publicly stated that the no-action letter wasn’t the most helpful for cryptocurrency entrepreneurs as the token was “so obviously not a security.”

While there are many who view the SEC’s unofficial framework and its TurnKey no action letter as “nothing burgers,” there happened to have been some very significant regulatory movement in the U.S. during the month of April. One was the re-introduction of the Token Taxonomy Act of 2019 (HR 2144), and the other was Blockstack’s Form 1-A filing with the SEC.

All comments


Comment not found