House panel put DeFi’s regulatory boundaries under congressional scrutiny

The House Financial Services Subcommittee on Digital Assets, Financial Technology and Inclusion held a hearing on decentralized finance on September 10, 2024, bringing a dispute over software, intermediaries and financial regulation directly before Congress.

The hearing, titled “Decoding DeFi: Breaking Down the Future of Decentralized Finance,” did not enact legislation or settle which federal agency had jurisdiction over a particular protocol or token. Its significance was institutional: lawmakers formally examined whether financial services executed through blockchain-based smart contracts could fit existing rules, required a new framework or sometimes operated without an intermediary capable of performing conventional compliance duties.

Contemporaneous participants and coverage described it as Congress’s first hearing focused specifically on DeFi. The official record independently confirms its date, subject, witness roster and legislative discussion materials.

What the panel considered

Five witnesses appeared: Brian Avello of UDHC; Rebecca Rettig of Polygon Labs; Amanda Tuminelli of the DeFi Education Fund; Peter Van Valkenburgh of Coin Center; and Mark Allen Hays of Americans for Financial Reform.

The committee memorandum defined DeFi broadly as blockchain-based financial activity using smart contracts to enable permissionless, peer-to-peer services. It also cautioned that projects differed substantially in their actual degree of decentralization. Some retained organizations, developers, governance bodies or service providers with meaningful control, while others could be more difficult to associate with a traditional operator. The memorandum called misleading claims of decentralization “decentralization theater.”

That distinction was central to the policy problem. Financial regulation normally assigns obligations to identifiable parties such as brokers, exchanges, banks, custodians or money transmitters. A protocol composed of publicly available code and independently submitted transactions does not necessarily reproduce those roles. Conversely, placing a decentralized label on a service does not prove that no person controls its operation, collects fees or can change its rules.

Lawmakers also considered two unnumbered discussion drafts. One would have required the Securities and Exchange Commission, Commodity Futures Trading Commission and Treasury secretary to conduct a joint DeFi study. The other would have required Treasury to report on privacy-preserving technologies. Neither discussion draft represented enacted law, an introduced bill with a final number or a binding agency instruction on September 10.

Competing views of the regulatory perimeter

Most witnesses were affiliated with organizations supporting blockchain development or DeFi policy advocacy. Their written positions generally emphasized the difference between publishing software and operating a conventional financial intermediary. They warned that imposing intermediary-style duties where no controlling intermediary existed could burden open-source development, privacy and permissionless networks.

Hays presented the principal critical position. His written testimony argued that DeFi markets remained exposed to speculation, fraud, cybersecurity failures and reliance on crypto intermediaries, often without protections associated with regulated financial markets. He urged Congress to prioritize enforcement of existing requirements rather than create broad exemptions or a specially accommodating framework.

The disagreement echoed an existing executive-branch record. Treasury’s April 2023 DeFi illicit-finance assessment had found no generally accepted definition of DeFi and said services performing covered financial functions could have anti-money-laundering obligations regardless of the labels they used. Treasury also identified potential regulatory gaps, weak compliance and cybersecurity vulnerabilities.

Why the hearing mattered—and its limits

The September 10 hearing placed three unresolved questions on the congressional record: how to identify control, when software developers become financial service providers, and how privacy or permissionless access should be balanced against consumer-protection and illicit-finance obligations.

It produced evidence and competing policy arguments, not a final answer. No regulator approved a protocol, no DeFi activity received a blanket exemption, and no new compliance requirement became effective because of the hearing. The defensible event-day conclusion is narrower: Congress had begun treating DeFi as a distinct policy subject whose architecture could challenge rules designed around identifiable intermediaries.