DeFi Regulation: CryptoUK Pushes Back on FCA Guidance13 min read2,661 words

DeFi Regulation: CryptoUK Pushes Back on FCA Guidance

CryptoUK backs much of the FCA’s crypto perimeter guidance but warns it could sweep in DeFi developers. Here’s what the dispute means for UK firms.

DeFi regulation UKFCA crypto guidanceCryptoUKDeFi developerscrypto regulatory perimeter
DeFi Regulation: CryptoUK Pushes Back on FCA Guidance

Who Should Be Regulated in DeFi? CryptoUK Challenges the FCA

For a DeFi developer, it's not always obvious where "writing software" ends and "operating a financial service" begins. A protocol might be built by a team, governed by token holders, and used by people across multiple countries. That raises a basic regulatory question: when does contributing to the technology cross the line into carrying on a regulated activity?

CryptoUK wants the Financial Conduct Authority to make one thing clear: developing, maintaining, or securing a DeFi protocol - or taking part in its governance - should not automatically make someone a regulated firm. The trade group broadly supports the FCA's draft guidance on the UK crypto regime, but says some proposed interpretations go beyond what the underlying legislation is meant to cover.

This point matters well beyond one consultation. Guidance can affect how firms decide whether they need authorization, how investors assess legal risk, and whether UK-based teams choose to build or operate crypto services locally. Below is what the FCA is consulting on, what CryptoUK objects to, and a way for firms to think through the boundary without treating either software development or "decentralization" as a built-in exemption.

What is the FCA's crypto perimeter guidance about?

The FCA's consultation paper, CP26/36, deals with the boundary of the UK's developing crypto regulatory regime. In regulatory terms, the perimeter is the line between activities that need authorization and activities that fall outside the relevant rules. In this draft, the FCA proposes amendments to the Perimeter Guidance Manual (PERG) to reflect the FSMA 2000 (Cryptoassets) (Miscellaneous Amendments) Regulations 2026.

In practice, that boundary affects real decisions: whether a business needs to apply for FCA authorization, what it can do while its status is unclear, and how it structures relationships with customers and service providers. The FCA says the recent legislative amendments have left some firms uncertain. It also says applicants may get extra time where questions about the technical services exclusion have delayed authorization applications.

CryptoUK, which says it represents more than 150 crypto companies, generally supports the draft. It welcomed proposed exclusions covering certain temporary settlement and payment arrangements, assets backing UK-recognized stablecoins, proprietary trading and market making, and technical service providers.

CryptoUK's concern is straightforward: guidance should explain the legislation, not quietly expand it. That distinction matters because businesses may read guidance as a practical signal of how the FCA will assess their activities, even though guidance and legislation are not the same thing.

The consultation is part of a wider rulebook

The FCA is building the UK's crypto framework step by step. Core rules for crypto firms were finalized in June, and the wider regime is due to take effect on October 25, 2027. The FCA has also issued guidance ahead of its authorization window and worked with the Bank of England on a shared vision for tokenization.

CP26/36 focuses on how to interpret the perimeter as the legislative framework changes. The FCA expects to publish final guidance in January 2027. Until then, this is a consultation - still a proposal, not a final ruling on how each developer, protocol, or crypto business will be treated.

For firms making plans now, the timing matters. They have to separate what the law currently says from what the draft guidance proposes, and what still remains unsettled. Treating all of that as one category can lead to either unnecessary caution or misplaced confidence.

Why does CryptoUK want protection for DeFi developers?

CryptoUK's position is that writing, maintaining, or securing software should not, on its own, mean someone is carrying on a regulated activity. It makes the same point about participation in decentralized governance. The group says this fits the FCA's stated approach in DeFi: regulation should focus on who effectively controls a financial service, rather than assuming every contributor is the operator.

The practical problem is that protocol "contributors" and actual decision-makers may not be the same people. One person might write code and then leave. Another might handle security reviews. Token holders could vote on proposals, while a separate company provides an interface or runs a commercial service. CryptoUK argues a broad reading could blur those roles by treating any contribution as evidence of operating the protocol.

