Citadel Securities and SIFMA Oppose SEC DeFi Broker Exemption, Demand Full Registration for Tokenized Securities Platforms

Citadel and SIFMA Target MEV in DeFi Broker Fight

On April 26, 2026, Citadel Securities and SIFMA formally opposed the SEC's April 13 staff statement that carved out certain non-custodial DeFi user interfaces from broker-dealer registration requirements. Their position is not a procedural objection. It is a substantive argument that any platform facilitating tokenized securities trades — regardless of custody model — should face full broker-dealer registration. More critically for DeFi infrastructure teams: both institutions explicitly named MEV extraction as an investor protection concern that the SEC cannot ignore if it formalizes this exemption.

This is the most consequential TradFi intervention in DeFi regulatory infrastructure since the original broker definition debate of 2022. The stakes are not abstract. Tokenized equities are live. RWA platforms are processing real order flow. And the incumbent financial establishment just put MEV on the SEC's enforcement agenda.

What the Filings Actually Say

The SEC's April 13 staff statement drew a line: non-custodial DeFi interfaces that do not hold customer funds or exercise discretion over trade execution would not automatically trigger broker-dealer registration under the Securities Exchange Act. This was a meaningful concession to the crypto industry's long-standing position that UI-layer access to permissionless protocols differs structurally from traditional brokerage.

Citadel Securities and SIFMA reject that line. Their submissions, as reported by RWA Times on April 26, characterize the exemption as creating an uneven playing field and argue that economic function — not custody — should determine regulatory classification. If a platform routes order flow, aggregates liquidity, or enables price discovery in tokenized securities, Citadel's position is that it is acting as a broker.

The MEV framing is where the filings get technically specific. Citadel's prior submissions characterized MEV as encompassing front-running, back-running, and sandwich attacks that arise when block producers or entities with privileged mempool access insert transactions for profit. SIFMA took this further, arguing that permitting MEV extraction in tokenized equities contexts would represent a material regression in investor protection standards — standards that took decades to build in traditional markets through Regulation NMS, best execution requirements, and exchange transparency rules.

The notice-and-comment rulemaking process is now the battleground. Citadel and SIFMA are expected to push hard against any effort to codify the April 13 exemption into formal rule text without explicit MEV prohibitions or disclosure requirements attached.

What This Means for DeFi Protocols and Infrastructure Teams

Protocol teams building on or adjacent to tokenized securities markets need to read this clearly. The regulatory conversation has shifted from "are you a broker?" to "does your infrastructure enable extractive order flow manipulation?" Those are different questions with different technical answers required.

The SIFMA framing treats all MEV as harmful by default. That is an oversimplification — MEV encompasses a spectrum of activity from benign arbitrage that tightens spreads to genuinely adversarial sandwich attacks that degrade execution quality for end users. But regulators do not start from nuance. They start from the characterization that politically powerful commenters provide. Right now, the most politically powerful commenters in this process have defined MEV as front-running.

Any protocol handling tokenized securities order flow that cannot demonstrate verifiable, auditable execution quality will face an uphill argument with the SEC. "We are non-custodial" is no longer sufficient cover. The question becomes: can you prove that block-level transaction ordering on your platform does not systematically disadvantage end users? Can you show consent mechanisms, disclosure of ordering incentives, and post-execution audit capability?

Protocols without answers to those questions should not wait for formal rulemaking to find them. The comment period will move faster than most DeFi teams expect, and informal staff guidance often hardens into enforcement posture before rules are finalized.

Where Birdai's Infrastructure Fits This Regulatory Moment

Birdai's architecture was built for exactly this evidentiary demand. The MEV Observatory tracks millions of decoded transactions across mainnet and L2 environments, providing independent, verifiable data on ordering behavior, sandwich activity, and searcher concentration. That is not a product feature in a normal market cycle. In the current regulatory environment, it is a compliance artifact.

Birdai Auction operates on a neutral auction model — block space is allocated through a transparent, competitive process that does not privilege any single searcher or builder with asymmetric mempool access. This is the structural response to Citadel's specific objection: that privileged access to pre-confirmation transaction data creates front-running opportunities analogous to payment for order flow abuses in traditional markets.

BirdSearch provides the post-execution audit trail that SIFMA's investor protection argument implicitly demands. If the SEC moves toward requiring disclosure of execution quality metrics for tokenized securities platforms, the ability to surface specific transaction-level ordering data on demand is not optional infrastructure. It is the difference between a platform that can demonstrate compliance and one that cannot.

Institutional positioning in this regulatory environment requires more than clean legal arguments. It requires verifiable, machine-readable evidence that MEV activity on a given platform is either absent, bounded, or subject to informed user consent. Birdai's infrastructure stack is designed to produce exactly that evidence.

What to Watch Next

The SEC's next move is whether to open formal notice-and-comment rulemaking on the April 13 staff statement or allow it to function as informal guidance without binding effect. Citadel and SIFMA will push hard for the former, because formal rulemaking gives them standing to embed their MEV characterization into rule text. Watch for SEC Commissioner statements in May and June 2026 on the scope of the broker definition review. Any signal that the Commission intends to address MEV explicitly in proposed rule language should be treated as a priority compliance trigger for every RWA protocol and tokenized securities platform currently operating under the assumption that the April 13 exemption holds.

Source: RWA Times, "We need lasting clarity – Crypto industry pushes SEC to formalize DeFi broker guidance", April 26, 2026.