Skip to content

Getting the UK’s DeFi Perimeter Right

Aave Labs

Aave Labs

•

Aave Labs' response to the FCA's consultations on its cryptoasset Perimeter Guidance (PERG, CP26/36) and its DeFi guidance consultation (GC26/7)

The UK is finalising one of the most consequential pieces of its new cryptoasset regime: the FCA's Perimeter Guidance Manual (PERG), which will tell developers, interface providers and regulated firms where the regulatory perimeter sits for decentralised finance. Alongside it, the FCA has consulted on new guidance for regulated firms that use or interact with DeFi. Today Aave Labs submitted a single response to both: CP26/36 on cryptoasset perimeter guidance, and GC26/7, the FCA's DeFi guidance consultation. You can read our full response here.

Our message is simple. The features that make DeFi safer should not be the features that bring it within the perimeter.

Two consultations, pulling in opposite directions

The FCA's two papers approach DeFi from different angles. The DeFi guidance consultation (GC26/7) asks how regulated firms should manage the risks of using DeFi, and rightly encourages them to rely on protocols that are maintained, monitored and risk-managed, and to screen out illicit activity. The perimeter guidance consultation (CP26/36) asks who needs to be authorised. As drafted, it treats those same features (ongoing maintenance, risk management and screening) as signs of centralisation or discretion that can bring a protocol or interface inside the perimeter.

Left unresolved, that tension would penalise the safest infrastructure and the most protective interfaces. It would also push UK users towards offshore services that offer fewer protections.

Why this matters: DeFi is becoming market infrastructure

This is not only about crypto trading. As financial institutions tokenise assets, the real change is not that tokenised securities can be listed and traded onchain. It is that they can be used as collateral, moved and mobilised in real time for liquidity and treasury management. Decentralised lending protocols like Aave are what make that collateral mobile. The UK's perimeter decisions now will shape whether onchain capital markets are built here or elsewhere.

What we are asking for

1. Give the technical services exclusion practical effect. One of the activities regulated under the UK's new cryptoasset regime is "arranging" transactions in cryptoassets. This covers both bringing about a particular transaction and making ongoing arrangements with a view to transactions taking place. The second limb is broad. Read literally, it could capture any software that helps a user transact, including a wallet or interface that simply lets users interact with a blockchain. HM Treasury therefore introduced a technical services exclusion. Technology providers that merely give users access to regulated services or decentralised protocols are not treated as arranging, and so do not need authorisation for that activity. We welcome it. The exclusion applies only to arranging; it does not cover other regulated activities, such as dealing in or safeguarding cryptoassets.

The draft guidance in PERG, however, tells firms what is not a technical service without explaining what is. We ask the FCA to give a positive, functional explanation. A technical service is the means by which a user obtains information from, connects to and interacts with an underlying service or protocol. In practice, that covers informational, presentational, connectivity, transaction-preparation and transaction-processing functions: retrieving and presenting blockchain data, preparing and validating transactions, estimating network fees, and transmitting instructions the user has authorised. These functions should be capable of being technical however sophisticated they are, even where they are provided commercially or involve many steps. The line should fall where a provider stops giving users the means to act and starts acting for them: independently selecting, recommending, directing or otherwise determining material aspects of the user's transaction. That is where substantive intermediation begins.

2. Make the decentralised protocol route workable. Parliament gave interfaces two routes to the exclusion: access to a regulated firm, and access to a decentralised protocol. As drafted, the guidance could treat access to almost any protocol as access to the service of whoever develops, maintains or governs it, which would leave the second route with little practical application. A protocol is technology that runs according to its code. The right question is whether anyone actually provides or operates the service the user accesses: whether someone holds users' assets, takes their orders, sets the terms of their transactions, or decides how those transactions are executed. Developers, token-holder governance, and risk stewards and guardians acting within limits set by that governance should not, of themselves, change the answer: they help keep a protocol safe, but they do not operate it or decide users' transactions.

3. Recognise that safety is not intermediation. Interacting directly with a blockchain is highly technical. Without an interface, users would have to read raw transaction data, contract code and long hexadecimal addresses, and work out network fees themselves. A self-custodial interface does not act on the user's behalf. It helps users understand what they are doing and manage their own assets in a better-informed way, for example by showing estimated network fees, displaying clear transaction details and blocking interaction with known scam assets. These features inform and protect users. They should not be treated as discretion.

The same applies at the protocol level. Mature protocols publish their risk and asset listing frameworks, and use independent risk stewards and narrowly defined guardian functions approved by token-holder governance. Guardians can act quickly in an exploit, an oracle failure or a market dislocation, for example by suspending new deposits and borrowing while users remain free to withdraw and repay. These are exactly the safeguards the FCA's DeFi guidance consultation wants regulated firms to look for. They should count in a protocol's favour, not against it.

4. Keep both routes to DeFi open. Users should be able to reach DeFi directly, through self-custodial interfaces, and through regulated firms. Neither route should be treated as the preferred path. The FCA's new requirements that customer orders be executed only on FCA-authorised venues, and that retail customers only acquire assets admitted to a UK trading platform, could together operate as a de facto prohibition on regulated firms offering DeFi access. The legislation does not require this. We ask the FCA to use its existing powers to provide a proportionate route, consistent with the direction being taken in the EU and the US.

5. Treat payment stablecoins as what they are. Payment stablecoins issued under the US GENIUS Act must be fully backed and redeemable at par. They are fundamentally different from cryptoassets whose value is not referenced to fiat currency. We ask for mutual recognition, so that they are not subject to the financial promotion restrictions designed for those cryptoassets.

6. Fix the timing. Final guidance is expected only after the authorisation application window closes. We welcome the FCA's commitment to forbearance and ask that it be built into the final guidance, so that firms are not penalised for guidance that arrives after they apply.

A constructive path forward

We are grateful for the FCA's open engagement with industry throughout this process, and we share its aim: a clear, proportionate perimeter that protects consumers and market integrity. The UK has an opportunity to set a standard for how open, onchain infrastructure is regulated. Getting the perimeter right, by recognising safety rather than penalising it, is how the UK keeps users, builders and onchain capital markets onshore.

We look forward to continuing the conversation with the FCA, HM Treasury and industry colleagues.


Need help or want to learn more?

Share your questions or feedback and we'll get back to you.