None of that means a developer can never be involved in a regulated activity. The key is what the person actually does and how that activity connects to the service. Publishing open-source code is not the same, in a factual sense, as controlling access, setting operational terms, or making decisions about a service offered to customers. The point isn't that one category is always exempt. It's that "developer" shouldn't be treated as the deciding label by itself.

Separate contribution from control

To assess this in the real world, CryptoUK argues it helps to split work into distinct functions:

  • Technical contribution: writing, reviewing, maintaining or securing code.
  • Governance participation: proposing or voting on changes, with the practical influence depending on the mechanism and participants.
  • Service operation: running or managing parts of the service users rely on.
  • Commercial activity: offering a product, arranging transactions, or maintaining customer relationships.

These can overlap, but they shouldn't be treated as interchangeable. A developer who also has effective control over how a financial service operates may be creating a different regulatory question than a contributor with no such control. Likewise, saying a project is "decentralized" doesn't automatically settle whether any identifiable person or organization exercises control in practice.

That's why CryptoUK's request is for clearer boundaries - not an argument that DeFi should sit outside regulation. Any workable approach has to tie the analysis back to conduct, responsibility, and control. Otherwise, firms may struggle to tell when something needs authorization and when it's simply part of building or maintaining software.

Where does CryptoUK say the draft goes too far?

CryptoUK argues some parts of the draft guidance may go beyond what the legislation supports. It highlights three areas: how the UK connection is defined, conditions attached to certain exclusions, and indicators that could narrow the technical services exclusion.

First, the draft proposes a link to the UK based on where a protocol is developed or governed. That could be relevant, CryptoUK says, but the concern is whether it would create a broader regulatory trigger than the legislation provides. For projects with contributors and users in multiple jurisdictions, a vague "location" test can be hard to apply consistently.

Second, CryptoUK points to requirements attached to exclusions for payments and proprietary trading. An exclusion only helps if firms can tell when it applies. If guidance interprets conditions more narrowly than the legislation, businesses may not be able to rely on the boundary they believe Parliament set. The practical impact will depend on the final wording and how each firm's activities fit the rules.

Third, CryptoUK objects to parts of the technical services exclusion that it believes could narrow it compared with the law. This isn't just a drafting issue. The FCA has acknowledged that uncertainty about this exclusion has slowed down some authorization applications, and says affected applicants will get additional time.

Why guidance wording has operational consequences

When the legal boundary is unclear, firms have to decide before the regulator settles every interpretive point. They may pause a product launch, adjust their operating model, seek specialist advice, or apply for authorization. Each option comes with costs, and companies can take a conservative position simply because the downside of being wrong is significant.

That's also why the FCA's examples and definitions matter. Useful guidance should help firms distinguish ordinary technical work from conduct that looks like operating or controlling a regulated service. It should also show how exclusions work in common scenarios, rather than leaving firms to infer the answer from broad labels.

CryptoUK is asking for more examples of activities that typically sit outside the perimeter. That won't remove the need to assess specific facts. But it could reduce avoidable uncertainty by showing how the FCA expects the framework to apply to recurring patterns of work.

For the FCA, the trade-off is familiar: guidance should be clear enough to be useful without becoming a substitute for legislation or creating loopholes. CryptoUK argues that clarity should track the law - especially where an expansive reading could affect whether people can build or maintain decentralized software in the UK.

What else is at stake for stablecoins and UK firms?

CryptoUK's response also covers stablecoin treatment and the competitive position of UK businesses. It asks the FCA to publish a public record of stablecoins recognized under the UK regime, and to clarify how those stablecoins differ from electronic money. At bottom, these requests come down to an operational need: businesses need to know which assets qualify and what regulatory treatment applies before they build payment or settlement processes around them.

A public register could make those details easier to verify, and clearer definitions could prevent firms from treating distinct legal categories as if they were interchangeable. The underlying material doesn't establish that every stablecoin will qualify for recognition, or that recognition will remove all regulatory obligations. It's a request for a more usable way to identify which assets fall within the relevant UK framework.

