When Your Utility Token is a Security: Why Munchee Failed

By: Gleb Zaslavsky
December 18, 2017

In July 2017, the Securities and Exchange Commission (SEC) sent shockwaves through the blockchain community with the release of the DAO report, in which it found that virtual tokens could be securities under federal law, subject to SEC registration requirements.

The report left unanswered an important question on many developers’ minds: How would the SEC’s analysis apply to utility tokens—virtual tokens that serve some function in an online platform? Following the DAO report and SEC guidelines, many experts and advisors in the field have drawn a line in the sand between a so-called security token and a utility token.

On Monday, December 11, 2017, the SEC addressed the so-called “utility” tokens in a cease-and-desist order to Munchee Inc., an iPhone developer that sought to raise funds through an initial coin offering (ICO) for a new utility token. The SEC concluded that Munchee’s token was a security and ordered it to stop offering and selling it to the public.

Blockchain startups and developers should be familiar with what Munchee did wrong, and what it could have done differently, to avoid similar problems in their own ICOs.

In short, Munchee:

  • Engaged in sale of pre-functional utility tokens that carry the high risk of being treated as securities (Munchee acknowledged that the ecosystem would not be functional until 2018/2019, yet sold the tokens in 2017);
  • Stated that the purchasers of Munchee tokens can “flip” the tokens for profit once the Munchee ecosystem was functional;
  • Stated that Munchee tokens would be traded in secondary market;
  • Discussed in great detail and advertised heavily the potential for increase in value and profits from re-sale.

Not surprisingly, all of these factors analyzed together led SEC to the conclusion that Munchee token was in fact a security.

Munchee and the MUN Token ICO

Munchee is an iPhone developer that released the Munchee app in early 2017. The app enables users to share photographs and reviews of restaurant meals in the United States.

In a white paper published in October 2017, Munchee proposed enhancing its app by turning it into a Munchee “ecosystem,” in which restaurant customers could buy meals, and restaurants could buy advertising, using virtual tokens called MUN tokens. To fund development of its enhanced app, Munchee proposed a $15 million ICO for pre-functional MUN tokens.

On October 31, 2017, Munchee began selling MUN tokens in exchange for ether or bitcoin. The next day, the SEC contacted the company, and Munchee voluntarily stopped selling the tokens. It also refunded the roughly $60,000 it had raised from 40 buyers during the ICO. The SEC’s recent cease-and-desist order resulted from an offer of settlement by Munchee to avoid penalties.

Why MUN Tokens Were Securities

The SEC’s definition of a security includes investment contracts, which it defines as (1) an investment of money (2) in a common enterprise (3) with a reasonable expectation of profits (4) to be derived from the entrepreneurial or managerial efforts of others.

In its cease-and-desist order to Munchee, the SEC focused on those last two elements: a reasonable expectation of profits derived from the efforts of others.

Reasonable Expectation of Profits

The SEC identified two characteristics of MUN tokens that satisfied the reasonable-expectation-of-profits element. First, the value of the pre-functional MUN tokens bought during the ICO would naturally increase once the Munchee “ecosystem” on which they could be used was implemented.

Second, in promoting MUN tokens in its white paper, through social-media accounts, and elsewhere online, Munchee emphasized the likelihood that the tokens would increase in value. It also promoted MUN tokens to investors in countries other than the United States, even though the Munchee app is only available in the U.S.

Derived from the Efforts of Others

Any increase in MUN tokens’ value between the ICO and the launch of the enhanced Munchee app would be the result of Munchee’s efforts. Specifically, Munchee would develop the enhanced app, increasing demand for MUN tokens and, accordingly, the tokens’ value.

In addition, Munchee had promised to support secondary markets on which MUN tokens could be sold, including by buying or selling MUN tokens to ensure a “liquid secondary market.” This, too, would tend to increase MUN tokens’ value.

What the Munchee Order Means for Developers

Since the DAO report was released in July 2017, many developers have operated under the mistaken belief that they could avoid SEC regulation simply by implementing a new virtual token as a utility token. The Munchee order makes clear that that is not the case. As such, developers should take the following lessons from Munchee’s plight:

  • Utility tokens can be securities. The label attached to a virtual token does not affect its legal classification.
  • Developers should avoid ICOs involving pre-functional tokens. The sale of a pre-functional utility token will almost always involve an expectation of profits derived from the developer’s efforts
  • Developers must consult a qualified blockchain lawyer before an ICO. Munchee planned to spend 10% of the amounts raised through its ICO on “legals to make sure Munchee is compliant in all countries.” That review should have been conducted beforehand.

 

 

Latest articles
UPDATE: New Name, Website and Logo

Dear Clients and Friends of the Firm,

We are writing to share some exciting news!

Beginning November 12, …

A Path to Secondary Trading of Your Security Token

Our joint report with Securitize and OpenFinance Network discussing checkpoints on the path to secondary trading for …

Digital Finance During WEF 2020

Earlier in January, a small picturesque village of Davos in Switzerland hosted the 50th

Tokenizing Equity: Benefits, Risks and Practical Considerations

Special thanks to Carlos Domingo from Securitize and James C. Row, CFA from Entoro Capital for their insights and …

INSIGHT: The Dual Nature of ‘Utility’ Tokens and Dual Token Structures

This article by Rika Khurdayan, Max Dilendorf and Gleb Zaslavsky was originally published by The Bureau of National …

Contact us