Share article

CT loves to argue about vibes, until regulators show up and ask who is "in charge." Yesterday's House Financial Services Committee hearing put that question back on the main timeline, with the Blockchain Association's Summer Mersinger urging the SEC to stop treating decentralized finance (DeFi) like a traditional middleman business and start treating it like infrastructure. [1]
Mersinger's core message was simple: DeFi protocols are closer to open, neutral plumbing than they are to a broker, exchange, or other intermediary. Because of that, she argued DeFi should get tailored regulatory treatment, rather than being forced into compliance frameworks built for companies that custody customer assets, run order books, or control access.

Enjoy articles without ads?

Register for free and get unlimited access to all articles.

What Mersinger told lawmakers

Testifying Wednesday, Mersinger framed DeFi systems as software-based networks that can facilitate financial activity without the same role played by centralized intermediaries. Her ask, directed at the SEC's approach to crypto markets, was for "appropriately tailored" consideration that recognizes how decentralized systems actually operate. [2]
The distinction matters because many SEC compliance regimes assume there is an accountable, controllable entity in the middle that can register, surveil transactions, restrict users, and implement standardized disclosures. In DeFi, the "service" may be smart contracts (self-executing code) deployed on public blockchains, with governance and upgrades distributed among token holders, contributors, or a foundation structure depending on the project.
Her argument does not read as a call for zero oversight. Instead, it tries to separate the technology layer (open protocols) from the risk layer (activities that look like traditional finance, such as leverage, market making, or products marketed to retail).

Why "DeFi is infrastructure" is the real regulatory battleground

This is not just semantics, it is the legal lever.

If regulators classify DeFi protocols as intermediaries, compliance expectations can snap into place quickly: registration obligations, broker or exchange style rules, and potential liability theories that pull in developers, front end operators, and governance participants. [3]

If DeFi is treated as infrastructure, the focus shifts toward specific conduct and touchpoints, like custodial gateways, hosted interfaces, or identifiable promoters, rather than the base protocol itself.
That framing has become a recurring industry strategy because it narrows the question from "Is this whole protocol an illegal unregistered entity?" to "Which parts of the stack behave like a regulated financial service?"
Crypto policy watchers on X circulated the Blockchain Association's position via its DeFi focused account, signaling that the group wants the SEC to build a DeFi-specific lane instead of porting over rules designed around centralized control. [4]

The subtext is familiar to anyone who has spent time in DeFi Discords: builders want clarity, but they also want to avoid a regime that effectively requires someone to "turn the protocol off" to comply.

What this could change for builders and users

If the SEC seriously adopts an infrastructure lens, it could reshape where enforcement and compliance pressure lands:

  • Protocol developers and governance participants could argue they are publishing and maintaining software, not operating an intermediary. That does not grant immunity, but it can change the facts regulators emphasize.
  • Front ends and hosted interfaces could become the primary compliance chokepoints, since they are often run by identifiable teams that can implement geo-blocking, disclosures, and controls.
  • Riskier DeFi activities (high leverage, synthetic exposure, or products that resemble securities offerings) would still be on the radar, but the regulatory approach could target those behaviors instead of treating all DeFi rails as a single regulated "entity."

For users, the practical impact would show up in UX. If policy pushes obligations up to interfaces, traders might see more gating and more region-based restrictions, while underlying contracts remain live onchain. If policy instead treats the protocol itself like an intermediary, users could see broader disruption as teams preemptively sunset features to reduce legal exposure.

Notably, no new SEC rulemaking came out of this hearing. The testimony is part of an ongoing effort to influence how the SEC interprets its authority over decentralized systems, especially as Congress debates crypto market structure and regulators continue to test legal theories in enforcement actions. [5]

The takeaway: watch the definition, not the drama

The next catalyst is not a meme coin cycle, it is language. If "infrastructure versus intermediary" becomes the working frame in draft guidance, speeches, or litigation arguments, that is a meaningful shift for DeFi.

What to watch next:

  • Whether SEC officials publicly acknowledge a differentiated DeFi framework, even informally.
  • Whether lawmakers translate this framing into market structure text that limits intermediary-style obligations to entities with clear control and custody.
  • Whether enforcement focus tightens on identifiable interface operators and promoters, rather than generalized claims against protocol code.

Risk remains: a lot of DeFi still walks and quacks like finance, even if the stack is decentralized. The fight is over whether the SEC regulates the rails or the actors using the rails, and the Blockchain Association just made its preferred answer clear.