One Vault. Two Continents. Completely Different Questions.
SEC Commissioner Peirce's Headstands and Summervaults asks what a crypto vault is under Howey and Reves. Europe asks who is providing which regulated activities. Same protocol, different map: Recital 94, closed CASP services, professional basis, and Recital 22.
Updated deep dive comparing SEC Commissioner Hester Peirce's 22 July 2026 statement Headstands and Summervaults with the European MiCA perimeter for crypto vaults, yield strategies and onchain lending. Core thesis: US analysis classifies what the vault is (Howey, Reves, investment company, note); MiCA asks whether an identifiable person provides a regulated crypto-asset service on a professional basis. Principles travel; the legal map does not. MiCA Article 3(1)(16) closed list (149 articles); no lending/borrowing/vault-management/yield licence. Recital 94 and ESMA/EBA Article 142 report confirm intentional omission; staking sits in the same legislative space. "Professional basis" undefined: regularity, remuneration and public offering count against you; size does not save you. Recital 94 is not a business-model safe harbour. Two doors: Door One (activity not on Article 3) vs Door Two (Recital 22 fully decentralised without intermediary). Sequence: activities first, then Article 3, then Recital 22. Matrix adds receipt-token issuance as separate ART/whitepaper analysis. Custody Art. 3(1)(16)(a); curator discretion vs portfolio management Art. 3(1)(25) "client-by-client" argument for pooled vaults is unsettled. BaFin Ethena GmbH March 2025 USDe order and ART-vs-investment-product line; Art. 3(1)(6) ART definition; Article 4(2) whitepaper exits unavailable once ART. EMTs Art. 3(1)(7); EBA June 2025 PSD2/MiCA overlap opinion. Commission/MFSA Recital 22 checklist (admin keys, concentrated governance, custody, closed code, named marketing); Aave/Compound turnout 3-5%; ring-fencing may evidence centralisation. Beyond MiCA: AIFMD pooled funds, Art. 61 reverse solicitation (ESMA Feb 2025 narrow), DORA, GDPR, national credit/crowdfunding law. Answers: MiCA Howey equivalent for vaults? Recital 94 lending safe harbour? Professional basis? Recital 22 vs 94? Custody and curator portfolio management? Receipt tokens ART Ethena? EMTs PSD2? AIFMD after MiCA gap? Reverse solicitation for offshore vaults?
One Vault. Two Continents. Completely Different Questions. MiCA Edge Cases | Where Innovation Meets Regulation Why Europe's Answer Looks Nothing Like Hester Peirce's On 22 July 2026, SEC Commissioner Hester Peirce published a statement titled Headstands and Summervaults . It addressed one of the crypto industry's fastest moving areas: crypto vaults, automated yield strategies and onchain lending. Her message would have been familiar to anyone who has spent time around US securities law. Moving an activity onto a blockchain does not move it outside the securities laws. Depending on how a vault is structured, it may be an investment contract, an investment company or a note. The analysis begins, as it so often does in the United States, with Howey and Reves. For developers building in Europe, the instinctive response is almost immediate. "What's the MiCA equivalent?" It is an understandable question. It is also the wrong one. Not because Europe lacks an answer, but because it starts from a different question. The United States asks what a vault is. Europe asks what somebody is doing. That distinction sounds almost trivial. It is anything but. It explains why two regulators can examine the same protocol, agree on every technical detail, and still arrive at entirely different legal conclusions without either being inconsistent. More importantly, it explains why so many founders spend months searching for the European equivalent of an American legal test that was never intended to exist. This is where many founders unfold the wrong map. They read American guidance and assume Europe is trying to solve the same problem. The natural instinct is to search for the European version of Howey. There isn't one. MiCA was never intended to become a European securities code. It was designed to authorise and supervise crypto asset service providers. Before asking whether a vault resembles a security, Europe asks something far more practical. Is an identifiable person providing a regulated crypto asset service on a professional basis? It is an almost disappointingly practical question. Yet nearly every issue discussed in this piece flows from it, including the one part of that sentence nobody ever stops to define. We will come back to that. An American securities lawyer examining a vault is likely to spend hours analysing the legal nature of the arrangement. Does it represent an investment contract? Does it resemble an investment company? Could it qualify as a note? Technology matters, but only because it affects the application of existing securities law. A European supervisor often begins somewhere entirely different. Who controls the assets? Who decides where capital is allocated? Who upgrades the contracts? Who operates the interface? Who receives the fees? Who has the ability to intervene when something goes wrong? Those are not the same questions, so they rarely produce the same conversation. One framework begins with legal classification. The other begins with operational responsibility. From that point onward, the analyses gradually diverge. That is why Peirce's statement is simultaneously essential reading and the wrong map for Europe. The principles travel well. Automation does not eliminate legal responsibility. Novel technology does not exempt familiar financial activity. Marketing labels matter less than economic reality. Those observations remain true whether the protocol is deployed in Delaware or Dublin. The legal framework does not travel nearly as well. The American map reaches one destination. The European map begins somewhere else. MiCA Begins With Activities, Not Products The distinction becomes obvious the moment you open MiCA. Unlike traditional securities legislation, MiCA does not begin by classifying crypto products according to what they resemble. It begins with a closed list of activities. Article 3(1)(16) identifies ten crypto asset services that require authorisation when provided on a professional basis, including custody and administration, operation of trading platforms, exchange services, execution and transmission of orders, advice, portfolio management and transfer services. Together they define the perimeter of MiCA's CASP regime. That word, closed , is doing an enormous amount of work. Financial regulation often expands over time. Supervisors interpret broad principles, markets evolve, and new products gradually find themselves pulled inside existing rules. MiCA was drafted differently. The legislators deliberately listed the activities they intended to regulate. That means what is not on the list matters every bit as much as what is. There is no crypto asset lending service. There is no borrowing service. There is no "vault management" licence. There is no standalone yield generation service. For legislation spanning 149 articles, those omissions are striking. They are also entirely intentional. Recital 94 leaves little room for doubt. The Regulation expressly states that it does not address the lending and borrowing of crypto assets, including e money tokens, and should not prejudice applicable national law. Rather than creating a harmonised European framework for crypto lending, the legislators consciously decided not to. ESMA and the EBA later confirmed exactly the same position in their joint Article 142 report. MiCA contains no definition of crypto lending because it was never intended to create one. The same observation extends beyond lending. The Article 142 report analyses staking, lending and borrowing together, yet none of the three appears in Article 3's list of regulated crypto asset services. A pure staking protocol therefore occupies much the same legislative space as a pure lending protocol. Both remain outside MiCA's harmonised licensing regime unless they begin performing other regulated activities. There is also a phrase sitting quietly inside the CASP definition itself that deserves more attention than it gets. MiCA applies to services provided on a professional basis, and it never says what that means. No revenue threshold. No user count. No transaction volume. The safest reading borrows from how the same phrase is treated elsewhere in European financial law: regularity counts against you, getting paid counts against you, offering the service to the public counts against you. Size does not save you. A three person team quietly earning meaningful fees from a public vault is acting on a professional basis whether or not anyone involved would describe it that way. This is not a loophole. It is a legislative decision. This is also where many founders stop reading MiCA. They discover that lending is absent from Article 3, close the Regulation and congratulate themselves on finding a gap. Unfortunately, MiCA does not stop there. The supervisor has only just opened the file. The Headline Activity Is Rarely the Whole File One of the easiest mistakes in financial regulation is to focus on the headline activity while overlooking everything happening around it. That mistake is particularly easy to make in crypto because products are designed to feel seamless. A user experiences a single vault. A supervisor rarely does. By the time a protocol reaches the market, lending may sit alongside custody, portfolio allocation, governance, execution, token issuance and treasury management. Commercially, those features belong to one product. Legally, they may belong to several different regulatory analyses. This is where many founders discover that Recital 94 answers a much narrower question than they first assumed. It excludes lending from MiCA's harmonised framework. It does not exclude everything built around lending. A theoretical lending protocol is relatively easy to analyse. One party supplies capital. Another borrows it. The protocol facilitates the transaction. If lending genuinely is all that happens, Recital 94 tells us that MiCA deliberately leaves the activity outside its harmonised framework. Commercial va