• CryptoUK, the UK industry trade body, has responded to the FCA’s draft guidance on which crypto activities fall inside the regulated perimeter.
  • It broadly supports the approach but says parts of it would treat developers of non-custodial DeFi software as regulated by default, further than the legislation goes.
  • We could not locate CryptoUK’s own published response, so the detail here rests on Decrypt’s account of it.

A regulator is deciding where the fence goes, and the UK’s crypto trade body thinks it has been drawn around people who never signed up to be inside it. CryptoUK has told the Financial Conduct Authority that its draft guidance would sweep in developers of decentralised finance software who neither hold customer money nor run anything.

If writing and publishing open-source financial software makes you a regulated firm in the UK, almost nobody in that position will apply for authorisation. They will block UK users instead. That is the practical consequence for anyone here who uses a decentralised exchange or lending : not a safer, licensed version of the same thing, but a front end that stops loading on a British connection while the underlying code keeps running for everyone else.

What the perimeter actually is

Modern cityscape view of Canary Wharf skyline with river reflection in London, England.
The Canary Wharf skyline in London, home to the Financial Conduct Authority’s headquarters. Photo by Lina Kivaka on Pexels.

Every financial regulator works from a list of activities that require permission. Taking deposits, arranging investments, safeguarding someone else’s assets. Do one of them in the UK by way of business and you need authorisation from the FCA. Do something outside the list and you are free to get on with it. The edge of that list is what the industry calls the perimeter, and perimeter guidance is the regulator setting out, in plain terms, which side of the fence a given activity falls on.

For most of crypto this is awkward but workable. An exchange holds customer coins, so somebody is clearly carrying on a regulated activity and somebody can be made to answer for it. The FCA has been consulting through 2025 and 2026 on the rules that will sit under the UK’s crypto regime, with the government’s statutory instruments bringing activities such as trading platforms, custody and issuance into scope.

Where DeFi breaks the model

Decentralised finance is the part that does not fit. A lending protocol or an automated exchange is code deployed to a . Once it is live it executes by itself. There is often no company, no customer accounts, no ability to freeze anything and sometimes no mechanism to change the code at all. The developers who wrote it may have moved on years ago.

Regulation needs a person. The whole framework is built on the idea that someone is carrying on the activity, which means someone can be authorised, supervised and fined. When the software runs without an operator, the regulator has to decide whether the nearest available human counts. CryptoUK’s objection, as reported, is that the draft guidance leans towards saying yes by default rather than asking whether a particular developer genuinely exercises control.

The trade body is not arguing that DeFi should sit outside regulation entirely. Its position is narrower: that the guidance should track the legislation rather than extend it, and that publishing non-custodial software is not the same as running a financial service.

What we can and cannot stand behind

CryptoUK is an interested party. It represents firms that would bear the cost of a wider perimeter, and its reading of what the law permits is an argument rather than a finding. The FCA will publish its own summary of consultation feedback in due course, and that document, not a trade body’s submission, is what determines the outcome.

We have not seen CryptoUK’s response itself. Decrypt’s write-up is the basis for the characterisation above, and the specific wording of the objections may be narrower or broader than a summary suggests.

What to watch

Whether the final guidance keeps a control test, some version of the question “does this person actually determine what the software does?”, or drops to a simpler rule based on who built it. That single drafting choice decides whether UK users keep access to non-custodial protocols or start meeting geo-blocks.

Also worth tracking: whether the FCA addresses front ends separately from the underlying contracts. A website that lets you interact with a protocol is a much easier thing to regulate than the protocol itself, and regulators elsewhere have found that distinction useful. If the UK adopts it, the fence ends up somewhere quite different from where this consultation currently puts it.

Our policy coverage tracks the UK regime as the rules firm up, and if you hold coins yourself rather than on a platform, our guide to self-custody explains what changes and what does not.