Lawbitragetag:typepad.com,2003:weblog-925429810017461882017-10-02T07:53:43-04:00Law and Finance by Houman Shadab TypePadAnything that Can be Digitized: The SAFT Approach for Utility Tokenstag:typepad.com,2003:post-6a01053611984e970b01bb09c6c4e9970d2017-10-02T07:53:43-04:002017-10-02T14:47:20-04:00The SAFT Project is a positive development that could very well help to empower the next revolution in business that consists of digitally-native goods, services, and property -- and their supporting token-based, distributed software networks. The SAFT structure creates a two-step process. A legally compliant, private investment is first made...Houman Shadab

The SAFT Project is a positive development that could very well help to empower the next revolution in business that consists of digitally-native goods, services, and property -- and their supporting token-based, distributed software networks.

The SAFT structure creates a two-step process. A legally compliant, private investment is first made by sophisticated investors prior to the tokens having any functionality. Later, utility-tokens are sold to the public once they enable purchasers to use the underlying software network for any number of purposes including transaction processing, identity management, and secure messaging.

A key benefit of the SAFT is separating the potentially high-risk investment aspects of tokens from their non-financial, software-based functionality. This is achieved by permitting only legally qualified, accredited investors to purchase tokens when doing so is a bona fide investment. When the tokens' underlying software has yet to be developed, the tokens have no immediate use value and their sale would most likely qualify as a regulated securities transaction.

But when tokens provide actual functionality, their sale to the public is usually best viewed as an act of software-related commerce and not a financial activity (that would be subject to securities regulation). To be sure, because anything that can be digitized can be made highly tradable, it is no longer possible to completely separate investment and commerce. In a commoditized digital world, anything that can be consumed can also be used for purely speculative purposes. But the law already takes this into account. As the SAFT whitepaper notes, speculative motives are not sufficient to move a transaction from the realm of commerce into investment. This is especially the case when the secondary market price is driven primarily by broad-based market forces.

Although the SAFT structure leaves open several legal and policy questions, it is a worthwhile approach to bringing much-needed legal and technical standards to token sales of the type that myself and colleagues at the Accord Project are developing. The SAFT not only strikes a reasonable balance between innovation and investor protection, but it also takes into account the realities of a brave new digital marketplace.

Speaking Engagements - First Half 2016tag:typepad.com,2003:post-6a01053611984e970b01b7c8072194970b2016-01-19T00:15:52-05:002016-01-21T11:56:58-05:00The following are my speaking engagements for the first half of 2016 on various aspects of fintech, smart contracts, blockchains, and Bitcoin: Jan. 10: American Association of Law Schools 110th Annual Meeting: Section on Economic Globalization and Governance, The Future of Global Finance: A Roundtable, New York City. Jan. 22:...Houman Shadab

The following are my speaking engagements for the first half of 2016 on various aspects of fintech, smart contracts, blockchains, and Bitcoin:

Please let me know if you are going to be at any of the events or would like to discuss further.

In itBit We Trusttag:typepad.com,2003:post-6a01053611984e970b01bb082ba198970d2015-05-11T14:59:12-04:002015-05-13T13:32:28-04:00Since their inception, Bitcoin exchanges have operated under a fog of legal uncertainty. Last week, just one day after the New York-based exchange itBit announced obtaining a banking law charter giving it the ability to operate in all 50 states, a California official called that into question. Almost every state...Houman Shadab

Since their inception, Bitcoin exchanges have operated under a fog of legal uncertainty. Last week, just one day after the New York-based exchange itBit announced obtaining a banking law charter giving it the ability to operate in all 50 states, a California official called that into question.

Almost every state has its own licensing requirements for traditional money transmitters that include payment processors and money transfer firms like Western Union. The safe but costly route for Bitcoin exchanges would be to obtain a license in each state that requires it for digital currency firms. But it's unclear which do.

Texas, for example, stated that transmitting digital currencies like bitcoin doesn't require a license in its state. Other states, like New York and California, are still in the midst of passing digital currency-specific licensing requirements, making it a question of what Bitcoin exchanges should do until those licensing laws are finalized. The prominent and reputable Bitcoin exchange Coinbase, for example, was operating in New York and California without a license in either state—and probably didn't need one.

