BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
BTC/USD $68,420 +2.8%
ETH/USD $3,540 +1.4%
SOL/USD $142.80 -0.6%
BNB/USD $605.20 +0.9%
XRP/USD $0.62 -1.2%
DOGE/USD $0.18 +5.4%
Policy

CryptoUK Urges FCA to Clarify DeFi Developer Regulation

CryptoUK, the trade association representing more than 150 crypto companies in the United Kingdom, has formally called on the Financial Conduct Authority to issue explicit guidance stating th

AnonymousCryptoCompass newsroom
November 21, 2026
10 min read
NEWS
CryptoUK Urges FCA to Clarify DeFi Developer Regulation
CryptoCompass editorial visual for policy coverage.

CryptoUK, the trade association representing more than 150 crypto companies in the United Kingdom, has formally called on the Financial Conduct Authority to issue explicit guidance stating that writing, maintaining, or securing decentralised finance protocol code does not, by itself, constitute a regulated activity, pushing back against what the industry sees as a dangerously ambiguous default assumption embedded in the regulator's draft perimeter framework.

According to Decrypt's reporting on the submission, it was filed on November 18, 2026, the final day of the consultation window for FCA Consultation Paper CP26/36 on cryptoasset perimeter guidance, and published the following day. It was prepared in collaboration with law firm CMS and signed by Nick Brooks, CryptoUK's policy director. For related coverage, see Crypto Staking Dashboard Estimates Q4 2026: Rates and Risks Before Year-End.

CryptoUK asks the FCA to clarify the default treatment of DeFi developers

The core of CryptoUK's argument is a request for explicit carve-out language in the FCA's forthcoming perimeter guidance. As stated in the submission, "software development, maintenance, security work and participation in decentralised governance should not, by themselves, establish that a person carries on a regulated activity." That framing targets a specific gap: the draft guidance does not distinguish clearly between contributors who write open-source protocol code and parties who operate a financial service using that code. Context on this theme: HYPE Holding Near Breakeven: Asia Session Roundup.

CryptoUK argued that authorisation requirements should attach only to the entity that effectively controls the financial service, not to anyone whose technical labour contributed to the protocol's existence. The distinction matters because UK-based open-source contributors, security auditors, and governance participants could otherwise be caught within the FCA's regulatory perimeter solely on the basis of technical involvement, without exercising any discretionary control over how end users interact with a protocol. More on this in Report: Bitcoin Core Fixes Node Message Processing Vulnerability.

Geographic nexus as a contested boundary

The submission also challenged a specific provision in the draft guidance that would use the location of protocol development as the basis for establishing a UK regulatory nexus, according to Decrypt's account of the filing. CryptoUK argued this approach exceeds the scope of the underlying legislation and could expose UK-domiciled open-source contributors to authorisation obligations that the FSMA 2000 framework was not designed to impose on them. This geographic test is distinct from the question of who controls a service, and CryptoUK characterised it as an overreach relative to what Parliament enacted.

Why a default regulatory assumption matters for DeFi development

The FCA's stated position in CP26/36 is that "the perimeter is technology neutral: the same statutory tests apply however decentralised a business model is," according to legal analysis published by Lawbeam reviewing the consultation paper. That principle, applied without a developer-specific carve-out, creates a scenario in which the same statutory test that governs a centralised exchange could theoretically be applied to a pseudonymous contributor who deployed a smart contract from a London address.

The practical concern for builders is compliance uncertainty at the point of contribution rather than at the point of operation. A developer who writes and deploys an automated market maker contract cannot easily determine, under the current draft, whether the act of deployment triggers authorisation requirements. That ambiguity, CryptoUK contends, is sufficient to redirect engineering talent and protocol development activity away from UK jurisdictions before the full crypto regime takes effect on October 25, 2027, per the Lawbeam analysis confirming that timeline.

The difference between writing code and operating a service

According to Decrypt's reporting and Lawbeam's legal analysis, CryptoUK's requested distinction is between writing or publishing code and operating a service that facilitates financial transactions for end users. Under CryptoUK's proposed framework, a developer who publishes a DeFi protocol under an open-source licence, then steps back from operational control, would not meet the threshold of "effectively controlling" the resulting financial service. The question of whether a party exercises effective control would then require case-by-case analysis, rather than being resolved by default against the developer.

This is not a blanket exemption argument. According to Decrypt's account of the submission, CryptoUK's position is that technical contribution alone is insufficient to establish regulated status, while leaving open the possibility that a developer who also acts as an operator, administrator, or governance controller with meaningful discretionary power could still be caught. In CryptoUK's framing, the distinction is between contribution and control, not between DeFi and everything else.

What the request could mean for the UK crypto sector

The UK's full cryptoasset regulatory regime is scheduled to come into force on October 25, 2027, with authorisation applications having opened on September 30, 2026 and the application window closing on February 28, 2027, according to the Lawbeam legal analysis of CP26/36. The FCA is expected to publish its final perimeter guidance in January 2027, according to a single source reported by Decrypt; that timeline could not be verified directly from the FCA's website due to access restrictions, but it is consistent with the broader regulatory schedule. Depending on the eventual publication date, the interval before the close of the authorisation window could leave firms limited time to adjust compliance strategies after the developer-liability question is resolved.

