In bull and bear cycles alike, cryptocurrencies have commanded the attention of markets and policymakers. The 117th Congress has introduced dozens of bills addressing the crypto ecosystem.1 In addition, multiple regulators have been outspoken about their readiness to be the “cop on the beat” when it comes to overseeing crypto markets.2 Nonetheless, key questions remain about how best to regulate the crypto ecosystem and the extent to which current laws and regulations apply. This briefing paper proposes a cryptocurrency regulatory framework with the goals of dispelling uncertainty, unencumbering entrepreneurship, and providing practical consumer protections.3 The framework recognizes the unique risks and benefits of cryptocurrencies, proposing a clear‐​cut test for whether crypto projects trigger securities laws and a common‐​sense registration and disclosure option for those that do.

Legislating Rational Securities Treatment

A top priority for any crypto regulatory framework is determining whether and to what extent cryptocurrencies are or ought to be subject to U.S. securities laws. At a high level, the federal securities regime seeks to ensure that public representations regarding potential investment opportunities are accurate.4 Where crypto entrepreneurs sell tokens to the public to finance the development of their projects, it is reasonable to ask whether, when, and how securities laws apply. While various federal bills touching the question have been introduced, and the Securities and Exchange Commission (SEC) has engaged with the issue in enforcement actions and informal guidance, to date no law or formal rule has decisively clarified the application of securities laws to cryptocurrencies.5

A jurisdiction that leaves the applicability of laws uncertain or prioritizes legacy regulatory formalities regardless of their practical relevance to cryptocurrencies risks becoming inhospitable to both crypto entrepreneurs and users to the detriment of technological innovation, capital formation, and consumer welfare.6 Accordingly, any applicable securities rules should be tailored to the specific risks of cryptocurrencies: fraud, deception, and manipulation by developers, sellers, and promoters who remain actively involved in the management of crypto projects.

Background on Securities Classification

Determining whether a crypto project presents risks akin to those of traditional securities goes hand in hand with the question of whether the project’s activities meet the legal standard for a security offer.7 The Securities Act of 1933 defines “security” to include an “investment contract.”8 Under the Supreme Court’s canonical test articulated in SEC v. W. J. Howey Co., “an investment contract for purposes of the Securities Act means a contract, transaction or scheme whereby a person [1] invests his money in a [2] common enterprise and [3] is led to expect profits [4] solely from the efforts of the promoter or a third party.”9

The Howey test’s fourth prong—whether a purchaser is relying on the efforts of a third party—is critical to determining whether a crypto project presents the risks that securities laws were designed to mitigate. Securities laws evolved in no small part to address the risks posed to investors by a managerial body’s ability to possess information that investors do not and its capacity to act at odds with investors’ best interests.10 In the era of the Securities Act and the Howey decision, and for decades thereafter, the archetypical covered entity under securities laws was a centralized enterprise with a corporate form, headquarters, and managerial hierarchy. Crypto projects aspire to upend this model, eschewing not only the physical plant of 20th‐​century enterprises but also, more importantly, managerial bodies exercising ongoing control over projects.

Where a crypto project involves the expectation of third‐​party managerial efforts (i.e., where it is centralized), and the other Howey test elements are satisfied, applying securities safeguards is appropriate to mitigate associated risks. But where a project does not involve this expectation and the associated risks (i.e., where it is decentralized), applying legacy securities laws is both legally inappropriate and practically ineffective for addressing potential harm.

A Clear Test for Decentralization

Policymakers should provide a clear test for whether a crypto project is decentralized.11 The key decentralization question in light of Howey and its progeny is whether the cryptocurrency purchaser is led to expect profits “solely” from the efforts of others, or in other words, whether the purchaser is relying on others’ essential managerial or entrepreneurial efforts.12 The decentralization test therefore should ask if at the time of a token sale managerial efforts are required to make the cryptocurrency project achieve minimum viable functionality, including with respect to both the token’s underlying technology and the broader project’s promoted utility. More formally, the question is whether when selling a cryptocurrency, the seller, promoter, or developer explicitly or implicitly promises performance necessary to bring the project and its benefits to fruition.13 If yes, the cryptocurrency project is centralized. If not, it is decentralized for the purposes of securities laws.14

Congress should clarify that securities laws do not apply to decentralized cryptocurrency projects. For example, Congress could amend 15 U.S.C. § 77b and 15 U.S.C. § 78c by providing new subdivisions (a)(20) and (a)(81), respectively, that read:

The term “investment contract” shall not include a contract, transaction, or scheme involving the sale of an intangible asset wherein –

