1. A filing on UK crypto regulation and public blockchains
The Hyperliquid Policy Center (HPC) asked the United Kingdom's Financial Conduct Authority (FCA) on Wednesday, November 18, 2026, to treat public blockchains as neutral infrastructure. In responses to two consultations shaping UK crypto regulation, the group argued that validators and software developers who do not control financial products built on those networks should not carry regulatory obligations.
The submissions arrived on the final day both consultations were open for comment. They address a question that sits at the center of every attempt to write rules for decentralized systems: when a financial service runs on a network that no single company operates, who is the regulator supposed to hold accountable?
HPC's answer is that responsibility should follow control. In its view, compliance duties belong to regulated firms that offer financial services and to individuals who hold unilateral control over regulated activities. The people and organizations that keep the underlying network running, without directing how financial products on it behave, should sit outside the perimeter.
2. Who would be exempt under the proposal?
Validators and developers are the two groups HPC wants kept out of scope. The organization said validators that verify transactions, and developers who maintain blockchain software, should not be regarded as carrying out regulated activities simply because their work supports a public network.
Validators are the participants that check transactions and add them to a blockchain's record, typically earning fees for doing so. Developers write and update the software that those validators and other users run. Neither role, on HPC's account, involves deciding which financial products are offered to customers or on what terms.
The qualifier in that position is important. HPC is not asking for a blanket exemption for anyone who happens to hold one of these roles. Its argument covers those who support a network without controlling the financial products that run on it. Someone who validates transactions and also holds unilateral control over a regulated activity would, under the group's own logic, still fall within the rules because of that control.
To make the point, the group drew a comparison with the public internet. Network operators and service providers that carry internet traffic are not automatically placed under the same financial rules as the businesses that use their infrastructure to reach customers. A bank that offers online accounts is regulated as a bank; the companies that route its data are not. HPC argued that blockchains should be understood in the same layered way, with financial regulation attaching to the service and not to the pipes beneath it.
3. The two FCA consultations
HPC's responses were directed at a pair of papers the regulator had put out for comment. The first, CP26/36, concerns the scope of regulated cryptoasset activities and the exclusions available to providers of technical services. It is the document that determines where the boundary of regulation is drawn, and therefore which actors need to concern themselves with FCA rules at all.
The second, GC26/7, deals with operational resilience and financial crime requirements for firms that use decentralized finance (DeFi) infrastructure. Where the first paper asks who is regulated, the second asks what regulated firms must do when part of their service depends on protocols and networks they do not run themselves.
Both consultations closed on November 18. They form part of the preparation for the UK's expanded crypto framework, which takes effect on October 25, 2027. From that date, firms carrying out newly regulated cryptoasset activities will need authorization from the FCA. The guidance the regulator settles on before then will shape how businesses structure themselves in advance of the deadline, which is why interest groups have been keen to register their positions now.
4. Seven clarifications and a test for decentralization
The group did not present itself as an opponent of the regulator's general direction. HPC said it supports the technology-neutral approach the FCA has taken, under which rules are meant to apply to activities regardless of the systems used to carry them out. What it requested was seven clarifications intended to make sure obligations land on the parties running regulated activities and not on the networks underneath them.
One of the most consequential concerns how a regulator should decide whether a blockchain is decentralized in the first place. HPC proposed a test built around a single question: can any one individual unilaterally control how the network's rules apply to users? If no one person holds that power, the network would qualify as decentralized under the group's approach.
HPC also asked that a network not forfeit that classification for reasons it considers beside the point. Developers continuing to maintain the software should not, in its view, cause a blockchain to be treated as centrally controlled. Nor should the fact that validators earn fees for securing transactions. Both are ordinary features of how public networks operate, and the group's concern is that treating either as evidence of control would leave very few networks able to meet the standard.
The distinction matters because classification drives everything that follows. A network judged to be decentralized is infrastructure; one judged to be controlled by identifiable people may bring those people within the scope of regulation. A test based on unilateral control sets a specific threshold, and HPC is asking the regulator to adopt it explicitly instead of leaving the matter to case-by-case interpretation.
5. Where HPC says responsibility should sit
Exempting infrastructure providers does not, in the group's framing, mean that nobody is accountable. HPC said regulated firms that use public blockchain infrastructure should remain responsible for customer protection, for operational resilience and for meeting financial crime requirements. A firm that builds a service on a public network would carry the same duties as one using any other technology.
The group went further on what should happen when those duties cannot be met. If a financial product is unable to satisfy the applicable rules, HPC said the product should be excluded from the UK market. The alternative it rejects is shifting the obligations onto infrastructure providers that have no means of fulfilling them. A validator processing transactions cannot, for example, carry out the customer checks expected of a firm that deals with clients directly.
This is the practical core of the proposal. It accepts that some products may not be available to UK customers and treats that outcome as preferable to a regime that places requirements on parties structurally incapable of complying.
6. Blockchain records as a compliance tool
A further request turns the technology's characteristics into an argument for regulatory recognition. HPC asked the FCA to acknowledge that blockchain transaction records could serve as one way for financial institutions to meet transparency and recordkeeping requirements.
Public blockchains keep a shared, time-ordered record of every transaction processed on the network. Financial firms are required to maintain reliable records of their activity and to make certain information available to supervisors. HPC's suggestion is that, where the relevant activity takes place on a public network, the network's own ledger could help satisfy those obligations.
The request is framed as recognition of a possibility, not as a demand that on-chain data replace existing recordkeeping. It fits the broader shape of the filing, which leaves regulated firms carrying their duties in full while asking the regulator to accept that public infrastructure can be part of how those duties are discharged. It also complements the group's support for technology neutrality: if the rules do not favor one system over another, a record held on a public ledger should be capable of counting toward compliance in the same way as a record held in a firm's own database.
7. The same argument in Brussels
The UK filing repeats a position the group has already advanced elsewhere. HPC made a similar case in its response to the European Commission's review of the Markets in Crypto-Assets Regulation (MiCA), the European Union's framework for the sector.
There, too, it argued that oversight should depend on the functions market participants perform and not on the technology they use. Applied consistently, that principle leads to the conclusions set out in the UK submissions: a firm offering a financial service is regulated because of the service, and a party that merely operates or maintains a network is not regulated because of the network.
Pressing the same line with regulators in more than one jurisdiction suggests the group is seeking a common standard for how decentralized infrastructure is treated, so that the same network is not classified one way in London and another way in the European Union.
8. What happens next
With the comment period over, the FCA will review the feedback it has received from industry before issuing final guidance. HPC's submissions are one set of responses among those the regulator will weigh, and nothing in the filings indicates how the FCA views the specific requests.
The fixed point on the calendar is October 25, 2027, when the expanded framework comes into force and FCA authorization becomes mandatory for firms conducting the newly regulated cryptoasset activities. Whether validators and developers are expressly placed outside that requirement, and whether the regulator adopts a control-based test for decentralization, will be settled in the final text.
For firms building on public networks, the outcome will determine how much of the compliance burden rests with them alone. For those who run or maintain the networks themselves, it will determine whether UK rules apply to them at all.