For UK-based DeFi builders, the stakes in January's guidance are concrete. A technology-neutral perimeter rule without developer carve-out language would require any UK-domiciled individual or entity with meaningful DeFi protocol involvement to assess whether they carry on a regulated activity, seek legal advice, and potentially apply for authorisation or restructure their involvement before October 2027. The scale of Ethereum's DeFi ecosystem provides broader context for the activity subject to this regulatory question, and the perimeter decision carries significant implications for where protocol development is domiciled globally.

Case-by-case scrutiny remains the floor

Even if the FCA adopts CryptoUK's recommended language, the guidance would not create a blanket safe harbour for all DeFi participants. Any party who exercises effective control over a financial service, whether through admin keys, protocol upgradability, governance weighting, or fee extraction mechanisms, would still be subject to the same statutory tests that apply to centralised operators. The clarification CryptoUK seeks would narrow the pool of parties facing default authorisation exposure, not eliminate regulatory oversight of DeFi entirely. The FCA's technology-neutral position, as confirmed through Lawbeam's review of the CP26/36 text, signals the regulator intends to look through the technical architecture to identify functional control rather than granting categorical exemptions by asset type or delivery mechanism.

CryptoUK's submission also addressed two adjacent issues: a call for the FCA to publish a public register of UK-approved stablecoins, and a request that the regulator flag to HM Treasury any rules that place UK firms at a competitive disadvantage relative to EU counterparts operating under MiCA, according to Decrypt's account of the filing. The stablecoin register request reflects the same perimeter concern applied to issuers rather than developers, while the MiCA alignment ask signals that CryptoUK views the UK-EU regulatory divergence as a live competitiveness risk as the October 2027 go-live approaches. The UK has been working to position itself as a crypto-friendly jurisdiction, and similar regulatory clarity efforts are emerging elsewhere; Hong Kong's recent proposal to criminalise misrepresentation in virtual asset licence applications reflects how jurisdictions are simultaneously tightening enforcement integrity while clarifying perimeter boundaries for builders.

What to watch next from the FCA and CryptoUK

The FCA's January 2027 final guidance publication is the nearest concrete milestone. If the guidance adopts language distinguishing technical contribution from operational control, it would validate CryptoUK's core argument and provide DeFi developers with a clearer compliance baseline ahead of the February 28, 2027 authorisation application deadline. If the final guidance retains a technology-neutral test without developer-specific carve-outs, firms will face the authorisation window without clarity on whether UK-domiciled protocol contributors require individual authorisation.

Further detail from CryptoUK on the precise regulatory language it has proposed is also worth monitoring. The submission's reference to "effective control" as the threshold concept suggests the trade association may publish model guidance language or engage directly with the FCA during the post-consultation review period. Any FCA acknowledgement that it is considering the developer-operator distinction as a structuring principle for its final guidance would signal a meaningful shift from the current technology-neutral framing. Market participants tracking the broader macro environment amid a period of elevated uncertainty in crypto markets will find the January guidance publication a key regulatory catalyst with direct implications for UK-based DeFi protocol activity in 2027.

FAQ

What is CryptoUK asking the FCA to clarify?

CryptoUK is asking the FCA to include explicit language in its final perimeter guidance stating that software development, code maintenance, security work, and participation in decentralised governance do not, by themselves, constitute carrying on a regulated activity in the UK. The trade association also objects to a draft provision that would use the geographic location of protocol development as the basis for a UK regulatory nexus, arguing that this approach exceeds the scope of the FSMA 2000 framework as amended, according to Decrypt's reporting on the CP26/36 submission.

Does the request mean DeFi developers are exempt from UK regulation?

No. CryptoUK's position is that technical contribution alone should not trigger regulated status by default, not that DeFi participants are categorically exempt. The submission argues that authorisation requirements should apply to whoever effectively controls a financial service. A developer who also exercises operational control, holds admin keys, or manages upgradeable contracts with meaningful discretionary power could still be subject to the FCA's statutory tests. The requested clarification narrows the default assumption, it does not create a blanket exemption.

Why is the distinction between developers and operators important?

Without a clear distinction, any UK-domiciled person who contributes code to a DeFi protocol could face an obligation to assess whether they carry on a regulated activity, potentially requiring legal advice, authorisation, or restructured involvement before the UK crypto regime takes effect on October 25, 2027. The authorisation application window closes on February 28, 2027, per the Lawbeam analysis, giving developers limited time to act once final guidance is published in January 2027. Regulatory ambiguity at the point of contribution, rather than operation, creates a chilling effect on where protocol development is domiciled, which is the competitiveness concern underlying CryptoUK's submission.

Editorial credits

SP Sophia Panel Writer · Coincu HN Haruto Nakamura Editor · Coincu Monitors published articles around the clock and can correct or withdraw them.

Checked by Coincu QC Team before publishing on November 21, 2026 for headline accuracy, metadata, commercial disclosure and authorship claims: our AI review system checks every article before it goes live, and our editor monitors it after publication. Report an error.

Coincu uses AI for research, drafting and review. Our editorial team is responsible for every article and corrects or withdraws articles when needed. How we review.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.

The post CryptoUK Urges FCA to Clarify DeFi Developer Regulation was initially published on Coincu.