The Coat Check Problem in the CLARITY Act
Why “control, entitlement, and property” must be explained like a ticket and a coat before any capability-based classification can work
Introduction: The Receipt Is Not the Thing
The CLARITY Act promises clarity, yet the first point of failure is not technical and not even legal. It is a basic human error that markets have learned to exploit: mistaking the receipt for the thing itself. A receipt feels like ownership because it is designed to; it is tidy, legible, reassuring, and it sits in the customer’s hand. But the receipt is only evidence of a relationship. When conditions are calm, that relationship behaves like ownership. When conditions are stressed, it becomes whatever the paperwork, the operational discretion, and the insolvency rules say it is.
That is why the triad matters, and why it must be introduced in ordinary language before anyone is dragged into capability tests or statutory definitions. The triad—Control, Entitlement, Property—forces the reader to separate three questions that are routinely collapsed into one flattering word: “balance”. The first question is control: who holds the asset in a practical sense, who has the power to move it, freeze it, lend it, delay it, or refuse to release it. The second question is entitlement: what the customer is actually entitled to demand, on what conditions, with what delays, subject to what compliance flags, and under what reserved discretions. The third question is property: whether the customer’s claim is merely against the intermediary as a debtor, or whether it is a right in the asset itself that survives failure, outranks general creditors, and can be asserted against the world.
A coat check makes the distinction unavoidable. The customer hands over a coat. The attendant takes it behind a counter and places it among other coats. The customer receives a numbered ticket. In that simple exchange, the three elements separate cleanly. The attendant has control, because the attendant has physical custody and decides when the coat is returned. The customer has an entitlement, because the ticket represents a right to demand return, but only through the attendant’s process. The customer’s property right is the decisive point: does the coat remain the customer’s property, held for safekeeping, or has it been transformed—by practice, by terms, or by law—into part of the coat-check’s general inventory such that, if the business fails, the customer becomes just another claimant holding a scrap of paper?
This is not a cute analogy. It is the only honest starting point for analysing how “clarity” can fail in an intermediated market. Modern digital-asset venues replicate the coat check at scale and conceal it behind design. They take custody—directly or through layered custodianship—and issue customers an internal ledger entry. That ledger entry is displayed as a balance. The customer experiences it as ownership. Yet the venue, like the coat-check attendant, controls the underlying asset: it holds the keys or controls the arrangements that determine whether the asset can be moved. The customer’s ability to “use” the asset is mediated by the venue’s rules: withdrawal windows, verification checks, risk controls, discretionary freezes, fee schedules, and “temporary pauses”. The balance is not the coat. It is the ticket.
The CLARITY Act is vulnerable precisely here. It can assign categories, allocate jurisdiction, and define regulated activities, yet still leave the central retail confusion intact: the idea that because a protocol is capable of direct transfer, or because a token falls into a given statutory box, the customer must therefore possess something property-like when they hold a venue balance. But capability is not custody. Classification is not segregation. A definition does not prevent commingling. A label does not decide priority in insolvency. If the Act does not force the coat-check relationship to be stated and regulated in mechanisms rather than rhetoric, it will produce clarity on paper while preserving opacity where it matters—at the point where customers discover, too late, that they were holding tickets.
So the triad is introduced as a discipline, not as theory. Control is the operational reality of custody and discretion: who can actually move the asset and on whose say-so. Entitlement is the legal and contractual claim: what the customer can demand and how easily that demand can be deferred, qualified, or denied. Property is the insolvency-facing truth: whether the customer’s claim follows the asset, remains insulated from the intermediary’s failure, and is enforceable against third parties, or whether it collapses into a mere unsecured debt claim against a broken counter. That translation—from coat check to market structure—is the bridge the CLARITY Act must cross if it wants to deliver clarity rather than merely reorganise terminology.
The Triad, Made Concrete: Control, Entitlement, Property
The triad is simple once it is stripped of ornament. It names three different facts that people repeatedly treat as one, and it insists they be kept separate because law and markets punish the confusion.
Control is who holds the coat. Not who paid for it, not who feels entitled to it, not who can point to it through glass, but who actually has it in hand and can decide what happens next. Control is practical power: the ability to release, retain, delay, substitute, lend, misplace, or refuse. In any intermediated system, control sits where custody sits, and custody sits with the party behind the counter.
Entitlement is what the ticket lets the holder demand. The ticket is not nothing; it is the formal expression of a claim. It gives the holder standing to ask for return, and it sets the terms under which the demand is meant to be honoured. But entitlement is also where the fine print lives. It is shaped by rules, conditions, verification checks, hours of operation, “temporary pauses,” and discretionary exceptions. A ticket can be a strong entitlement or a weak one, and weakness often hides behind polite language.
Property is who owns the coat against the world. It is the hard question that only becomes visible when the polite assumptions die. If the coat-check counter catches fire, if the operator disappears, if the business is raided, shut down, or goes insolvent, property decides whether the coat is still yours in law or merely part of a general pile from which you must beg a distribution. Property is the difference between “return what is mine” and “queue with everyone else and hope.” It is the point at which the legal system decides whether your claim is tied to the coat itself or reduced to a debt claim against the coat-check’s estate.
That is the triad. Control answers “who can act.” Entitlement answers “what can be demanded.” Property answers “who owns, even when everything breaks.”
Where People Go Wrong: Tickets Masquerading as Coats
The first mistake is treating a ledger entry as the asset. A ledger entry is a record of what someone says you are owed inside a system they operate. It is an internal statement of position, not the thing itself. It may be accurate. It may be honoured. It may even be backed by real assets most of the time. But it is still a record—an assertion—until it is matched to custody, segregation, and enforceable rights that survive stress.
The second mistake is trusting the user interface as if it were a title deed. A UI balance is designed to feel like possession because that feeling keeps customers inside the system. The interface collapses everything into one comforting impression: “you have X.” In reality, the interface is merely a display layer over contractual terms, operational discretion, and whatever custodial arrangements sit beneath. When trouble arrives, the courts do not enforce feelings. They enforce relationships.
The third mistake is mistaking a right to “request withdrawal” for ownership or control. A request is not a power. A request is not possession. A request is not segregation. And a request is certainly not priority. Possession means the ability to move the asset without asking permission. Segregation means the asset is held separately and identifiably as yours, not merely noted in a database row. Priority means that, if the intermediary fails, your claim is not treated as one more unsecured debt but stands ahead of general creditors because it attaches to the asset itself. A withdrawal clause that can be paused, delayed, conditioned, or denied at the operator’s discretion is not the same as any of these, however confidently it is marketed.
These are ordinary errors, but they become catastrophic because they all point in the same direction: they mistake entitlement for property, and they confuse visibility for control. The result is always the same. When the counter is stable, the ticket behaves like a coat. When the counter breaks, the ticket becomes what it always was: a claim, competing with everyone else’s claims, against the party who held the coats.
How the CLARITY Act Trips Here: Clarity About Labels, Fog About Tickets
The CLARITY Act can draw categories with impressive confidence. It can divide the world into statutory boxes, map activities to regulatory lanes, and tell agencies where their borders lie. That kind of clarity has value, but it is not the clarity that retail markets actually need, because it does not dissolve the central confusion that harms customers: the difference between holding an asset and holding a claim to an asset.
The Act inherits the market as it exists, not as the rhetoric imagines it. Most retail activity is not direct interaction with a protocol. It runs through venues, brokers, custodians, payment rails, and layered service providers that sit between the customer and the underlying asset. Those intermediaries hold the assets, control movement, and present customers with balances—tickets—inside internal systems. The customer experiences “ownership” through an interface, while control remains behind the counter.
That is where the Act can trip over its own promise. A capability-based or category-based regime risks encouraging the reader to believe that once the asset is properly classified, the customer’s position is therefore secure or property-like. But classification does not change who holds the keys. A jurisdictional lane does not force segregation. A definition does not prevent commingling, reuse, discretionary freezes, or the quiet conversion of “custody” into credit risk. If the statute treats market structure as an afterthought—something to be handled by disclosure, or by vague “customer property” language—then it will produce clarity about taxonomy while leaving the ticket-coat confusion intact.
In other words, the Act may be perfectly clear about what the asset is, yet remain unclear about what the customer has. And in a market dominated by intermediaries, that second question is the one that decides outcomes.
One Focus Area: “Customer Property” Without Customer Control
This is the only area worth drilling into, because it is where everything real happens. Retail customers rarely hold control. They use venues. They rely on custodians. They interact with interfaces that display certainty and hide structure. So the question is not whether a protocol is capable of peer-to-peer transfer in the abstract. The question is what the law does when the customer has handed the coat over.
“Customer property” is the phrase that sounds protective and can still be empty. It becomes meaningful only if it is welded to custody mechanics that change outcomes under stress. Without that weld, the statute merely dignifies a ticket with the language of ownership while leaving control—and therefore the power to harm—with the intermediary.
Customer protection, in practice, turns on four custody facts. First, segregation: are customer assets kept separate and identifiable, or merely “separately accounted for” inside an internal ledger while the underlying assets are pooled? Separate accounting alone is a spreadsheet comfort. It is not a barrier against commingling, double use, or estate capture. Segregation must mean that a customer’s coat can be pointed to as a coat, not as a line in a list.
Second, enforceable withdrawal: is withdrawal a right with narrow, objective limits, or a request subject to broad discretion and “temporary pauses”? A right that can be paused whenever liquidity is tight is not a right; it is a marketing sentence. If the customer has no control, withdrawal must be the practical substitute for control, and it must be enforceable rather than aspirational.
Third, reuse constraints: can the coat-check lend coats out, pledge them, or treat them as inventory? If “customer property” permits rehypothecation or functional borrowing, then the customer is not being protected as an owner; the customer is being treated as a lender. The statute must force the business to choose: safekeeping custody with strict limits, or a credit product with explicit risk and corresponding regulation. The middle position—calling it custody while using it like funding—is the precise abuse the phrase “customer property” is supposed to prevent.
Fourth, priority and insolvency treatment: when the counter catches fire, are customer assets insulated from the intermediary’s general estate, or do customers stand in line as unsecured claimants? This is where the rhetoric is either vindicated or exposed. Property language is meaningless if it does not produce property outcomes in insolvency.
That is why the single question that matters is brutally simple: does the law force the coat-check to keep each coat separate and identifiable, with withdrawal rights that cannot be casually suspended, and with priority rules that keep customer assets out of the intermediary’s general pool? If the answer is yes, “customer property” is real. If the answer is no, “customer property” is a label applied to a ticket.
What a Better “Clarity” Looks Like: Writing Protections That Cannot Be Misread
Real clarity is not achieved by refining definitions until the statute reads like a taxonomy. It is achieved by drafting core protections so plainly and mechanically that nobody—consumer, venue, lawyer, regulator, judge—can pretend a ticket is a coat. The Act’s consumer-facing heart should therefore read less like a classification scheme and more like an allocation of custody duties and failure outcomes.
Start with segregation, and draft it as a physical fact rather than an accounting posture. “Separate accounting” is not enough, because accounting can be honest and still be useless. The statute should require that customer assets held by an intermediary are maintained in a manner that is individually identifiable, not pledged, not pooled in a way that destroys traceability, and not treated as the intermediary’s assets for financing or operational purposes. The rule must bite at the custody layer: if the intermediary holds, it holds for customers, with controls that make customer assets auditable and estate-resistant.
Then make auditability enforceable rather than performative. A regime that relies on periodic attestations, marketing dashboards, or voluntary proofs leaves the same old ambiguity intact, just dressed up in metrics. Auditability needs to mean that a competent examiner can verify, at a given time, that customer assets exist, are not encumbered, are not double-counted against other obligations, and match customer entitlements. The duty should be continuous in principle, and enforceable in practice: record-keeping standards, reconciliation requirements, retention obligations, and penalties for misstatement that are strong enough to outweigh the commercial temptation to blur lines.
Next, constrain withdrawal discretion with hard edges. If the customer does not have control, withdrawal is the functional substitute for control, and the law should treat it that way. The statute should presume prompt withdrawal and permit delays only under narrowly defined, objectively testable circumstances—fraud, legal compulsion, clearly specified operational outages—with time limits, notice requirements, and escalating obligations as the delay extends. Broad “risk management” discretion is exactly how tickets are kept looking like coats until the venue needs the coats for itself.
Finally, make insolvency treatment explicit, because this is where all the polite language is tested. If the Act means “customer property,” it should say, in terms a bankruptcy court cannot ignore, that customer assets held in custody are not property of the intermediary’s estate, are held for the benefit of customers, and must be returned in kind where possible, with clear priority rules when return in kind is not possible. If the Act permits lending or reuse, then it should force the relationship to be treated as credit: the customer is taking counterparty risk, and the statute should not allow that risk to be hidden behind the vocabulary of custody.
A better CLARITY Act does not merely classify assets. It classifies relationships and then imposes custody mechanics that make misdescription expensive. It drafts so that a venue cannot market tickets as coats, cannot rely on internal accounting as a substitute for segregation, cannot suspend withdrawal as a business strategy, and cannot push customers into the unsecured queue while still calling the arrangement “customer property.” That is clarity that survives contact with failure.
Conclusion: The Triad Is a Discipline, Not a Theory
The triad is not philosophy and it is not a slogan. It is the minimum language required to prevent the same relationship being described three different ways, depending on who is selling it, regulating it, or suffering it. Control names the practical power that sits with custody. Entitlement names the claim the customer actually has under the rules. Property names what survives when the counter breaks and the polite assumptions evaporate.
If the CLARITY Act wants to deliver clarity rather than classification theatre, it must draft protections that respect those distinctions. Otherwise it will remain clear only about labels while leaving the market free to keep doing what it has always done: hand out tickets, call them coats, and let the customer discover the difference only when there is smoke in the room.