533d6baf-5

ConfirmedRegulation & Policy625 words3 min decode

UK FCA Cryptoasset Guidance Draws Call for Objective Control Test

Andreessen Horowitz's Nov. 18 letter to the FCA seeks objective tests for decentralization and noncustodial software, answering two draft UK crypto guides.

Andreessen Horowitz Recommends Clearer Tests for UK Crypto Rules
WitnessAndreessen Horowitz Recommends Clearer Tests for UK Crypto Rulesstempow / pixabay

Outputs

  1. Andreessen Horowitz submitted a letter to the FCA dated Nov. 18 responding to two proposed UK crypto regulatory guides.

  2. The letter asks the FCA to use objective criteria to assess control over decentralized protocols.

  3. The letter asks when noncustodial software connecting users with third-party services falls outside the proposed licensing regime.

  4. The perimeter guidance covers the scope of a planned licensing regime and includes an exclusion for technical service providers.

  5. The FCA's separate decentralized finance guidance addresses operational resilience and financial crime risks.

A venture capital firm asked the Financial Conduct Authority on Nov. 18 to set objective tests for judging control over decentralized protocols, in a letter answering two proposed UK crypto regulatory guides. Andreessen Horowitz's submission covers the cryptoasset regulatory perimeter and the FCA's separate decentralized finance guidance, both still in draft form.

The perimeter guidance defines which activities and providers fall inside a planned licensing regime, and it includes an exclusion for technical service providers. The firm's recommendation concentrates on two points: what counts as control over a decentralized protocol, and when noncustodial software that connects users with third-party services falls outside the licensing perimeter altogether.

What does the regulatory perimeter decide?

A perimeter test sets who needs a license before any product ships, and it separates operating firms from software developers. Where control is judged by undefined discretion, two teams can read the same guidance and reach opposite conclusions about one architecture.

If a noncustodial provider cannot point to a bright line for exclusion, the same asymmetry follows, and product timelines absorb the cost of resolving the question later. Objective criteria turn a compliance question into an engineering checklist; open-ended tests push the decision into legal argument after launch.

What Andreessen Horowitz asked for

  • Apply "objective criteria" to assess control over decentralized protocols rather than case-by-case judgment.
  • Clarify when noncustodial software connecting users with third-party services falls outside the proposed licensing regime.
  • Give the technical service provider exclusion a workable edge: the perimeter guidance already excludes those providers, and the letter's noncustodial software recommendation sits at that boundary.

What the DeFi guidance covers

The second document in the response is the FCA's decentralized finance guidance, which addresses operational resilience and financial crime risks. Operational resilience asks a covered entity to show how it keeps operating when systems fail; financial-crime rules ask it to show how it detects and reports suspicious activity.

Both are process obligations for firms already inside the perimeter, and neither answers the question of who enters the perimeter at all. The recommendations reported for the letter center on the perimeter guide, and the decentralized finance guidance enters the response as a distinct second consultation.

Neither document, as described, carries a compliance date, so firms reading the drafts have no timetable from this text alone. Both are proposals, and the Nov. 18 letter is an answer at that proposal stage rather than a response to a final rule.

Why the perimeter exclusion matters most

For developers, the practical stakes sit in the exclusion for technical service providers. A software provider that connects users to third-party services can hold a different legal position from an operating firm, and the draft wording decides which side of the licensing line it occupies.

Read as a drafting request, Andreessen Horowitz's recommendation concerns the edge of the existing exclusion rather than its replacement, and objectivity matters most there because the same code can be characterized either way. For a business model built on supplying software rather than holding customer assets, that classification travels straight into licensing cost, customer contracting and how the firm explains its own regulatory status to counterparties.

Both documents are guidance rather than the licensing regime itself, which puts the decision at the drafting stage. A definition inserted now travels into every application that follows it. A definition left open becomes the first point of dispute in the first supervisory conversation that touches it.

The next revision of the two drafts will show whether the FCA turns the call for objective criteria into a test developers can apply, or leaves providers reading an exclusion that stays hard to apply. On the Nov. 18 letter, the perimeter remains drafted, contested and unfixed.

via tokenpost.com (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,509 articles