itBit was able to bypass much of the uncertainty about being required to obtain state money transmitter licenses. It accomplished this by obtaining a trust charter under New York banking law, which is generally required of exchanges in the state.

Under New York law, a trust company is a type of banking organization that is technically distinct from a bank. A trust company has all of the powers of a bank to take deposits and make loans, and also certain fiduciary powers such as acting as an agent for governmental bodies. Firms organized as trust companines in New York include the derivatives clearinghouse Ice Trust, the wealth and asset manager Northern Trust, and the FDIC-insured bank Stuben Trust.

itBit, in particular, is authorized as a limited purpose trust company. This means it is not allowed to make loans or take deposits. To obtain the charter, itBit had to meet the very strict requirements of ordinary New York chartered commercial banks and subject itself to ongoing oversight. However, itBit is not required to obtain insurance from the Federal Deposit Insurance Corporation (FDIC), and it is subject to a much lower level of minimum capital--$2 million versus at least $50 million for a commercial bank.

Despite being organized under New York's banking law, itBit is not a bank in the ordinary sense and it not regulated by any federal banking authority such as the Federal Reserve or the FDIC. Being regulated as a bank would be too expensive and require a level of regulation and oversight ill-suited for a digital currency exchange.

itBit does, however, indirectly provide FDIC insurance to its clients' dollars by holding them at a separate FDIC-insured bank. itBit might be subject to some degree of FDIC oversight or compliance obligations indirectly, but that depends on how closely itBit and its banking partner work together. Bitcoin firms Coinbase and Circle similarly provide FDIC insurance to their customers' dollar accounts.

With a trust charter under New York banking law, itBit is basically in the clear when it comes to needing a state license to operate as a money transmitter.

Under New York's traditional money transmitter statute and its pending Bitlicense, a company chartered under its banking law does not need a license. Nationally, states generally don't require a firm chartered under another state's banking laws to get a money transmitter license.

For example, moving across the Hudson River, New Jersey excludes any federal or state chartered bank from being required to get a money transmitter license in its state, and defines a bank to include a trust company like itBit. Moving westward, things get easier: Illinois is explicit about excluding trust companies chartered in any state from needing a money transmitter license.

But it's when we get out to California that things get a little gnarly.

California does not require a money transmitter license for trust companies authorized under California law. But unlike New Jersey or Illinois, that statutory exemption does not explicitly apply to out-of-state trusts. It's therefore not a surprise that a California official would question whether itBit's New York trust charter is enough for it to do business with California clients.

Nonetheless, itBit seems to be on solid ground to operate in the Golden State. California recognizes that out-of-state trusts may conduct business within its borders. It also recognizes that out-of-state banks, which include trusts, don't need an office to operate in the state. As an electronic exchange, it's unlikely that itBit will be opening an office in California, or any other state, in the near future. Likewise, the laws that permit commercial banks to open branches in other states through interstate reciprocity don't fit the operational model of itBit.

An out-of-state trust authorized to do business in California thus likely qualifies for the money transmitter exemption that applies to trust companies generally. Indeed, there seems to be no precedent or policy reasons for requiring a regulated banking trust like itBit to obtain a money transmitter license. But it would be good to have greater certainty about the issue. Washington State seems to have a similar snag. And Louisiana, at least by statute, requires an out-of-state bank to be a "federally insured depository" institution to qualify for a licensing exemption. It's not clear whether itBit fits that description.

itBit's road to obtaining a trust charter under New York banking law was long and costly. It also proved to be savvy. In one fell swoop, it gave the firm a basis to operate nationally while building confidence in the Bitcoin ecosystem. So it's no surprise that upon announcing its trust charter that itBit also disclosed a $25 million round of financing. By doing so, itBit demonstrated the fundraising benefits of being a regulated firm and that financial institutions are not always on the hunt for minimal regulation.

There seems to be some uncertainty about whether itBit—a banking law trust—automatically qualifies to do business without a money transmitter license in certain states. But that uncertainty should, more than anything else, lead law makers to rethink the patchwork quilt of U.S. state money transmitter laws. As of now, it potentially undermines the operations of global digital currency exchanges.

