The trading process for crypto assets involves multiple technical layers, with the user-facing interface at the forefront. These interfaces—including websites, browser extensions, mobile applications, and software embedded in self-custody wallets—are responsible for converting user-defined trading parameters into on-chain executable instructions. However, whether these interfaces constitute a "broker" in the legal sense has long lacked clear definition.
In the crypto space, the regulatory jurisdictions of the U.S. Securities and Exchange Commission (SEC) and the Commodity Futures Trading Commission (CFTC) often overlap. The SEC exercises oversight over securities-related crypto asset trading under the Securities Exchange Act, while the CFTC oversees crypto derivatives and commodity-type crypto assets under the Commodity Exchange Act. This dual-track regulatory structure creates a double layer of uncertainty for crypto frontends seeking compliance.
On April 13, 2026, the SEC’s Division of Trading and Markets released a staff statement providing explicit guidance on whether a "covered user interface" must register as a broker-dealer. The statement defines a "covered user interface" as a website, browser extension, or software application that helps users initiate crypto asset securities transactions on blockchain protocols. Meanwhile, the CFTC had previously addressed compliance pathways for self-custody wallets accessing derivatives markets via no-action letters and similar mechanisms. The coordinated efforts of both agencies on the crypto frontend mark a pivotal shift in U.S. crypto regulation—from fragmented enforcement to the construction of a systematic regulatory framework.
How "Covered User Interfaces" Are Defined and Regulatory Boundaries Drawn
The SEC staff statement first clarifies the scope of a "covered user interface." This definition includes three types of platforms: websites, browser extensions, and software applications, including software products embedded in self-custody wallets. Their core function is to help users prepare and transmit crypto asset securities trading instructions. The typical workflow is: users set trading parameters on the interface, the interface converts these parameters into blockchain-readable instructions, and users then sign and submit these instructions to an on-chain protocol via their self-custody wallet.
This technical definition carries significant legal implications. The statement explicitly limits the functional boundary to "assisting in the preparation of transactions," rather than "executing or matching trades." This means that software tools providing only the conversion of information between users and blockchain protocols are, in principle, not considered "brokers" under Section 15 of the Securities Exchange Act. However, the statement also emphasizes that the exemption applies only to interface providers meeting specific conditions. Any activities beyond "assisting in preparation"—such as trade matching, custody of funds, order routing, or providing investment advice—are excluded from the exemption.
The SEC and CFTC maintain consistency in this definition. On March 17, 2026, the CFTC publicly confirmed it would apply the SEC’s interpretive framework to the Commodity Exchange Act, making a clear distinction between securities-related and commodity-related regulation. This coordination is not a temporary arrangement—the two agencies signed a Memorandum of Understanding on March 11, 2026, establishing an institutional framework for interagency coordination and providing a unified approach to cross-jurisdictional frontend regulatory issues.
What Operational Conditions Must Be Met for Broker-Dealer Registration Exemption
The SEC staff statement offers a conditional exemption pathway for crypto frontends, but requires interface providers to strictly adhere to several operational constraints. All these conditions point to a core principle: the interface must remain technologically neutral and must not act as a financial intermediary.
Specifically, the exemption conditions cover seven areas. The interface must not actively solicit users to engage in specific crypto asset securities transactions. It must not provide investment advice or any information that could be construed as a transaction recommendation. It must not hold or custody user funds. It must not execute orders or decide routing on behalf of users. It must use objective pricing and routing logic. Compensation structures must be fixed and unrelated to routing. The interface must fully disclose fee structures, potential conflicts of interest, and associated risks to users.
For multi-routing scenarios, the requirements are even more specific. If the interface connects to multiple execution paths or liquidity sources, it must allow users to sort or filter options based on objective criteria (such as price or speed), and must not label any route as "best" or "most reliable." Additionally, the interface may not use promotional language such as "best price" to influence users’ trading decisions or execution paths.
The intent behind these requirements is clear: to draw a line between the frontend’s function as a technical tool and as a financial intermediary. Interfaces may display market data, asset prices, and estimated gas fees, and may charge clearly disclosed transaction fees, but may not intervene in trading decisions through routing choices, pricing optimization, or investment advice.
Why Fee Structure Neutrality Is Central to Compliance
Fee structure design is a key focus of SEC review. The statement requires that compensation for covered user interfaces must meet two criteria: it must be fixed and unrelated to routing. This means interface providers cannot earn differentiated commissions by directing users to specific counterparties, liquidity pools, or execution paths.
The rationale is to prevent conflicts of interest for interface providers. If an interface’s revenue is tied to the trading destination, it creates an economic incentive to steer users toward routes that benefit the provider rather than the user, undermining the interface’s role as a neutral technical tool. The SEC makes it clear that interfaces earning variable commissions based on trading direction, token selection, or routing destination may not qualify for safe harbor protection.
For aggregator wallets or DeFi frontends, this restriction is particularly significant. The SEC’s requirement for "objective routing and pricing logic" means that any interface steering users to specific pools or protocols for revenue purposes risks being classified as a broker-dealer. Therefore, fee structure neutrality is not just a technical parameter—it is a core factor in determining the legal status of the interface.
How the Five-Year Window Affects Compliance Planning for Frontend Developers
The SEC staff statement is explicitly temporary. Unless the Commission takes further action, the statement will automatically expire five years from April 13, 2026. This timeframe provides frontend developers with limited but clear compliance predictability.
From a developer’s perspective, the five-year window has a dual meaning. On one hand, it provides a certain compliance runway. DeFi frontends, wallet extensions, and mobile applications that have long operated in regulatory gray areas can now operate under a clear set of conditions, without facing enforcement risk for unregistered broker-dealer activity. On the other hand, the five-year term means compliance planning must account for this time constraint—the safe harbor is not permanent, and future legislation or formal rulemaking could alter the current standards.
The SEC is also soliciting public feedback on the statement, indicating that the framework is still evolving. The statement itself is not a formal Commission rule, but staff-level guidance, and does not carry the same legal weight as formal regulations. This means that ongoing comprehensive crypto legislation in Congress—including market structure bills aiming to clarify the SEC-CFTC regulatory split—could still materially impact the frontend regulatory framework.
How CFTC’s Coordinated Actions Cover Derivatives Trading Frontends
While the SEC issued frontend guidance, the CFTC took parallel coordinated action. On March 17, 2026, the CFTC’s Division of Market Participants issued a no-action letter to Phantom Technologies, allowing its self-custody wallet to provide users with access to CFTC-regulated derivatives markets without registering as an introducing broker, provided ten conditions are met.
The conditions in this no-action letter are instructive. Under these terms, the wallet allows users to view market data and submit orders for event contracts, perpetual contracts, and other CFTC-regulated derivatives directly to partner platforms. The wallet must not hold user assets or exercise discretion over routing or execution. The ten specific conditions cover user disclosures, direct access to partner platforms, marketing controls, recordkeeping obligations, bankruptcy notification requirements, and joint liability commitments with partners.
Although this CFTC action targets a specific entity, its framework aligns closely with the SEC’s frontend guidance: both require non-custodial, non-discretionary, and transparent information practices as prerequisites for compliance. Notably, the CFTC Chair has publicly stated that the agency is working with the SEC to modernize rules and ensure that on-chain software systems and frontends have a clear place within the U.S. regulatory framework.
Layered Impact of New Frontend Regulations on Different Platform Models
The new regulations impact different types of frontends in distinct ways, creating a layered effect.
Pure information display interfaces face the least resistance. Interfaces that only show market prices and allow users to construct trades independently generally do not touch on the core definitions of broker-dealer activity, so their compliance adjustment costs are relatively low. These interfaces already have a fairly clear compliance status under the current framework.
Aggregators that optimize routing or recommend trades face the greatest challenges. These interfaces, which drive decentralized trading access within the ecosystem, may need to be redesigned to meet the SEC’s neutrality standards. Business models that aggregate liquidity and provide users with optimal routing suggestions structurally conflict with the SEC’s requirements not to "determine trade routing" or use "best" labels.
Centralized platforms already registered as broker-dealers are largely unaffected by this guidance. The guidance primarily targets non-custodial crypto frontends previously operating in regulatory gray areas, not traditional market participants who have already completed registration.
On the derivatives side, the CFTC’s no-action letter provides a concrete compliance template for specific entities. Other wallet providers seeking similar exemptions may need to follow the same set of conditions, meaning the CFTC’s ten conditions could become the industry reference standard for non-custodial wallets accessing derivatives markets.
Legal Effect of Staff Guidance and Future Legislative Trends
Accurately understanding the legal status of the SEC staff statement is crucial. The statement is not a formal Commission rule and does not have the same legal force as official regulations. It represents the staff’s latest interpretation of the broker-dealer definition under the Securities Exchange Act, not a binding rule adopted through the statutory rulemaking process.
This legal status entails several limitations. The statement does not bind the courts—federal courts can independently determine whether a particular crypto asset is a security and whether a particular interface constitutes a broker-dealer when adjudicating disputes. The SEC Commission can also update, modify, or withdraw the guidance without going through the formal rulemaking process. The statement clearly notes that the Commission may further refine or revise the guidance based on public feedback.
Meanwhile, Congress is advancing comprehensive crypto legislation. Key Senate committees are expected to vote on market structure bills aimed at clarifying the SEC-CFTC regulatory split and establishing a unified rulebook for exchanges and market participants. The White House’s digital asset advisor has noted that previously "intractable" legislative differences on crypto have narrowed significantly, improving the outlook for passing relevant bills. If such legislation is enacted, SEC-CFTC coordination in crypto regulation will move from an administrative arrangement based on memoranda to a statutory institutional framework.
Conclusion
The series of actions by the SEC and CFTC around crypto frontend regulation in 2026 marks a shift in U.S. crypto oversight—from fragmented enforcement-driven approaches to the construction of systematic regulatory frameworks. The SEC staff statement provides a conditional broker-dealer registration exemption for covered user interfaces, with core requirements including non-custody, non-discretion, fee neutrality, and full disclosure. This exemption is temporary, offering a five-year window. The CFTC has implemented parallel measures for derivatives via no-action letters and has established an interagency coordination mechanism with the SEC through a Memorandum of Understanding. While this guidance does not carry the force of formal regulation, it currently offers the clearest regulatory reference for compliant operation of crypto frontends. The ultimate shape of this framework will be determined by future legislative developments.
FAQ
Q1: What types of software products are included as covered user interfaces?
Websites, browser extensions, mobile applications, and software embedded in self-custody wallets. Their core function is to help users convert set trading parameters into blockchain-executable instruction formats.
Q2: What are the core conditions for crypto frontends to obtain a broker-dealer registration exemption?
Core conditions include: no solicitation of specific trades, no investment advice, no custody of user funds, no order execution or routing decisions, use of objective pricing and routing logic, fixed fee structure unrelated to routing, and full disclosure of relevant information to users.
Q3: Will the exemption automatically expire after the five-year window?
Unless the SEC Commission takes further action, the staff statement will automatically expire five years from April 13, 2026. However, future formal rulemaking or Congressional legislation may provide a new framework before then.
Q4: What role does the CFTC play in crypto frontend regulation?
The CFTC oversees crypto derivatives and commodity-type crypto assets. The agency has provided a compliance pathway for non-custodial wallets accessing derivatives markets via no-action letters and has established an interagency coordination mechanism with the SEC through a Memorandum of Understanding.
