Have you ever built a clean interface that simply points a user toward a licensed trading firm and then wondered whether that one connection suddenly turns you into a broker? That question stopped being theoretical this week. Staff at the U.S. derivatives regulator issued a no-action position that, under tightly drawn facts, will not recommend enforcement against certain passive software providers for failing to register as introducing brokers. I have watched this debate for years, and the letter feels less like a victory lap than a map with fences around it.
What The New Staff Position Actually Changes
The relief is narrow on purpose. It covers passive software that helps a user reach a registered futures commission merchant, introducing broker, or designated contract market. The user stays a customer of that regulated firm. The software firm does not take the account, does not hold the money, and does not become the place where the trade legally lives.
That last point matters more than the headline. A lot of wallet and interface teams talk as if “we never touch the funds” is enough. In derivatives land, solicitation and order flow can still look like brokerage even when custody sits somewhere else. The letter tries to draw a line between a tool and an intermediary. Whether a particular product sits on the safe side of that line will depend on design choices that many teams treat as product features rather than legal facts.
In my experience, founders hear “no-action” and translate it as “we are cleared.” That is not how these letters work. A staff position is a statement that one division will not recommend an enforcement case for a specified failure, if the recipient stays inside the stated conditions. It does not rewrite the Commodity Exchange Act. It does not bind every other office. It does not bless fraud, hype, or a later product pivot that quietly becomes more hands-on.
A no-action letter is a pause on one enforcement theory, not a new license and not a rewrite of the statute.
The timing is not accidental. The same day, securities staff moved on a separate five-year path for eligible venues that want to handle tokenized versions of listed stocks. Market-structure legislation that would have split digital-asset oversight more cleanly failed a procedural vote days earlier. Agencies are using the tools they already have. Developers who were waiting for Congress to settle the map now have two staff-level paths instead of one statute.
Why Introducing Broker Status Kept Haunting Builders
An introducing broker, in plain language, is a person or firm that solicits or accepts orders in futures, commodity options, swaps, or certain retail commodity deals without holding customer funds. That definition was written for phone rooms and branch offices. Code can still perform pieces of the same job. A screen that routes interest, frames a product, or walks a user into an order ticket can look a lot like solicitation even if no human ever picks up a headset.
I have found that product managers underestimate how much “helpful UX” can look like brokerage. Auto-filled tickets. One-tap “open a futures account.” Banners that talk about leverage the way a salesperson would. None of those features feel sinister inside a sprint review. They can still pull a team toward registration questions that eat months.
Registered intermediaries already sit in a crowded stack: futures commission merchants, introducing brokers, designated contract markets, clearing houses, and associated persons. Each bucket carries its own books, exams, and conduct rules. Software teams did not want to inherit that stack just because a wallet could display a listed crypto future. The new position gives them a defined off-ramp, but only if the product stays passive in the way staff described.
The Ten Conditions That Decide Who Qualifies
Relief is not automatic. A provider has to live inside a list of conditions, file a notice, and accept the agency’s power to look under the hood. Miss one condition and the comfort of the letter fades. That is the part I would tape to a whiteboard before anyone ships a “derivatives tab.”
- The provider and covered personnel cannot be subject to statutory disqualification, including certain convictions and regulatory bars.
- Users must have a direct customer or membership relationship with the registered firm that actually handles the trade.
- Users must be able to reach that registrant without the software, so the tool is not the only door.
- The provider cannot publish advertising that would need National Futures Association pre-approval if the firm were a registered introducing broker.
- Trade execution, accounts, and asset control stay with the registered intermediary or exchange.
- The software remains passive and does not turn the developer into the customer-facing broker of record.
- A notice must be filed with the Market Participants Division before relying on the position.
- The filing must include consent to jurisdiction for investigations and enforcement tied to the covered activity.
- Every listed condition has to be satisfied, not treated as optional product guidance.
- The position lasts only until a Commission rule or guidance on the same activity takes effect.
Look at condition three again. Users must be able to reach the registrant without the app. That sounds small. It is not. If your interface is the only practical way a retail user can open the futures relationship, you start to look less like a browser and more like the storefront. Condition four is equally sharp. Marketing copy that would need self-regulatory pre-clearance if you were registered is off limits. Cute launch tweets can become a problem if they read like brokerage solicitation.
Perhaps the most interesting aspect is the consent-to-jurisdiction clause. Teams that wanted distance from U.S. process now have to accept it as the price of the safe harbor. That is a trade. Some offshore builders will refuse it. Some U.S. builders will file the notice and sleep better. Neither choice is free.
Passive Software Versus A Product That Quietly Brokers
Staff already sketched a similar idea in an earlier letter involving software that gave access to regulated derivatives while leaving execution and custody with registered firms. The new letter generalizes that fact pattern. It still assumes a model where the code is a doorway, not a desk.
Where does the model break? Custody is the obvious one. If the developer holds keys that control customer property used in the derivatives flow, the “passive” story gets harder to tell. Trade recommendations are another. A feed that screams “buy the dip on this contract” is not the same as a blank ticket. Explicit signals, managed strategies, and human chat that steers order flow all push the facts away from the letter.
I keep coming back to a simple test I use in diligence calls. Who does the customer think they hired? If the answer is the wallet brand, you have a problem. If the answer is the futures commission merchant on the account documents, and the wallet is just how they logged in, you are closer to the facts staff described. Perception is not the legal test, but it is a decent early warning.
| Product Choice | Closer To Relief | Closer To Broker Risk |
| Account relationship | User is customer of the registrant | User treats the app as the broker |
| Asset control | Registrant or user holds the funds | Developer can move customer property |
| Order handling | User sends orders to the registrant | App solicits, packages, or steers tickets |
| Marketing tone | Software features, not trade pitches | Copy that reads like brokerage ads |
| Access path | User can reach the firm without the app | App is the only on-ramp |
This table is not a statute. It is a way to force a product conversation before counsel has to write a memo. I have sat in rooms where engineering wanted a smarter default order type and legal wanted a blank screen. Both instincts can be right. The letter rewards the boring screen more than the clever one.
Crypto Wallets Sit In The Gray On Purpose
The public headline talked about crypto developers. The staff language talks about passive software in regulated derivatives markets. Those two sentences can both be true. A digital-asset wallet that connects a U.S. user to a listed crypto future through a registered intermediary may fit. A general-purpose DeFi dashboard that lets anyone lever an offshore perpetual may not.
Regulated crypto derivatives already live inside this agency’s world. Futures, options, and swaps on digital commodities are supposed to travel through the U.S. structure when they are offered to U.S. persons in the relevant ways. Enforcement cases against offshore platforms that sold leveraged crypto products to Americans without registration are part of that history. The letter does not reopen those products. It talks about the status of the software layer, not about making a previously illegal contract legal.
That distinction will get lost in social posts. Someone will claim U.S. users can now trade anything through any wallet. That is not what the paper says. American customers do not receive new product permissions. They receive, at most, a world in which some interface providers are less likely to be charged solely for missing introducing-broker registration when the rest of the stack is already registered.
I’ve found that the teams most likely to benefit are the ones that already partnered with futures commission merchants and never wanted the broker license. The teams least likely to benefit are the ones that built a full retail funnel and hoped a staff letter would wash it after the fact. Letters like this reward architecture that was conservative from day one.
How This Fits Next To Tokenized Stock Relief
On the same calendar day, securities staff published a separate five-year trading exemption for eligible venues that want to list tokenized National Market System stocks. Covered tokens need the same rights as the traditional shares they represent. Products that only track a price do not qualify. Venues face limits on symbols and activity. Smart contracts must be public and auditable. Trading in the token should stop when the primary exchange halts the underlying name.
Put the two actions side by side and a pattern shows up. Both agencies are carving operational paths with existing powers after a market-structure bill stalled. The Senate failed to clear a cloture vote on that bill, leaving the broader rewrite short of the votes needed to open debate. Some lawmakers later signaled they would keep talking. No second procedural vote was locked in at the time of these staff moves.
I do not read that as agencies going rogue. I read it as agencies refusing to freeze while Congress argues about titles and definitions. Builders who wanted a single statute now have two staff documents with sunset logic. The derivatives letter lasts until a Commission rule on the same subject arrives. The securities order is framed as a five-year experiment with a comment file attached. Temporary is the theme.
When legislation stalls, staff letters become the working constitution of the market. That can help shipping teams. It can also vanish when a formal rule lands.
Tax work moved on a different track. A House committee advanced a digital-asset tax bill covering staking rewards, lending, wash-sale treatment, dealer questions, and a proposed exemption for certain small network fees. That is not the same as market structure. It still tells you Washington is not idle. It is just moving in pieces.
What U.S. Developers Can Do With The Letter Tomorrow Morning
If you ship software that might touch listed derivatives, the practical sequence is dull and useful.
- Map every screen that mentions a futures product, an options contract, or a swap.
- Write down who owns the customer relationship on paper, not in the brand deck.
- Confirm users can open and use the registrant channel without your interface.
- Strip marketing that sounds like a broker pitching leverage.
- Check statutory disqualification facts for founders and covered staff.
- Decide whether you will file the notice and accept jurisdiction.
- Document why the product is passive, with screenshots and flow charts dated today.
That last bullet is the one teams skip. Memory fades. Features creep. A year from now someone will add a “smart order” module because conversion dipped. If you do not have a record of the original passive design, you will argue from vibes. Staff letters are fact-specific. Facts need paper.
Should every wallet file? No. If you never connect to a designated contract market or a futures commission merchant, this letter is not your project. If you only show spot balances, this letter is not your project. If you run an offshore venue for U.S. retail leverage, this letter is definitely not your project. Using a staff position as costume jewelry on a non-qualifying business is a good way to look worse in an exam.
The Risks That The Letter Does Not Touch
Fraud still matters. Manipulation still matters. Unlawful solicitation still matters. Breach of the conditions still matters. Registered exchanges and intermediaries still own their own duties. The letter is about one registration theory for one kind of software activity. It is not a shield for a sloppy market.
Retail access is another trap. Nothing in the position lets a developer offer a product that U.S. law otherwise blocks. If the contract cannot be sold that way, a prettier interface does not fix it. If the customer cannot lawfully trade that market, a notice filing does not create capacity.
There is also successor-rule risk. Relief lasts until the Commission adopts a rule or guidance on how introducing-broker duties apply to this software. A future framework could be friendlier. It could also be colder. Building a whole growth plan on the assumption that staff comfort is permanent would be, frankly, sloppy.
Associated person questions linger at the edges. The letter discusses personnel engaged in covered activities and the introducing-broker registration issue. Human support teams that start recommending specific contracts can create a second set of facts. Chat is not automatically “passive software.” I would treat live guidance as a separate legal workstream, not as a help-center footnote.
A Human Read On Why The Line Was Drawn This Way
Regulators have a boring problem. Software keeps eating functions that used to require a licensed human. If every API wrapper becomes a broker, innovation freezes. If no wrapper is a broker, the registration system becomes optional for anyone with a frontend. Staff tried to keep the licensed firm at the center of money, accounts, and execution, while letting code sit in front of that firm without automatically inheriting the license.
Is that the perfect line? Of course not. Perfect lines do not exist in markets where a button can be both a utility and a sales pitch. It is a workable line for a moment when Congress has not finished the larger map. I would rather have a workable line than another year of shrugs.
There is a cultural split inside crypto that this letter quietly exposes. One camp wants interfaces to disappear into protocol. Another camp wants branded super-apps that own the relationship. The relief is friendlier to the first camp when the protocol door opens onto a registered intermediary. The second camp still has a path, but it looks a lot more like actual registration.
Simple diligence scorecard: Direct customer tie to a registrant No developer custody of trading property Alternate access path exists Marketing stays non-brokerage Notice filed and conditions accepted Product changes logged before release
Use that scorecard in a weekly product meeting, not once a year with outside counsel. Feature drift is how good facts become bad facts. I have seen it happen on roadmaps that started as “view only” and ended as “we kind of route the ticket now.”
Questions Founders Should Ask Counsel This Week
Do we currently solicit or accept orders in a way that would make introducing-broker registration the default answer? If the honest reply is “maybe,” do not file a notice and hope. Fix the product or register.
Can a user complete the entire regulated relationship without us? If not, the letter’s access condition is already under stress.
Who is disqualified? This is unglamorous. It is also binary. A barred person on the cap table or in a covered role can wreck the theory.
What happens if we add signals, copy-trading, or a managed sleeve next quarter? Write the answer before growth asks for the feature. The letter is not a standing permission slip for every adjacent idea.
Are we prepared to be examined on the covered activity? Consent to jurisdiction is not ceremonial. If the thought of a document request makes the room quiet, you are not ready to rely on the position.
What This Means For Users, Not Just Builders
If you are a trader, do not confuse a prettier wallet with a new legal market. Your protections still ride with the registered firm that holds the account. Read that firm’s documents. Know where margin calls come from. Know who to call when a fill looks wrong. The software brand may be the face you like. The intermediary is still the party with the rulebook.
If a product cannot tell you, in one sentence, which registrant carries your account, walk away. Fancy branding is not a substitute for a name you can check on a registration database. That advice is older than crypto. It still works.
Institutional users already live closer to this model. Many of them access listed markets through software that never pretended to be the broker. The letter mainly reduces uncertainty for teams that want to offer a similar doorway to a broader audience without collecting a license they do not need. It does not invent a new retail casino.
The Political Backdrop Without The Soap Opera
Market-structure legislation aimed to split digital-asset oversight and create registration routes for exchanges and other intermediaries. It did not get the procedural votes to open debate. That failure is why these staff actions feel larger than their page count. When the big bill slips, small papers become the news.
I am not going to pretend staff letters replace a statute. They do not. They do let responsible teams keep building instead of freezing until the next Congress finds sixty votes for something. That is a modest good. Modest goods still count in a market that has spent years arguing about definitions while products shipped anyway.
Watch the comment files and the rule calendars. The derivatives position ends when a Commission framework arrives. The tokenized-stock experiment has a clock and a request for public input. Neither document is the last word. Both are usable words, which is more than builders had on Monday morning.
A Closing Read For Teams That Ship This Quarter
If your software is truly a doorway to a registered derivatives firm, this letter is the cleanest staff signal you have seen in a while. File the notice only if the facts are real. Keep the user relationship with the registrant. Keep custody and execution where they belong. Keep the ads boring. Keep a paper trail when the product changes.
If your software wants to be the broker in all but name, stop hunting for a footnote that makes that comfortable. Registration exists for a reason. The letter is not an insult to that reason. It is a recognition that not every line of code that touches a listed market should trigger the full broker stack.
Will some people overclaim? Yes. Will some people ignore the conditions and still paste “CFTC approved” into a launch thread? Also yes. That noise does not change the text. The text is conditional, temporary, and fact-bound. Treat it that way and you can actually use it. Treat it like a trophy and you may meet the part of the agency that still brings cases.
I keep a simple bias after reading papers like this. Build the dull version first. The dull version is the one staff can recognize. Flash can come later, after a rulebook catches up, or after you decide the license is worth the cost. That is not a romantic product philosophy. It is how you stay in the market long enough for the next letter, the next rule, and the next chance to ship something people can actually use without a subpoena hanging over the standup.
