Blockchain networks can operate without a central administrator. But the enterprises that provide mining, validation, and supporting services for these networks operate through identifiable legal entities, contractual relationships, and management structures. This opens a gap for regulation: even if the underlying infrastructure is decentralized, the commercial activities built around it can still be organized into corporate entities that regulators can license and supervise.
Abu Dhabi Global Market (ADGM) is building a framework on top of this distinction. Its Registration Authority (RA) published on October 28 the "Guidance on Crypto Mining Activities in and from ADGM," establishing a commercial licensing pathway for crypto mining under activity code 7230, while clarifying when activities involving third-party digital assets may fall within the regulatory scope of the Financial Services Regulatory Authority (FSRA).
But what truly deserves attention is not the "mining license" itself, but the accountability model this guidance seeks to establish: connecting a company's legal identity with its on-chain activities, and extending regulatory scrutiny to international operations managed from ADGM.
This raises a larger question for crypto regulation: if regulators cannot effectively supervise a decentralized network as a single entity, can they achieve regulatory objectives by focusing on the enterprises that organize commercial activities around that network? ADGM offers one answer, and its limitations are as important as its ambitions.
The regulatory boundary is not just about "mining"
There is a distinction in the guidance that is easy to overlook: participating in blockchain consensus does not equal providing financial services.
Under ADGM's approach, independent mining or validation for one's own account falls within the commercial licensing regime and does not in itself constitute a regulated financial activity. But when an operator holds, controls, or exercises discretion over third-party digital assets, this position may change.
This distinction is critical because two enterprises may do technically similar things while bearing completely different responsibilities. An operator validating transactions for its own account uses its own capital and receives its own rewards; whereas an enterprise that pools client assets, manages validator private keys on behalf of clients, or exercises discretion over third-party holdings introduces another layer of risk—it is no longer merely operating infrastructure, but bearing responsibility for entrusted assets.
ADGM clarifies the circumstances in which such activities may require a separate Financial Services Permission, including custody or management of third-party assets. The guidance also distinguishes between two types of arrangements: non-custodial technical services that do not possess or control client assets, and other arrangements that may fall within FSRA's regulatory scope.
Its regulatory logic is noteworthy: it does not lump all activities related to blockchain validation into a single category, but rather differentiates based on what the enterprise actually does and whose assets are involved. This preserves a commercial pathway for infrastructure operators while avoiding automatically subjecting every participant in a consensus mechanism to financial services regulation; at the same time, it makes the boundary between "infrastructure" and "financial intermediation" a core compliance issue that enterprises with evolving business models must confront.
Difficulties often arise where the boundary is less clear: for operators that combine technical infrastructure with pooled fund arrangements, asset management, or client-facing services, self-identifying as a "miner" or "staking service provider" cannot determine their regulatory status—what matters is the substance of their activities.
The broader lesson is: the regulatory boundary of blockchain infrastructure may be determined not only by the technology itself, but also by the business models built around it.
Disclosing wallet addresses enhances visibility, but does not tell the whole story
The treatment of on-chain reward flows reflects a second dimension of this approach.
The guidance requires licensed mining entities to disclose the blockchain wallet addresses and smart contract addresses they own or control and use to receive or manage mining and validation rewards. The Registration Authority may also use third-party tools to monitor these disclosed addresses for regulatory purposes; information provided under disclosure requirements will be treated as confidential regulatory information and not made public.
Thus, a connection is established between the company's legal identity and its on-chain activities: ownership records identify who ultimately owns or controls the enterprise, while disclosed reward-flow addresses allow regulators to locate specific portions of its digital asset activities.
The significance is not that "on-chain addresses make enterprises instantly transparent"—but that it provides regulators with another information channel for assessing the activities of an identifiable entity.
But there is an important limitation: a disclosed address in itself cannot establish the full commercial purpose of every transaction, identify all parties involved, or explain the relationships among entities in a complex business. The value of the information depends on whether it can be corroborated with corporate registration records and other regulatory evidence.
The guidance effectively assumes the necessity of maintaining this connection: it requires enterprises to notify when reward-flow arrangements undergo material or structural changes, such as changes in custody architecture or service providers; at the same time, it distinguishes such changes from routine address rotation for security purposes. This distinction is telling—the framework does not simply require enterprises to submit a static wallet list, but to understand the overall arrangement of how rewards are received and managed, while permitting routine operational adjustments that do not materially change that arrangement.
For operators, this means on-chain records and corporate compliance cannot be managed as two separate functions: enterprises need to know which addresses they own or control, how these addresses relate to licensed activities, and when a "material change" occurs. For regulators, the challenge is to use this information proportionately—greater visibility aids supervision but does not replace the need to interpret transactions in context.
The regulatory reach challenge posed by global headquarters
When enterprises operate across borders, the boundaries of corporate accountability become more apparent.
A mining entity registered in ADGM may manage facilities, subsidiaries, contractors, and personnel across multiple jurisdictions. Its headquarters can oversee the overall business but may not control every operational decision at every site.
The guidance directly addresses this structure: the Registration Authority may require information on overseas operations, including location, scale of operations, ownership structure, subsidiaries, and key management personnel, and encourages due diligence on overseas jurisdictions and business partners proportionate to their risk. Crucially, the guidance defines "reasonable supervision" as governance-level accountability rather than day-to-day operational control over overseas activities—headquarters should promote appropriate governance and compliance while acknowledging that overseas operations remain subject to applicable local laws and regulations.
This is a meaningful distinction: regulators holding an ADGM-registered headquarters accountable does not necessarily require that entity to directly operate every overseas facility, but rather can assess whether the headquarters understands its international footprint, has appropriate reporting and accountability structures, and has taken reasonable steps to manage relevant risks.
The Registration Authority may also require supplementary documents, periodic reports, communication with overseas regulatory counterparts, and inspections at the locations where the entity operates (including overseas). Licensed entities should promptly report material compliance violations or significant regulatory actions arising in their international operations.
But this model also raises a practical question: when headquarters does not exercise day-to-day control over certain operations, how should responsibility be assessed? The guidance establishes the principle of "reasonable supervision," and how this principle is implemented depends on the structure, complexity, and risk profile of individual enterprises—an enterprise with wholly-owned subsidiaries faces different supervisory challenges than one that relies heavily on independent partners and contractors.
This is not a weakness unique to ADGM, but a structural challenge faced by any jurisdiction that seeks to regulate internationally active enterprises through locally registered entities. The regulatory task is to establish meaningful accountability rather than assuming that "headquarters control" equals "direct operational control." For mining enterprises, this means that even if physical activities occur elsewhere, their international footprint may still be relevant to their ADGM regulatory relationship.
The real test: whether the boundary holds as enterprises evolve
ADGM's approach relies on two distinctions working together: the distinction between commercial mining and regulated financial services, and the distinction between headquarters accountability and direct control over global operations. Both are clear in principle, but become tricky to apply as enterprises expand, layer services, change custody arrangements, and develop increasingly complex international structures.
A company may initially validate the network only for its own account, then later introduce services involving third-party assets; a mining enterprise may establish its headquarters in ADGM while relying on facilities and contractors elsewhere. In these cases, the initial structure is no longer sufficient to describe the full range of risks and responsibilities.
This is precisely where the significance of the guidance's risk-based approach lies: ADGM states that supervisory intensity may vary based on factors such as the scale of operations and whether services are provided to third parties; the framework also lists cybersecurity, physical security, operational resilience, record-keeping, and applicable anti-financial crime obligations as relevant considerations.
The guidance also clarifies its own status: it is non-binding indicative guidance that must be read together with applicable legislation, does not replace relevant laws, and does not provide definitive answers for every business model. For activities that are ostensibly "incidental," the Registration Authority retains discretion to determine whether they substantively constitute commercial mining requiring a license.
These qualifications are important because this document should not be understood as covering every individual who operates a validation node or every enterprise that interacts with a blockchain. Small-scale individual mining is generally outside its scope, as are certain incidental node or validator operations that meet established conditions.
What ADGM has established is an initial framework, not the elimination of all classification issues. Its planned broader framework and further consultation will provide opportunities to refine this approach as the industry and business models evolve.
The bigger picture: regulating organizations, not protocols
ADGM's guidance points toward a pragmatic approach to regulating blockchain infrastructure: focus on the identifiable organization carrying out the activity, determine whether it handles its own assets or others' assets, and assess how it manages the risks that accompany the broader business.
This does not mean that decentralized networks themselves thereby become fully transparent or controllable, nor that regulating one company can answer all questions about activity on a global blockchain. What it does is: establish a framework for regulating commercial entities—at the level where legal obligations, management decisions, and operational arrangements can be assessed.
The distinction between own-account activity and third-party asset services is at the core of this framework; so is connecting corporate registration records with on-chain reward flows, and assessing international business through governance rather than assumptions of direct control.
The next question is how these principles land in practice. Regulatory certainty depends not only on whether there is a license category, but also on whether enterprises can determine which requirements apply to them, and whether regulatory expectations can remain proportionate to their activities.
For ADGM, the opportunity lies in developing a framework that can accommodate the diversity of blockchain infrastructure enterprises while maintaining a clear distinction between commercial activity and regulated financial services; for operators, the challenge lies in building organizations that can explain what they do, whose assets they handle, and how their activities are governed.
The core insight is that decentralization has not eliminated the corporate structures through which this industry operates. These structures provide regulators with a handle for accountability, but the reach of that accountability has its limits. How ADGM balances these two realities will have far more profound implications than whether there is a mining license.
