The FCA Just Gave DeFi Front Ends 28 Days and a 2027 Deadline
The FCA's CP26/36 consultation asks where regulated crypto activity ends and ordinary software begins. The answer will decide who carries the permission burden, and the firms with the most at stake aren't exchanges. They're the people who write the interface.
The most valuable sentence in UK crypto policy right now isn't about bitcoin. It's about what counts as software. The FCA opened consultation CP26/36 on October 21, and the headline is exemptions. The substance is a permission burden that's about to land on one side of a line nobody's drawn cleanly yet. My read: the developers win, the middlemen lose, and most people are watching the wrong part of this.
Where the line lands
The paper works through carve-outs introduced by recent legislative changes. Temporary settlement arrangements. Qualifying stablecoin holding inside a payment flow. Certain proprietary trading. And technical services that do nothing more than give a user access to another provider or a decentralised protocol.
That last one is the whole game.
There's a difference between being an intermediary that arranges a transaction and being a piece of software that opens a door. Those sound similar when you write them in a press release. They're completely different businesses when the FCA asks what kind of authorisation you hold. One path means a full permission set and the compliance headcount that goes with it. The other means you keep shipping.
Follow the money and you find the same thing every time. The cost of being classified as an arranger isn't the licence fee. It's the ongoing infrastructure: reporting, monitoring, capital, staff. A mid-sized firm staring at that stack is looking at a seven-figure commitment over a few years, and that's before the legal bills from the argument about whether it applies at all.
Here's the thing about regulation built on facts and circumstances. It's honest. It's also expensive, because it means nobody gets an answer until someone looks at their specific setup. Small teams can't afford to buy that answer preemptively. Big ones can. That's a competitive moat dressed up as a rule.
The calendar is the real story
Responses close November 18. That's twenty-eight days from publication for a question that determines the structure of an entire industry. If you've ever tried to get a legal opinion on a novel activity inside a month, you know how that goes. Most firms will submit something thin or nothing at all. The ones with policy teams already on retainer will submit two hundred pages.
Then nothing happens for a while. Final guidance isn't expected until January 2027. The broader UK perimeter goes live on October 25, 2027. So firms get roughly nine months between the final text and the wall. Nine months to rebuild product architecture, retrain staff, and file applications that the FCA has said should be in the queue well ahead of time.
That's not a lot of runway. But it's not zero either, and the firms that treat the interim as a planning window instead of a waiting room will be the ones still standing in late 2027.
The case against my read
Let me steelman the other side. The FCA isn't waving a wand over DeFi. That's the obvious pushback and it's correct. Nothing in this paper declares every front end exempt. Whether an exclusion applies turns on actual activities and actual facts, and this is consultation guidance, not the final handbook. Text can change. Scope can narrow.
And there's a decent argument that a loose reading of "technical access" creates a giant loophole. If any interface pointing at a smart contract qualifies, then the perimeter has a hole in it big enough to drive a custody business through. You can bet the incumbent institutions will make that point loudly during the comment period. they've every incentive to.
So the bear case is straightforward. Nothing is settled, the final guidance may be tighter, and firms building on a generous reading of a consultation draft are building on sand. Fair. I don't dismiss it.
My verdict
I still think the direction is right, and the direction is what matters. A regulator that says, in writing, that providing technical access is different from arranging a transaction has made a structural decision. Tightening the edges later doesn't reverse it. It just moves the boundary a little. And a boundary that moves a little is a boundary you can plan around.
The losers here are the firms whose entire product is the arrangement. Custody-heavy intermediaries, platforms that sit between a user and a venue, anyone whose value proposition is being the trusted middle of a trade. Their permission burden doesn't shrink. If anything, the exclusion for pure technical access makes their position more expensive by contrast. When the cheap version of a service gets a lighter rulebook, the expensive version has to justify itself.
So ask yourself the question the FCA is implicitly asking. Do you want to be the venue, or do you want to be the door? Because the door just got a lot cheaper to operate, and the venue didn't.
One more thing. If your interface is the only realistic place a user can find a specific pool, are you really just providing access? Or are you the market? That's the question the industry will spend two years arguing about, and it'll be argued by whoever shows up to the consultation. The economics are tighter than people think, and the twenty-eight day window is the cheapest tap into anyone in this sector will get all cycle. Mining is an energy business that happens to produce bitcoin. Crypto regulation is a paperwork business that happens to produce a market. Write in.
Explore More
Key Terms Explained
The first cryptocurrency, created in 2009 by the pseudonymous Satoshi Nakamoto.
Following the laws and regulations that apply to financial activities, including crypto.
Who holds and controls your crypto assets.
Using computational power to validate transactions and create new blocks on proof-of-work blockchains.