CryptoUK also wants the FCA to raise outcomes it says could disadvantage UK firms. It points to UK technical providers that connect users to regulated overseas trading venues and enable payments using stablecoins issued abroad. In its view, these examples show that rules can affect a business beyond the narrow question of whether its core activity needs authorization. Access to markets and the assets used for payments can also shape how a business can operate.

Alignment with other frameworks is a choice, not a shortcut

CryptoUK argues the UK should align with the European Union's Markets in Crypto-Assets framework (MiCA), where appropriate. The qualifier is doing a lot of work here. Alignment may reduce friction for businesses operating across jurisdictions, but copying another framework without thinking through UK legislation and UK market structure can also cause problems.

For firms, the immediate task is not to assume that a UK approach will match the EU's. Instead, firms need to map where customers, services, counterparties, and assets sit, and then work out which rules apply to each part of the operation. If a UK technical provider connects users to an overseas venue, for example, the legal analysis may depend on the provider's role and the relevant jurisdictional rules - not just the venue's location.

A stablecoin used for payments also needs to be assessed under the relevant regime, not treated as a generic token. The FCA's proposed guidance, the underlying legislation, and any other rules that touch payment or electronic-money activity should be considered as separate pieces of the overall picture.

How should crypto firms assess the regulatory boundary?

While the FCA consultation is still unresolved, firms can make their analysis more useful by focusing on what the business actually does, rather than leaning on broad labels like "DeFi protocol," "developer," or "technical provider." Those terms can describe a product, but they don't, by themselves, answer the regulatory question.

CryptoUK's approach can start with four questions:

  1. What service does the user receive? Describe the actual function, including what happens when a customer initiates an action.
  2. Who performs each function? Separate software contributors, governance participants, interface providers, operators, and commercial entities.
  3. Who has practical control? Identify who can change the service, manage access, set terms, or make decisions that affect users.
  4. Which legal boundary or exclusion is being relied on? Identify the relevant provision and note where the draft guidance or legislation remains uncertain.

A working checklist for teams

Before relying on a technical-services exclusion (or any other exclusion), firms should document:

  • The service and the user activity it supports.
  • The exact technical, governance, and operational roles carried out by each person or entity.
  • Who can alter the service or influence its availability and terms.
  • Whether the UK connection is based on users, business operations, development, governance, or another factor.
  • Which exclusion is relevant, and what conditions the draft guidance attaches to it.
  • Any unresolved questions that could affect an authorization application, launch plan, or relationship with a regulated firm.

This method has limits. A written description can't resolve an ambiguous legal test, and decentralized governance can be hard to characterize in practice. When the outcome could affect authorization or a major business decision, teams should get advice grounded in their actual design and conduct. The checklist is meant to make that advice more precise, not to replace it.

Conclusion

CryptoUK's intervention is about a practical boundary: regulation should focus on carrying on or controlling a financial service - not automatically on contributing code or participating in governance. At the same time, decentralization isn't a magic phrase that resolves regulatory questions. What matters is how the service works, who performs its functions, and who has effective control.

For the FCA, the test is whether the final guidance draws that line clearly while staying within the legislation. For UK crypto firms, the sensible response is to map activities and responsibilities now, identify assumptions that depend on wording that isn't settled yet, and avoid treating either the draft or a project label as a definitive legal answer.

Frequently Asked Questions

CryptoUK says software development, maintenance, security work and governance participation should not by themselves establish that someone carries on a regulated activity. That is the trade group’s position on the draft guidance, not a universal exemption. The actual role, service and degree of control remain relevant to the assessment.
The regulatory perimeter is the boundary between activities that fall within the UK crypto regime and require authorization and those that do not. FCA consultation paper CP26/36 proposes guidance explaining that boundary and amending the Perimeter Guidance Manual to reflect changes to the legislation.
CryptoUK broadly supports the proposed guidance but says some parts may go beyond the legislation. It wants clearer treatment of UK connections, conditions attached to certain exclusions and indicators for technical services. It also asks for more examples of activities that typically fall outside the perimeter.
The UK regime is due to take effect on October 25, 2027. The FCA aims to publish its final perimeter guidance in January 2027. The consultation draft is therefore not the final guidance, and firms should distinguish proposed interpretations from the rules that ultimately apply.

Related articles