SEC Issues No-Action Statement for DeFi Frontends: MEV Disclosure and Order Routing Transparency Now Required

What Changed and When

On April 13, 2026, the SEC Division of Trading and Markets issued a formal no-action statement, File No. 4-894, creating a conditional safe harbor for DeFi frontend providers. Under this framework, frontends can operate without broker-dealer registration, but only if they satisfy 12 specific conditions. The statement runs five years, expiring April 13, 2031. This is not guidance. It is a compliance deadline with teeth.

The timing is deliberate. The statement arrives one week after the April 6 joint response from the Blockchain Association and a16z to letters from Citadel Securities and SIFMA, both of which argued that MEV searchers should be classified as brokers. The SEC has now drawn a partial boundary. Frontends that stay passive and transparent get a path. Everything else stays in registration territory.

What the Filing Actually Requires

The 12 conditions in File No. 4-894 are not abstract. Several carry direct infrastructure implications.

Conditions 5 through 7 govern order routing transparency. Users must be shown alternative execution paths before a trade executes. Routes must be sorted objectively, by price or speed, and no route can be labeled "best." The frontend cannot exercise discretion in selecting a route on the user's behalf. The moment a frontend makes that choice, it crosses into broker-dealer territory.

Conditions 8 and 9 govern fee structure. Fees must be fixed and neutral across venues and assets. No venue-contingent rebates. No asset-specific markups. Variable fee structures that depend on which liquidity source fills the order are explicitly incompatible with the safe harbor.

MEV disclosure is mandatory. Frontends must explain MEV risks to users in plain terms and disclose what data protections, if any, are in place. This is the first time the SEC has used the term MEV in a formal no-action instrument and attached a compliance obligation to it.

Affiliated venue disclosure is required with equal treatment. If a frontend routes to a venue it has an economic relationship with, that relationship must be disclosed and the affiliated venue cannot receive preferential treatment.

Onchain record maintenance is required. Execution records must be kept onchain. The filing does not specify a retention window beyond the statement's five-year duration, but the implication is clear: post-trade auditability is now a legal requirement, not a product feature.

Frontends that take custody, intermediate between buyers and sellers, or make any discretionary routing recommendation remain fully subject to broker-dealer registration. The safe harbor is narrow by design.

Implications for DeFi Protocols and Infrastructure

The immediate pressure falls on aggregators, swap interfaces, and any frontend that routes across multiple liquidity venues on Ethereum, Solana, or emerging execution layers like Sui. Most of these products were built without the assumption that their routing logic would need to be auditable, disclosed, and verifiable at the transaction level.

Routing opacity is now a legal liability. Frontends that route through affiliated market makers without disclosure, or that sort routes using criteria that aren't price or speed, fall outside the safe harbor. This includes a significant portion of current aggregator designs where fee-sharing arrangements with liquidity providers influence route selection.

MEV disclosure creates a documentation gap. Saying "MEV exists" in a terms-of-service is not the same as disclosing MEV risks with specificity. Protocols will need to characterize the MEV environment their users are executing in, sandwich exposure, backrunning probability, latency arbitrage, and explain what mitigations exist. That requires data infrastructure most frontends do not currently have.

The neutral fee condition will force structural changes. Protocols that earn incremental revenue by routing to venues where they hold liquidity positions or receive rebates will need to either restructure those arrangements or register. The no-action safe harbor is incompatible with the current economics of several leading aggregators.

On Sui specifically, execution transparency infrastructure is nascent. The chain's architecture creates verifiable execution ordering at the base layer, but frontend-level disclosure tooling does not yet exist at the standard these conditions require. This is a gap that will close quickly as teams face a five-year compliance window.

Where Birdai's Infrastructure Fits

Birdai's infrastructure was built for exactly this: auditable execution data that satisfies the compliance conditions before they were written.

What to Watch Next

The next 90 days will clarify how major aggregators interpret the affiliated venue disclosure requirement, specifically whether fee-sharing arrangements with integrated liquidity providers constitute the kind of economic relationship that triggers disclosure obligations. Enforcement posture on that question will determine whether several leading products are inside or outside the safe harbor. Watch also for how Sui-native frontends respond: the chain's execution model is well-suited to meeting the onchain record requirements, but the frontend layer needs tooling that does not yet exist at compliance grade. The April 2031 expiration creates urgency, but the first real test comes when the first frontend claims safe harbor and the SEC responds.

Source: SEC Division of Trading and Markets, No-Action Statement, File No. 4-894, issued April 13, 2026.