(A) the seller or promoter of the intangible asset, or an agent of the seller or promoter, does not at the time of the instant, primary market sale of the intangible asset explicitly or implicitly promise performance without which –

(i) the intangible asset would not exist; or
(ii) the promised benefits of the intangible asset would not materialize; and

(B) the intangible asset does not convey a financial right or interest in the seller, promoter, or a corporate entity.

Establishing Tailored Disclosures for Emerging Decentralized Cryptocurrency Projects

Cryptocurrency projects can take time to achieve decentralization. Some projects may seek to sell their cryptocurrencies to finance their development, including via so‐​called initial coin offerings (ICOs) or token presales. In the words of SEC Commissioner Hester Peirce, applying securities laws to cryptocurrencies at this stage “create[s] a regulatory Catch 22.”15 In short, a nascent cryptocurrency may be insufficiently decentralized to avoid securities laws, which in turn create compliance costs that foreclose an important means of financing the cryptocurrency’s development and thereby achieving decentralization.16 A targeted registration and disclosure option for crypto projects in the process of decentralizing could avert this outcome and provide more relevant information to purchasers.

A crypto project is naturally centralized during an ICO, which inherently involves a promise of future development efforts and, in many cases, future token delivery. Promised future development efforts may include building software and promoting its adoption by validators, users, or other network participants who would accept the token in exchange for goods or services. The key question is not which efforts are underway but rather whether the sale of the token involved an explicit or implicit promise to undertake efforts without which the project’s benefits would not manifest. Notably, it is possible for a crypto project’s token infrastructure to be decentralized while the broader project still involves centralization, such as where developers promise to sign up participating merchants. For that reason, the decentralization test considers not only promises regarding the functionality of the technology but also the benefits of the project as a whole. Where there are such promises during a primary market sale, this proposal would require tailored disclosures by the relevant seller for each tranche of centralized tokens sold. Token sales that do not involve a promise of performance at the time of a primary market sale would be exempt from the definition of an investment contract and not require such disclosures.

While facilitating the development of decentralized crypto projects, this framework also seeks to protect against end runs around applicable securities laws by projects that are not on the road to decentralization. On the front end, the framework restricts eligibility to projects that intend to create bona fide cryptographically secure distributed ledgers. First, registration under this proposal is limited to projects that do not entitle token recipients to any financial rights—such as to equity, debt, interest, profits, or dividends—in the seller, promoter, developer, or any other business. Second, the registration is confined to projects that promise to develop an open‐​source, permissionless, publicly readable, and cryptographically secure distributed ledger capable of validating stores or transfers of tokens without intermediaries. Each of these attributes is a key element of decentralized operations that render the application of securities laws designed for centralized firms inappropriate. For example, open‐​source software avoids creating a walled garden controlled by initial developers through proprietary intellectual property rights and helps to ensure that a crypto project ultimately can be maintained through consensus adoption of software updates by distributed users.17 Similarly, being permissionless means network participation is conditioned only on users deploying the project’s software, not an initial team rewarding insiders.

On the back end, the framework addresses the risk of a person or group maintaining ongoing control over the project beyond disclosed development efforts. First, the registrant will remain subject to the provisions of the Securities Act that create liability for fraud, untrue statements, and material omissions. Ongoing project management beyond disclosed development efforts, including those that deviate from the maturation course for an open‐​source, publicly readable, disintermediated, permissionless, and cryptographically secure distributed ledger, would be vulnerable to legal actions for fraud or material omissions or misstatements. In addition, where the seller, promoter, or developer makes subsequent promises regarding the project to users or prospective users who did not participate in a registered token sale or to participants in registered sales after the execution of their purchases, the cryptocurrency project would lose eligibility for the tailored disclosure framework. The reasons for revoking the project’s eligibility are that subsequent promises present risks not bargained for in the initial investment contract, cannot be mitigated by disclosures at the time of the sale, and violate the principles of decentralization for which a crypto project is afforded a tailored registration option.

For decentralizing crypto projects, Congress should legislate a tailored registration model prioritizing disclosures related to the specific risks of cryptocurrencies and providing protections against fraud and misleading statements. For example, Congress could amend 15 U.S.C. § 77c by adding a new section (a)(15) to exempt the following projects from the Securities Act, subject to the corresponding conditions:18

Any investment contract implicitly or explicitly promising the development of an open‐​source and permissionless blockchain or other cryptographically secure distributed ledger capable of recording, according to a consensus protocol, stores or transfers of intangible assets validated without an intermediary in a transaction history that is perpetually open to public retrieval, provided that –

(A) the investment contract includes a promise to deliver the intangible asset to the purchaser;

(B) neither the investment contract nor the intangible asset promises or conveys any financial right or interest in the seller, issuer, promoter, or any corporate entity;

