What a Workable US Crypto Framework Would Actually Need

Opinion, upfront: most of the public debate about US crypto regulation argues about outcomes — who wins, who loses, which agency should hold the pen — before anyone agrees on what a workable framework actually has to accomplish. That is backwards. Before litigating who should write the rules, it is worth being honest about the design constraints any serious framework has to satisfy, and about the trade-offs attached to each one.

Custody: who is actually holding the asset, and under what rule

Any framework has to answer a basic question before it answers anything else: when a customer’s crypto sits with a third party, what obligations does that party have to keep it segregated, operationally sound, and recoverable if the firm fails? Traditional finance answers this with custody rules built for securities and cash, and crypto does not map onto those rules cleanly, because a private key is not a share certificate and a hack is not the same failure mode as embezzlement. A workable framework needs its own custody standard, one that treats assets held on a customer’s behalf differently from a firm’s own balance sheet, and that gives customers a real, tested claim on their holdings in a bankruptcy rather than an unsecured one discovered too late. Readers new to the underlying distinction can start with our explainer on custodial versus self-custody wallets. In practice, state-level licensing regimes such as New York’s BitLicense currently do a share of this work already, unevenly, one state at a time, which is itself a symptom of the federal gap.

Disclosure: telling people what they actually hold

Securities law’s core insight, going back nearly a century, is that markets work better when the people selling an investment are forced to disclose what it is, how it generates a return, and what could go wrong. Crypto has resisted clean disclosure for structural reasons: a token can function as a security in one context and as network access in another, a project’s economics can change after launch through a governance vote most outside holders never track, and reserve backing for products like stablecoins is really an accounting and audit question wearing a crypto costume. A workable framework needs disclosure requirements calibrated to what is actually being sold, not disclosure copied wholesale from a decades-old equity prospectus and forced onto a product it does not describe well. Our guide to proposed US stablecoin frameworks is a useful test case, since reserve disclosure is close to a solved problem in traditional finance and still genuinely contested in crypto.

Jurisdiction: the seam between securities and commodities regulators

This is the fight that eats the most oxygen, and for good reason. Securities regulators have authority over securities, commodities regulators have authority over commodities and much of the derivatives market, and a meaningful share of digital assets do not sit clearly on either side of that line. Our explainer on which agency regulates which crypto assets lays out the current, contested state of play. A workable framework needs an explicit jurisdictional line, ideally drawn by Congress rather than inferred after the fact from settlements, that tells a project which rulebook applies before it launches, not after an enforcement letter arrives.

Consumer protection: easy to promise, hard to specify

Every framework proposal claims to protect consumers. Few specify what that means in practice for a market that trades continuously, globally, and often through offshore venues a US rule cannot reach directly. Real consumer protection here probably means at least three concrete things: enforceable custody and segregation rules of the kind described above, disclosure a non-specialist can actually parse, and some functioning version of anti-money-laundering compliance that does not simply push bad actors toward the least-regulated venue available. It does not mean pretending a framework can eliminate volatility, or that clear rules turn a bad investment into a good one. A framework that protects consumers from unclear custody and dishonest disclosure is doing real work. One that implies it can protect consumers from crypto’s price swings is overselling itself.

The trade-offs nobody gets for free

Every one of these design choices has a cost attached, and pretending otherwise is how bad policy gets sold. Tighter custody and disclosure rules raise compliance costs, which smaller and more experimental projects feel more acutely than well-capitalized incumbents; taken too far, that entrenches the largest players rather than protecting consumers. A federal jurisdictional line that preempts the state licensing patchwork would simplify compliance, but it would also override state regulators who, in specific cases, have moved faster and with more specific expertise than federal agencies have managed. Speed and deliberation trade off directly: a framework built quickly risks getting technical details wrong in ways that take years to unwind, while a framework built slowly leaves the current uncertainty in place for that much longer. There is no version of this that avoids every cost. There is only a choice about which costs a framework is willing to accept, and it is worth being suspicious of any proposal that claims otherwise.

Why a partial framework creates its own risk

It is tempting to treat these four constraints as a menu, where addressing any one of them counts as progress. In practice, a framework that only draws a jurisdictional line, without a matching custody standard, tells a firm which regulator to talk to but not what that regulator will actually require, which is only half the certainty a business needs to launch responsibly. A framework that mandates disclosure without addressing custody protects an investor’s ability to understand a product on paper while leaving the underlying asset exposed to the operational failure that disclosure was never designed to catch. These four pieces reinforce each other, and treating one as a stand-in for the whole package is how a framework ends up technically passed and practically incomplete. That is worth watching for in any legislative proposal that leads with the constraint easiest to explain in a headline, usually jurisdiction, while leaving the harder, more technical pieces, custody chief among them, for a later phase that may or may not arrive.

What this means for readers, not lawmakers

None of this is a prediction about what Congress or any agency will actually do. It is a checklist for what a framework would have to get right to be worth calling workable: a real custody standard, disclosure matched to the product being sold, a jurisdictional line drawn before launch rather than after a lawsuit, and consumer protection defined narrowly enough to be honest about its own limits. Readers evaluating any specific proposal, from either party or either agency, can use that checklist as a filter. If a proposal is silent on one of these four, that silence is itself the news.

This column is opinion, not investment, legal, or tax advice. It is not a forecast or a guarantee of any outcome. Crypto is volatile and high-risk; consult a licensed professional before making financial decisions.