Empowering Distributed Autonomous Companiestag:typepad.com,2003:post-6a01053611984e970b01b7c7514551970b2015-02-21T09:49:27-05:002015-03-01T10:17:41-05:00It is difficult to overstate the growing importance of software to companies, whether it be in the form of automated trading, web-based applications and data storage, or monitoring systems to comply with regulation. But software may soon also be changing the very nature of business enterprises by giving rise to...Houman Shadab

It is difficult to overstate the growing importance of software to companies, whether it be in the form of automated trading, web-based applications and data storage, or monitoring systems to comply with regulation. But software may soon also be changing the very nature of business enterprises by giving rise to digital companies that operate autonomously.

Digital firms taking the form of distributed autonomous companies (DACs) would likely be built using the type of blockchain technology underlying Bitcoin. The benefit of using a distributed blockchain ledger is that a DAC’s identity and activities can be publicly verified and carried out without a central authority or point of failure. The scope for abuse or incompetence could also be reduced because its operational rules would be secure and require consensus to be altered.

A DAC could own assets but would not need employees. Like modern day investment trusts, a DAC could enter into contracts with managers and others as needed to generate profits. A DAC’s automated decision making could also be programmed to operate by distributed consensus, meaning that some of its activities would require the verification or feedback of a network before being undertaken. For example, a DAC that manufactures goods may contract with a supplier but only after the blockchain network verified that the supplier meets certain production quality standards. With advances in artificial intelligence, a DAC might be able to operate mostly autonomously, but would probably still require human involvement at the edges.

But innovation does not do well amidst legal uncertainty. So in order for DACs to become operational and reach their full potential, the law must give them a stamp of approval. I argue that a framework similar to the law of limited liability companies would be the best fit.

The Need for Organizational Law

Organizational law is a set of background rules that governs companies' internal structure. In the United States, it is found in state statutes governing corporations and other types of companies. Organizational law serves several important functions, including:

providing external recognition that a company is an independent legal entity owned by shareholders (personhood);

making enforceable a company’s ability to own assets, enter into contracts, and generate profits and losses;

For these reasons, corporate statutes have long been described as enabling companies to form and operate according to the design of their founders. Delaware's corporate code is the preeminent source of organizational law for public corporations, largely because its case law is sophisticated and widely understood.

For DACs, organizational law would provide foundational rules to govern companies. To "incorporate," a DAC could a transmit a message to a blockchain recording its existence. Each DAC, in turn, would have a more specific set of rules embedded in its own code. These rules would govern its operations and the rights of its owners, and thereby serve the role traditionally served company operating agreements, certificates of incorporation, and bylaws. Organizational law is particularly suited for software code-based entities like DACs that would need to rely on a foundational set of parameters and specifications to permit its more specific operations to take place. The code-based system of organizational bylaws developed by Eris is an example of an operational framework for digital organizations.

As with traditional companies, a state legislature must enact a statute recognizing DACs to make certain that the company’s existence will be recognized and its rights will be enforceable in court. State legislatures recognizing new types of business entities is not uncommon. For example, as of February 2015, 27 states had enacted legislation recognizing benefit corporations, which are a new type of socially-minded for-profit company.

Instead of states adopting DAC statutes, or until they do, it may be sufficient to enact legislation simply recognizing that DACs are a legitimate form of business entitled to rights similar to other companies. For example, the following provisions from a Digital Company Enabling Act could serve as a first step in enabling a DAC to be recognized as a legal person under Delaware law:

SECTION 1. TITLE.

This Act may be cited as the Digital Company Enabling Act.

SECTION 2. PERSONHOOD, RIGHTS, AND POWERS.

A digital company has legal personhood and rights and powers to the full extent provided to limited liability companies under the Delaware Limited Liability Company Act.

SECTION 3. FORMATION.

In order to form a digital company, one or more persons must create, record, or transmit unique and publicly verifiable data that indicates formation of the company.

SECTION 4. DEFINITIONS.

...

“Digital company” means any company that operates primarily on the basis of software code.

While plenty of questions should remain even after the passage of this type of statute, a little bit of law could go a long way.

DACs Should be Structured as Limited Liability Companies, Not Corporations