(C) the investment contract is registered according to the requirements of, and its sellers, issuers, and promoters, as applicable, make the specialized disclosures pursuant to section 77g(e) of this title;

(D) the investment contract and its sellers, issuers, and promoters are not exempt from the requirements of and remain subject to sections 77g(e), 77l(a)(2), and 77q of this title; and

(E) the sellers, issuers, and promoters of the investment contract do not make any additional explicit or implicit promises of performance in connection with the investment contract or intangible asset to investment contract counterparties after the execution of their investment contracts or prospective investment contract counterparties outside of a sale registered in accordance with section 77g(e) of this title.

The exemption would require compliance with a tailored registration framework, which Congress could outline by amending 15 U.S.C. § 77g to add a new subsection (e):19

(e) Registration statement for intangible asset investment contracts

A registration statement filed pursuant to the exception provided under section 77c(a)(15) of this title shall be exempt from the requirements of section 77f of this title, be filed with the Commission in electronic format, be made available on a publicly accessible website on an ongoing basis, and contain –

(1) the names of the seller, promoter, and development team members;

(2) the professional, technical, and other relevant qualifications and experience of the development team members;

(3) the amounts of intangible assets of the issuer held by the seller, promoter, development team members, and any other recipients prior to the first public sale for which a registration is filed, and the amounts of intangible assets to which such persons have a right or have indicated an intention to hold; the foregoing amounts’ percentages of the total supply of the intangible assets in existence at the time of the registration, total supply of tokens scheduled to exist following the public sale for which the registration is filed, if knowable, and total supply of the intangible asset that ultimately will come into existence, if knowable;

(4) any rights, privileges, or restrictions specific to the intangible assets distributed prior to the first public sale for which a registration is filed, such as options or lock‐​up periods;

(5) a commitment to report on an ongoing basis whenever any holder of the intangible asset, or right to the intangible asset, received prior to the first public sale for which a registration is filed sells, exchanges, burns, or otherwise disposes of 10 percent or more of his or her held amount or right thereto, provided that staking of the intangible asset shall not be considered a sale, exchange, burn, or disposal thereof for purposes of this disclosure obligation;

(6) all pertinent technical documents, including archival copies of and uniform resource locators for all white papers, yellow papers, and other files produced by the seller, promoter, or development team describing the intangible asset, the intangible asset’s supporting infrastructure, and the general character of the project related to the intangible asset;

(7) all pertinent marketing materials, including archival copies of and uniform resource locators for public statements, relating to the intangible asset and its corresponding project produced by the seller, promoter, or development team;

(8) a uniform resource locator for the public repository containing the program code for the intangible asset and its corresponding infrastructure on an ongoing basis for the duration of the public sale for which the registration is filed, as well as an archival copy of the code at the time of registration;

(9) a commitment to report on an ongoing basis for the duration of the public sale for which the registration is filed all material changes to the program code committed by the development team and provide a description of the resulting functional changes;

(10) a tool allowing for a real‐​time search of the intangible asset’s transaction history recorded in its applicable blockchain or other cryptographically secure distributed ledger, and instructions for operating the tool;

(11) a statement of the intangible asset’s general character, intended design, and how the development team will produce an open‐​source and permissionless blockchain or other cryptographically secure distributed ledger capable of recording, according to a consensus protocol, stores or transfers of intangible assets validated without an intermediary in a transaction history that is perpetually open to public retrieval, which shall include descriptions of the intangible asset’s estimated development timeline and the purpose of the public sale for which the registration is filed, the planned supply of the intangible asset or determinants thereof, the protocols for recording and validating transactions on the intangible asset’s blockchain or other cryptographically secure distributed ledger and the applicable consensus mechanism, and the governance mechanism for updating the program code for the intangible asset;

(12) a description of any promised benefits of the intangible asset; and

(13) a description of the risks of holding the intangible asset, including any cybersecurity or functional vulnerabilities or risks of loss of value reasonably foreseeable by or known to the seller, promoter, or development team, as well as a statement of these risks that is no more than 280 characters in length; and a commitment to affirmatively provide the foregoing risk statement, in addition to access to the public website containing the foregoing disclosures, to all public purchasers of the intangible asset in the course of a public sale prior to its execution.

Conclusion

The core innovation of decentralized cryptocurrencies is their capacity to mitigate risks through technology. To incentivize the development of cryptocurrencies that realize this potential and to provide consumer protections focused on addressing actual risks, not preserving a regulatory status quo, Congress should amend securities laws to provide a simple test for decentralization and a streamlined token registration pathway for projects on the road to decentralization.