Like other business entities, the characteristics of a DAC can borrow from the two fundamentally different types of companies: partnerships and corporations. In their purest sense, partnerships are decentralized companies whose owners manage the business and are personally liable for the firm's debts. Partnerships are indistinguishable from their owners, and if a partner goes so does the partnership. At the other extreme are corporations. In a corporation, owners and managers are distinct, and management must be centralized in a board of directors subject to election by shareholders. Corporate shareholders are fundamentally passive and enjoy limited liability.

Although a DAC could take a variety of forms, the law of limited liability companies (LLCs) is best suited for DACs due to its simplicity and flexibility.

LLC statutes first emerged in the late 1970s to allow companies to enjoy the benefits of both partnerships and corporations. LLCs are not taxed on their profits, maintain limited liability for owners, and can adopt decentralized management without a board. But it wasn’t until more recently that LLCs began to take off. By 2007, LLCs were being formed at a faster rate than corporations and being used in a wide range of industries. Large companies have also adopted the LLC form, including Sony Computer Entertainment America, maker of the PlayStation home entertainment console.

A company is often understood to be a "nexus of contracts," and this description fits the LLC better than any other type of business organization. For example, the Delaware LLC Act "give[s] the maximum effect to the principle of freedom of contract and to the enforceability" of LLC agreements. This means that LLC law can accommodate a wide variety of specific business structures and use cases.

Corporate law, by contrast, is more rigid. In a corporation, mergers and changes to the articles of incorporation must be approved by directors and shareholders. In an LLC, these activities can be undertaken by one person or however is specified in the operating agreement.

Corporations also require at least one class of stockholders to have voting rights. Although a corporation can be structured like Google and Facebook with dual class shares that give founders disproportionate voting power, LLCs are not even required to have voting shares.

LLC law also allows managers to eliminate any extra-contractual fiduciary duties owed to shareholders. This allows LLC managers to be free from the nebulous body of law defining when fiduciary duties are violated. But under corporate law, fiduciary duties are sacred and cannot be eliminated.

Profit-Seeking Software: Series LLCs

A simple LLC structure may not be enough to enable DACs to be fully realized, however.

Blockchain organizational law should go further and also enable DACs to operate similar to what are known as series LLCs, which were first recognized under Delaware law in 1996.

The defining characteristic of a series LLC is that it permits a company to form internal companies each having a distinct purpose, owners, managers, and assets. The assets of each internal company can be transferred among each other while still preserving an internal liability shield that protects each company from the creditors of the others.

The general benefit of series LLCs is that they can create distinct businesses without being required to establish a new company from scratch. This likely reduces operational costs and taxes. More importantly, however, is that it enables a company to adopt a wide variety of governance structures and profit-sharing arrangements. For example:

series can be created to seek profits from particular activities and expand, dissolve, or multiply as profits are generated;

assets can be transferred among series based on their profitability or other criteria;

the ability of stakeholders to control, interact with, or share in the profits of different series can change depending on the success of particular series.

Individuals or entities (including other DACs) may interact with a DAC by buying in, contributing work, or being granted shares, as noted by William Mougayar.

The series LLC structure is particularly suited for a digital company created from software. Software code is typically written in a way that relies heavily on establishing hierarchies, defining entities by type, making decisions based on algorithms, and having the results of computations feed back into the system. These fundamental aspects of software architecture fit well into the series LLC legal structure. Series LLCs permit the ongoing creation and rearrangement of assets and distinct companies under the umbrella of a master company.

The following figure is a high-level illustration of the structural similarity between a series LLCs and building blocks of the widely-used approach to software languages known as objected oriented programming.

Under an object oriented approach, the master umbrella LLC can serve the place of the top-level class while each series is a company containing an operational software bundle (an object). Contracts between the master company, among series, or with a manager or other service provider are easily understood in terms of software functions. Numerous other aspects of object oriented programs, from “inheritance” that allows objects to be derived from one another to “encapsulation” that segregates data among objects, also fit easily into the structure and operations of a series LLC.

A series LLC is also conducive to autonomous decision making involving the creation of new companies (a new series) because doing so does not require a new master LLC to be formed. The automatic creation of new companies for certain tasks, or to hold specific assets or data, would likely be a key benefit of DACs.

Entrepreneurs and developers are creating the infrastructure required to make DACs a transformative force. But to make that happen, the law needs to empower them.