EST · MMXXVI
Home/Practices/DePIN Networks: Legal Counsel for Decentralised Infrastructure Projects
DeFi, Tokenization & Smart-Contract Law

DePIN Networks: Legal Counsel for Decentralised Infrastructure Projects

DePIN Networks: Legal Counsel for Decentralised Infrastructure Projects. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fix

A team builds a decentralised network that rewards node operators for hosting data or providing wireless coverage; tokens accrue to contributors in proportion to work verified on-chain. The question arrives the moment a jurisdiction is chosen for the foundation entity, the moment tokens list on an exchange, and the moment a user in a regulated market connects to the network: does the protocol constitute a regulated service, and does the token meet the definition of a security? For a DePIN (decentralised physical infrastructure network), the legal perimeter turns on how the protocol distributes risk, who holds operational control and whether participants have a reasonable expectation of profit derived predominantly from the efforts of others. The answer is never automatic, and it is never identical across the forty jurisdictions where a global user base and a distributed contributor pool may trigger oversight. This page maps the legal architecture for DePIN networks – the token classification logic, the licensing exposure for contributors and for the entity that publishes the protocol, the data-protection duties that attach when the network handles personal information, and the consumer-facing obligations that apply when individuals pay to access infrastructure delivered by the protocol.

DePIN networks sit at the intersection of three regulated domains: digital-asset law (because tokens mediate contribution and reward), telecommunications or data-services law (because the network delivers connectivity, storage or compute as a service to end users), and consumer-protection law (because individuals often purchase access with tokens or fiat and expect the network to perform). A protocol that rewards storage node operators with tokens falls within the CASP perimeter under MiCA if the issuer is established in the EU and the token is offered to the public; the same protocol may require a payment-service licence in Singapore if the token is classified as a digital payment token, a virtual-asset trading-platform licence in Hong Kong if the token displays features of a security, and registration under the money-transmitter regime in the United States if token redemption involves fiat conversion. Add the physical-infrastructure layer – the relay that routes mobile traffic, the storage array that holds user files, the compute node that executes off-chain workloads – and the regulatory picture includes telecommunications licensing in jurisdictions where wireless spectrum is involved, data-processor registration under the GDPR where European users' data transits the network, and potentially financial-services licensing if the token structure creates an investment contract under the Howey test. The complexity is structural, not incidental, and the cost of mis-reading the classification or the licensing trigger is high: an unregistered securities offering exposes the issuer and its directors to cease-and-desist orders, penalties and personal liability; an unlicensed telecommunications service risks shutdown; a protocol that processes personal data without the required controller or processor registration can face fines calculated as a percentage of global turnover.

What DePIN means in regulatory terms

DePIN is the industry shorthand for protocols that incentivise individuals or entities to provide real-world infrastructure – storage, wireless bandwidth, compute cycles, sensor data, energy distribution – and reward those providers with protocol-native tokens. The defining feature is that infrastructure assets remain owned and operated by distributed contributors, not by a central service provider; the protocol coordinates supply and demand on-chain. From a legal perspective, the concept breaks into three questions: (1) does the token that rewards contributors meet the definition of a security, a payment instrument or a utility asset under the applicable frameworks; (2) does the entity that publishes the protocol require authorisation as a service provider, and if so under which category; (3) do the individual contributors who operate the physical infrastructure require their own licences, registrations or approvals. The third question is often overlooked at design stage, yet it is the trigger for operational friction when a node operator in a regulated jurisdiction receives a letter from a local telecommunications regulator or a data-protection authority demanding an explanation of the service the operator provides and the legal basis under which personal data is processed.

Under MiCA, a token issued to reward infrastructure contribution is analysed first against the asset-referenced token (ART) and e-money token (EMT) definitions; if it is neither, it falls into the residual "crypto-asset" category and the issuer may be subject to whitepaper obligations and, depending on the offering structure, CASP authorisation. A token that confers no right to redemption, no claim on the issuer's reserves and no stabilisation mechanism is typically outside the ART/EMT perimeter, but the obligation to publish a whitepaper applies if the token is offered to the public in the EU, and that whitepaper must disclose the technical specification of the protocol, the emission schedule, the distribution mechanism, the rights conferred by the token and the risks. Under the Payment Services Act in Singapore, a DePIN token is a digital payment token if it is intended to be a medium of exchange or can be exchanged for fiat or another token; if the token meets that definition, any entity facilitating purchase, sale, exchange or custody of the token requires a payment-service provider licence at the appropriate tier. The VARA regime in Dubai treats tokens that represent participation in a profit-sharing or revenue-sharing arrangement as virtual assets subject to the full suite of VARA rulebooks, and any platform that offers those tokens for trading requires a broker-dealer or exchange licence.

The second classification axis is whether the token structure creates an investment contract. Under the framework articulated by the US Supreme Court in SEC v. W.J. Howey Co. (1946) and applied by the SEC to digital assets, an investment contract exists when (1) there is an investment of money, (2) in a common enterprise, (3) with a reasonable expectation of profits, (4) derived from the efforts of others. A DePIN token issued in exchange for staked capital or for pre-operational contribution, with value contingent on the protocol team's development roadmap, network effects and token-listing decisions, presents a high risk of classification as a security. Conversely, a token that rewards only actual, measurable infrastructure work performed after the network is operational, with value tied to service demand rather than promotional efforts, sits further from the security perimeter – though the classification is fact-intensive and the SEC has maintained in enforcement actions that even post-launch distributions can meet the Howey criteria where centralised promotion and network effects dominate. Outside the United States, the Securities and Futures Commission in Hong Kong treats tokens that confer profit participation, voting rights analogous to equity or a share of network revenue as likely falling within the definition of a security; operators of platforms that trade such tokens require a virtual-asset trading-platform licence, and the issuer may require a prospectus under the Securities and Futures Ordinance. The Monetary Authority of Singapore applies a similar substance-over-form approach, and a token that represents a collective investment scheme or a debenture may trigger prospectus and licensing obligations under the Securities and Futures Act.

For a protocol issuer, the classification outcome dictates the licensing path: a token classified as a security typically requires the issuer to operate under a prospectus exemption or to secure dealer registration, depending on the jurisdiction; a token outside the securities perimeter but within the payment-token or crypto-asset definition triggers VASP, CASP or payment-service-provider licensing; a token that is purely a protocol-internal unit of account with no secondary market or fiat gateway may avoid digital-asset licensing altogether but will still be subject to consumer-protection rules, anti-money-laundering obligations where fiat or cross-chain conversion is involved, and the tax treatment of the issuer's revenue and of contributors' rewards. Mis-classification is not a theoretical risk: operators we advise routinely discover post-launch that a jurisdiction in which they have substantial users treats their token as a security, rendering the initial distribution an unregistered offering and blocking compliant on-ramps until the classification is remedied through a restructure, a prospectus filing or a pivot to excluded markets.

Who requires a licence: entity and contributor

The licensing exposure for a DePIN network exists at two levels. The entity level applies to the foundation, company or DAO that publishes the protocol, maintains the code repository, markets the network and, in some models, operates the token treasury or runs the initial validator set. The contributor level applies to the individuals and entities that provide the physical infrastructure: the relay operator, the storage-node host, the wireless access point, the compute provider. The first level is typically addressed early in structuring; the second is often deferred until a regulator in a major market asks for an explanation of why hundreds of unlicensed entities are providing what looks, from the regulator's perspective, like a commercial telecommunications or data-processing service.

At the entity level, the licensing question turns on three activities: (1) issuing and distributing the protocol token, (2) operating or facilitating a secondary market for that token, (3) providing the user-facing service layer (the interface through which individuals purchase access to storage, bandwidth or compute). If the token is classified as a security, the issuer requires registration as a dealer or an offering exemption; if it is a crypto-asset under MiCA, the issuer is subject to whitepaper and transparency obligations and may require a CASP authorisation depending on whether it operates an exchange, custody or advisory service. If the foundation operates a decentralised exchange (DEX) or automated market maker (AMM) for the token, that activity requires licensing in most jurisdictions where the DEX has a nexus – an incorporeal protocol with no identifiable operator may escape direct regulation, but the moment a legal entity publishes the contracts, promotes the DEX or holds admin keys, licensing exposure attaches. Under VARA, operating an exchange for virtual assets requires a broker-dealer or exchange licence, and the activity is construed broadly to include protocols where the entity retains material influence over trading logic. Under the FCA regime in the United Kingdom, operating a facility that brings together buyers and sellers of crypto-assets is a regulated activity requiring authorisation, though the precise scope remains under legislative development at the time of writing. The MAS framework in Singapore treats operating a platform that facilitates exchange of digital payment tokens as a payment service requiring a licence, with no categorical exemption for non-custodial or automated protocols where the operator has control over the matching algorithm or can alter fee structures.

At the contributor level, the licensing trigger depends on the nature of the infrastructure provided. A node operator who stores encrypted user data and is compensated in tokens is providing a data-storage service; whether that service requires a business licence, a data-processor registration or a telecommunications licence varies by jurisdiction. In the European Union, a contributor who processes personal data on behalf of users or the protocol falls within the GDPR definition of a processor and must comply with the obligations in Article 28, including executing a data-processing agreement, implementing appropriate technical and organisational measures, and in certain cases appointing an EU representative. A contributor who operates a wireless relay that routes mobile or internet traffic may require a telecommunications licence or spectrum allocation approval in jurisdictions where radio spectrum is involved; in the United States, operating a wireless network device that transmits on licensed frequencies without FCC authorisation is a violation of the Communications Act, and while unlicensed bands (such as the 900 MHz ISM band) permit operation without individual licensing, commercial operation at scale may still trigger common-carrier or MVNO registration requirements depending on the service model. In the United Arab Emirates, operating telecommunications infrastructure without a licence from the Telecommunications and Digital Government Regulatory Authority is prohibited, and a contributor in a DePIN wireless network who routes commercial traffic falls within that prohibition unless the protocol entity itself holds the relevant licence and the contributor operates as a subcontractor under that licence.

The practical solution in most structures is to place licensing responsibility on the protocol entity where possible, treating individual contributors as subcontractors or service providers to that entity rather than as independent operators of a commercial service. This model requires the protocol entity to hold the relevant licences – telecommunications, payment-service provider, VASP or CASP – and to flow down compliance obligations to contributors through the protocol's terms of service. The alternative – a model in which each contributor is responsible for securing local approvals – scales poorly and is unenforceable in a truly decentralised network, but it is the default legal position in jurisdictions that lack a clear framework for shared or distributed infrastructure. Operators we advise typically adopt a hybrid approach: the foundation entity secures licences in the top-tier jurisdictions where the network has the largest user base and the highest regulatory scrutiny, and the protocol's terms of service explicitly prohibit contributors in certain jurisdictions from participating unless they warrant compliance with local law. The prohibition is imperfect – enforcement relies on IP geolocation and contributor self-certification – but it establishes a defensible compliance posture and reduces the risk that the protocol entity is held vicariously liable for unlicensed operation by contributors in high-enforcement jurisdictions.

Token structure: utility, work, revenue-share

The legal classification of a DePIN token is determined by the rights the token confers, the mechanism by which it is distributed and the expectation of profit among recipients. A token that functions purely as a protocol-internal unit of account – redeemable only for network services and not traded on external markets – sits outside the securities perimeter in most jurisdictions but may still constitute a payment token or stored value requiring licensing where fiat conversion or cross-border transfer is involved. A token that confers a share of protocol revenue, staking yield or fee redistribution presents a higher securities risk, particularly where the token is marketed to passive recipients or distributed in exchange for capital rather than work. The distinction is not binary, and many DePIN tokens exhibit a blend of utility, work-reward and profit-participation features.

Utility tokens – tokens issued solely to access a protocol service, with no secondary market and no expectation of appreciation beyond demand for that service – are the least regulated category in most frameworks. Under MiCA, a utility token that is accepted only by the issuer and for a specific service may fall outside the crypto-asset definition entirely if it qualifies as a limited-network token under Article 2(5), though the exemption is narrow and applies only where the token cannot be exchanged for fiat or other crypto-assets and the issuer does not promote secondary trading. Under the SEC's analysis, a token distributed solely to compensate verifiable work, with value tied to the cost of alternative providers and not to the success of the protocol team's promotional efforts, is less likely to meet the Howey investment-contract test – though the SEC's enforcement positions suggest that any token with a secondary market and a centralised development team may still be scrutinised. For a DePIN network, the challenge is that the utility thesis depends on limiting token liquidity, which conflicts with the goal of attracting capital and contributors by offering tokens that can be freely traded. The result is that most utility-token structures are restructured post-launch to permit secondary trading, at which point they enter the regulated perimeter.

Work tokens – tokens distributed as compensation for measurable infrastructure work, with distribution conditioned on verifiable contribution and with no advance distribution to non-contributors – present a stronger argument for classification outside the securities perimeter. The logic is that the token rewards past work rather than serving as an investment vehicle; value derives from service demand, not from the protocol team's efforts. The Securities and Futures Commission in Hong Kong and the Monetary Authority of Singapore both acknowledge that tokens rewarding actual service provision may fall outside securities classification if the work precedes the reward and the reward is proportionate to the work, but both authorities reserve the right to re-classify where secondary-market trading, staking mechanisms or revenue-sharing features are introduced. Under MiCA, a work token remains a crypto-asset if it is transferable and can be traded, and the issuer is subject to whitepaper and transparency obligations even if the token is not a security; the only categorical exemption is for tokens that meet the limited-network criteria, which few DePIN tokens do because cross-chain interoperability and exchange listings are standard features. The practical implication is that a work-token structure reduces securities risk but does not eliminate digital-asset licensing exposure, and the issuer must still address AML obligations, tax treatment and the cross-border licensing triggers in the jurisdictions where contributors and users are located.

Revenue-share tokens – tokens that entitle holders to a portion of protocol fees, transaction revenue or network earnings – are the highest-risk category. Under the Howey framework, a token that confers profit participation derived from the efforts of the protocol team or network operators is presumptively an investment contract, and the SEC has brought enforcement actions against issuers of such tokens on the basis that they constitute unregistered securities offerings. Under MiCA, a token that confers a financial return tied to protocol performance may be analysed as a transferable security or a structured deposit, triggering prospectus obligations and potentially a full banking licence depending on the structure. Under the SFC regime in Hong Kong, a token that represents an interest in a collective investment scheme – broadly defined to include any arrangement in which participants contribute value and expect profit from a common enterprise – requires a prospectus and a fund-management licence. The risk is not theoretical: exchanges in Singapore, Hong Kong and the EU routinely refuse to list tokens that display revenue-share features unless the issuer can demonstrate an exemption or produce a legal opinion that the token falls outside the securities definition. For a DePIN protocol, the strategic choice is whether to forgo revenue distribution to token holders – preserving the classification as a utility or work token – or to accept the securities classification and structure the issuance under a prospectus exemption, a Regulation D offering in the United States or a private-placement model in jurisdictions that permit unregistered distributions to professional or institutional investors.

Data-protection exposure when infrastructure handles personal information

A DePIN network that stores, transmits or processes data on behalf of users triggers data-protection obligations in any jurisdiction where the network has users or where contributor nodes are located. The obligations attach at two levels: to the entity that determines the purposes and means of processing (the controller), and to the entity or individual that processes data on the controller's instructions (the processor). For a DePIN protocol, the allocation of controller and processor roles is fact-specific and depends on the degree of control the protocol entity retains over how data is handled, whether the protocol entity can access or modify data, and whether individual contributors exercise independent judgment over data-processing activities.

Under the GDPR, a controller is the entity that determines why and how personal data is processed; a processor is the entity that processes data on the controller's behalf. For a decentralised storage network in which the protocol entity publishes the smart contracts, maintains the network client software, and markets the service to end users, the protocol entity is typically the controller; individual node operators are processors. This allocation triggers Article 28 obligations: the controller must execute a data-processing agreement with each processor, must ensure that processors implement appropriate technical and organisational measures, and must ensure that processors process data only on documented instructions. The challenge for a DePIN network is that individual contributors are often pseudonymous, geographically dispersed, and not party to any direct contract with the protocol entity; the terms of service may state that contributors act as processors, but the absence of a signed data-processing agreement and the inability to audit contributor nodes creates compliance risk. ESMA and the Article 29 Working Party (now the European Data Protection Board) have stated that reliance on terms of service alone is insufficient where the processing involves special categories of data or where the processor is located in a third country without an adequacy decision, and that the controller must take active steps to verify processor compliance. In practice, most DePIN protocols address this exposure by designing the network to handle only encrypted data, such that node operators process encrypted payloads without access to the plaintext and therefore fall outside the GDPR processing definition – but this approach depends on client-side encryption, robust key management and the absence of any centralised decryption capability, all of which must be audited and documented to satisfy a data-protection authority during an investigation.

Outside the EU, data-protection exposure varies but follows a similar controller-processor logic. In the United Kingdom, the Data Protection Act 2018 and the UK GDPR impose obligations substantially identical to the EU GDPR, with the added complexity that data transfers from the UK to the EU now require adequacy or appropriate safeguards following Brexit. In Singapore, the Personal Data Protection Act treats the entity that determines the purposes of data collection as an organisation responsible for compliance, and outsourcing data processing to third parties does not absolve the organisation of accountability; the organisation must ensure that processors comply with the PDPA's protection obligations and must notify the Personal Data Protection Commission of data breaches within three business days if the breach is likely to result in significant harm or involves large-scale exposure of personal data. In Hong Kong, the Personal Data (Privacy) Ordinance defines a data user as the entity that controls the collection, use or disclosure of personal data, and a data user who engages a data processor must take contractual or other means to ensure the processor complies with the six data-protection principles; the Privacy Commissioner has issued guidance stating that mere reliance on contract terms without active monitoring and audit is insufficient where the processor operates outside Hong Kong. In the United States, comprehensive federal data-protection legislation remains absent at the time of writing, but state regimes – including the California Consumer Privacy Act (CCPA) and the Virginia Consumer Data Protection Act – define a controller as the entity that determines the purposes and means of processing and impose obligations to execute contracts with processors, to honour consumer rights (access, deletion, opt-out of sale) and to conduct data-protection impact assessments for high-risk processing; a DePIN protocol that handles California residents' data and meets the CCPA's revenue or data-volume thresholds is subject to these obligations regardless of where the protocol entity or the node operators are located.

The practical implication is that a DePIN protocol with users in the EU, UK, Singapore, Hong Kong or a US state with comprehensive privacy legislation must either design the network to avoid processing personal data – through client-side encryption, zero-knowledge proofs or fully anonymised data flows – or must implement a compliance framework that includes data-processing agreements with contributors, security and audit obligations, breach-notification procedures, and appointment of data-protection officers or representatives where required. The cost of non-compliance is high: the GDPR permits fines up to four percent of annual global turnover or twenty million euros, whichever is higher; the CCPA permits civil penalties of up to seven thousand five hundred US dollars per violation and a private right of action for data breaches; Singapore's PDPA permits fines up to one million Singapore dollars and, for individuals, imprisonment. Regulators in the major digital-asset hubs have signalled willingness to enforce data-protection obligations against decentralised protocols: the Irish Data Protection Commission investigated a blockchain-based identity platform on the basis that distributing personal data across validator nodes without adequate processor agreements constituted a GDPR breach, and the investigation resulted in a consent order requiring the operator to implement contractual safeguards and to appoint an EU representative. OBOLUS routinely advises DePIN projects on the data-protection perimeter at design stage, before node operators are onboarded and before user data is processed, because retroactive compliance – executing data-processing agreements with hundreds or thousands of pseudonymous contributors – is operationally infeasible and exposes the protocol to enforcement risk during the transition period.

Consumer-facing duties when individuals pay for infrastructure

A DePIN network that sells storage, bandwidth or compute access to individuals triggers consumer-protection obligations in the jurisdictions where those individuals are located. The obligations include advertising and disclosure rules, contract-term fairness standards, service-level commitments, complaint and dispute-resolution mechanisms, and in some jurisdictions a cooling-off period or cancellation right. The regulatory landscape is fragmented, with consumer protection falling under telecommunications law in some jurisdictions, e-commerce law in others and general consumer-protection statutes in a third category, but the consistent principle is that an entity providing a service to consumers for payment must meet transparency and fairness standards set by the jurisdiction where the consumer resides.

In the European Union, the Consumer Rights Directive applies to distance contracts – contracts concluded without the simultaneous physical presence of the business and the consumer, which includes purchase of DePIN services through a web interface or mobile application. The directive requires the business to provide clear information on the main characteristics of the service, the total price, payment and performance arrangements, the identity and contact details of the trader, and the existence of a right of withdrawal; for service contracts, the consumer has a fourteen-day cooling-off period unless the service has been fully performed with the consumer's consent and acknowledgment that the right of withdrawal will be lost. A DePIN protocol that charges users in tokens or fiat for storage or bandwidth is subject to these obligations where the user is an EU consumer, and non-compliance exposes the operator to enforcement by national consumer authorities and to private claims for contract rescission. The Unfair Commercial Practices Directive prohibits misleading actions and omissions and aggressive commercial practices; a protocol that markets decentralised storage with claims of guaranteed uptime or immutability without disclosing the risk of node failure or the absence of legal recourse against individual contributors may be found to engage in a misleading practice, resulting in enforcement action and reputational harm. Under the Digital Services Act, which applies from February 2024, an online platform that hosts user-generated content or facilitates transactions must implement complaint mechanisms, must cooperate with law enforcement on illegal content, and must comply with transparency obligations regarding content-moderation decisions; a DePIN marketplace that allows users to purchase services from contributors may fall within the platform definition, depending on the degree of intermediation and control the protocol entity exercises.

In the United Kingdom, the Consumer Rights Act 2015 implies terms into contracts for the supply of services to consumers: the service must be performed with reasonable care and skill, information provided about the service that is taken into account by the consumer in deciding to contract is binding as a term, and where the price is not agreed in advance, the consumer must pay only a reasonable price. A DePIN protocol that promises storage or compute availability and fails to deliver due to insufficient node participation or protocol failure may breach the implied term of reasonable care and skill, exposing the operator to a claim for breach of contract and to enforcement by the Competition and Markets Authority if the practice is widespread. The Electronic Commerce Regulations 2002 require service providers to make certain information easily accessible to recipients, including the name of the service provider, geographic address, email address, and where applicable registration numbers and supervisory authorities; a protocol entity that operates from a non-UK jurisdiction and markets services to UK consumers must comply with these obligations or risk enforcement and inability to enforce contracts in UK courts. In Singapore, the Consumer Protection (Fair Trading) Act prohibits unfair practices, including false or misleading representations about the quality, benefits or availability of goods or services, and grants the consumer a right to rescind a contract entered into as a result of an unfair practice; a protocol that overstates network reliability or understates the risk of data loss may be found to engage in an unfair practice, and affected consumers may seek rescission and damages. The Monetary Authority of Singapore has issued guidelines stating that digital-payment-token service providers must ensure that advertising and marketing materials are fair, clear and not misleading, must disclose risks prominently, and must implement fair and transparent complaint-handling procedures; these guidelines apply by analogy to DePIN services where payment is made in tokens.

The practical challenge for a DePIN operator is that compliance with consumer-protection rules across multiple jurisdictions requires adapting the user interface, the terms of service and the customer-support infrastructure to local requirements. The cost is non-trivial – a protocol with users in the EU, UK, Singapore and multiple US states must implement GDPR consent flows, Consumer Rights Directive withdrawal handling, UK accessibility standards, Singapore dispute-resolution procedures and state-specific disclosures, all while maintaining a user experience that does not deter adoption. The alternative – geoblocking users in high-compliance jurisdictions – reduces the addressable market and is difficult to enforce in a decentralised network where the protocol front-end may be hosted on IPFS or accessed through third-party gateways. Operators we advise typically adopt a tiered approach: full compliance in the top-tier jurisdictions where the user base and revenue justify the cost, basic disclosures and terms of service in mid-tier markets, and explicit exclusion of users in jurisdictions where compliance cost exceeds expected revenue or where the legal framework is hostile to digital-asset services. The tiered approach is not risk-free – a consumer in an excluded jurisdiction who suffers harm may still bring a claim arguing that the protocol was accessible and that the exclusion was ineffective – but it allocates compliance resources to the markets where enforcement is most likely and most costly.

Cross-border licensing: which jurisdiction for the entity

The choice of jurisdiction for the protocol entity is driven by four considerations: the availability of a digital-asset licensing framework that accommodates decentralised infrastructure models, the tax treatment of protocol revenue and of token distributions, the enforceability of smart contracts and the legal recognition of DAOs or foundation structures, and the jurisdiction's reputation and political risk profile among institutional users and capital providers. No single jurisdiction optimises across all four dimensions, and most DePIN protocols adopt a multi-entity structure with the foundation in one jurisdiction, the token issuer in a second and operational subsidiaries in the jurisdictions where licensing is mandatory.

Switzerland remains the preferred foundation jurisdiction for protocol entities that require legal personality, credibility with institutional counterparties and a tested framework for token issuance. FINMA's token classification guidance – distinguishing payment, utility and asset tokens – provides clarity on the regulatory perimeter, and the Swiss foundation structure permits holding and distributing tokens for protocol purposes without triggering corporate-profit-distribution rules. The Swiss foundation is tax-transparent at the federal level if it meets the non-profit criteria, though cantonal tax applies, and the foundation structure is recognised by EU authorities and by global banks, facilitating fiat on-ramps and fiat-crypto conversion. The disadvantage is that Switzerland does not offer a streamlined VASP licensing process, and a protocol entity that operates an exchange or custody service must apply for a fintech licence, a full banking licence or SRO membership under an AML law affiliation, each of which involves material capital and compliance cost.

Cayman Islands and the British Virgin Islands are the traditional offshore choices for token-issuer entities and for holding structures where tax neutrality is required. The Cayman foundation company and the BVI business company are flexible vehicles that permit token issuance without share-capital requirements, permit amendment of constitutional documents to accommodate protocol governance, and offer privacy for beneficial owners subject to economic-substance requirements. Both jurisdictions enacted VASP legislation – the Cayman Virtual Asset (Service Providers) Act and the BVI Virtual Asset Service Providers Act 2022 – requiring registration or licensing for entities that provide exchange, custody, transfer or advisory services for virtual assets, and both regimes are designed to meet FATF standards and to satisfy the grey-list-removal criteria. The licensing process in both jurisdictions involves material cost and requires demonstration of adequate systems and controls, senior management fitness and probity, and local substance, but the cost is lower than in a full-scope EU or Singapore licensing process, and both jurisdictions offer tax neutrality and political stability. The disadvantage is reputational: institutional counterparties and some exchanges remain wary of Cayman and BVI entities due to association with opacity and regulatory arbitrage, and a protocol domiciled solely in an offshore jurisdiction may face listing refusals or banking difficulties.

Singapore and Hong Kong are the leading Asian licensing hubs. Singapore's payment-service-provider regime under the Payment Services Act is well-developed, the licensing process is transparent, and MAS has granted licences to exchanges and custodians with strong compliance and governance frameworks; a DePIN protocol that facilitates token trading or holds user tokens in custody will likely require a standard or major payment-institution licence, depending on transaction volumes. Hong Kong's VASP licensing regime under the SFC is narrower – it applies to trading platforms, not to issuers or non-custodial protocols – but the regime is designed to accommodate institutional participation, and a protocol entity that operates an exchange or offers investment advice on tokens will require a virtual-asset trading-platform licence or a Type 1 or Type 4 licence under the Securities and Futures Ordinance. The advantage of both jurisdictions is credibility with global banks and with institutional investors; the disadvantage is high compliance cost, long licensing timelines and a regulatory posture that favours established operators with demonstrated governance over early-stage protocols.

Dubai under the VARA regime and Abu Dhabi under the ADGM framework have emerged as credible alternatives for operators seeking a licensing jurisdiction with political commitment to digital-asset development. VARA licences in Dubai are activity-based and available for advisory, custody, exchange, broker-dealer and lending activities; the application process requires a detailed business plan, senior management CVs and evidence of systems and controls, and the regulator has signalled willingness to work with applicants to tailor licence conditions to the business model. ADGM's framework is similarly flexible and modelled on the UK's FCA approach. Both jurisdictions offer tax neutrality on protocol revenue, and both permit foundation or company structures suitable for token issuance. The disadvantage is that both regimes are new – VARA was established in 2022 – and the jurisprudence on enforcement, insolvency and cross-border disputes is limited; a protocol entity domiciled in Dubai or Abu Dhabi may face difficulty opening banking relationships in the EU or the United States due to correspondent banks' risk appetite, and the long-term regulatory trajectory remains uncertain.

For a protocol with a global user base and contributors in multiple jurisdictions, the standard structure is a Swiss or Cayman foundation as the protocol-governance entity, a subsidiary in Singapore, Hong Kong or Dubai holding the digital-asset licences necessary to operate the token exchange or custody service, and local subsidiaries or registrations in the EU, UK and the United States to comply with consumer-protection, data-protection and advertising rules. The structure is complex, but the alternative – a single-entity model domiciled in one jurisdiction – exposes the protocol to the risk that a regulatory change or an enforcement action in that jurisdiction forces the protocol offline or freezes its assets. The multi-entity structure also permits segregating high-risk activities: the token-issuance and protocol-development activities sit in the foundation or in a jurisdiction with a developed legal framework for DAOs; the licensed trading and custody activities sit in the regulated subsidiary; and marketing, customer support and fiat-on-ramp activities sit in local subsidiaries that comply with consumer-protection rules and hold local bank accounts. The cost of the structure is governance complexity and the need for intercompany agreements that allocate revenue, risk and compliance obligations, but the cost is justified where the protocol has material revenue and a user base in enforcement-active jurisdictions.

DAO models: do they avoid regulation?

A decentralised autonomous organisation – a protocol governed by token-holder voting, with no identifiable legal entity and no centralised management – is sometimes proposed as a structure that avoids regulatory oversight on the theory that no person or entity can be held accountable where decision-making is fully decentralised. The theory is appealing, but it does not withstand scrutiny in any major jurisdiction. Regulators and courts in the United States, the EU, Singapore and Hong Kong have stated that decentralisation of governance does not eliminate legal personality for regulatory purposes, and that the entities or individuals who publish the protocol, control the smart contracts or derive economic benefit from the protocol remain subject to licensing, AML and consumer-protection obligations. The SEC's enforcement actions against DAO-governed protocols have proceeded on the theory that the persons who created and promoted the DAO are liable for unregistered securities offerings even where those persons claim to have relinquished control post-launch, and the CFTC has similarly asserted jurisdiction over DeFi protocols on the basis that the protocols facilitate trading in commodities and derivatives. The European Securities and Markets Authority has stated in guidance that the lack of a legal entity does not preclude application of MiCA, and that the persons who provide services through the protocol – including token issuance, exchange operation or custody – are subject to authorisation requirements.

The practical implication is that a DAO structure does not shield the protocol founders, developers or token holders from liability; it simply creates ambiguity about which persons or entities are responsible for compliance. Where a regulator seeks to enforce licensing or consumer-protection obligations, the regulator will target the persons with the greatest control or economic interest: the team that deployed the smart contracts, the foundation that holds the protocol treasury, the token holders who vote on protocol parameters, or the individuals who market the protocol to users. In Commodity Futures Trading Commission v. Ooki DAO, a US district court held that a DAO is a person subject to the Commodity Exchange Act and that service of process could be effected by posting the complaint in the DAO's online forum and airdropping a token containing a link to the complaint to DAO token holders, establishing that the DAO itself can be a defendant. The court further held that token holders who vote on governance proposals may be held jointly and severally liable as general partners in an unincorporated association, exposing individual token holders to unlimited liability for the DAO's obligations. While the decision is a district-court ruling and not binding precedent, it reflects the regulatory view that DAO structures do not create legal vacuums and that persons who exercise control through governance tokens are legally accountable for the DAO's compliance failures.

For a DePIN protocol, the implication is that reliance on a pure DAO model – with no legal entity, no identified management and no traditional corporate structure – increases regulatory risk rather than reducing it. The better approach is a DAO-wrapped foundation: a legal entity (typically a Swiss or Cayman foundation) that holds the protocol treasury and employs or contracts with the development team, with governance over certain protocol decisions delegated to token-holder voting through on-chain mechanisms. The foundation provides legal personality for licensing, contracting and enforcement purposes; the DAO governance provides credible decentralisation and aligns token-holder incentives with protocol development. The foundation's constitution documents the scope of DAO governance – which decisions require token-holder approval, which decisions are reserved to the foundation council, and the mechanism for executing on-chain votes – and the structure permits the foundation to enter into service agreements with contributors, to hold bank accounts and exchange accounts, and to serve as the counterparty for licensing applications and enforcement negotiations. The model is not risk-free: regulators may argue that the foundation retains ultimate control and is therefore responsible for all protocol activities, including activities nominally delegated to the DAO. But the model at least provides a legal entity that can respond to regulatory inquiries, negotiate licensing conditions and enter into settlements, whereas a pure DAO model leaves the regulator with no clear counterparty and incentivises the regulator to pursue the protocol's most visible promoters or largest token holders on a joint-and-several-liability theory.

Structuring the contributor agreement

The contributor agreement – the legal relationship between the protocol entity and the individuals or entities who provide physical infrastructure – is the compliance lever for allocating licensing and liability exposure. Where the agreement characterises contributors as independent contractors providing services to the protocol entity, and where the protocol entity retains the right to approve or remove contributors, set service standards and enforce compliance obligations, the protocol entity is more likely to be treated as the service provider for licensing purposes and contributors are more likely to be treated as subcontractors or processors. Where the agreement disclaims any employment or agency relationship, states that contributors act in their own capacity and warrant independent compliance with local law, the protocol entity may argue that contributors are independent operators and that licensing exposure sits with the contributors – but this position is difficult to sustain where the protocol entity controls the token-distribution algorithm, sets the fee schedule or provides the user-facing interface through which individuals purchase infrastructure services.

A well-drafted contributor agreement for a DePIN protocol includes the following elements: (1) a clear statement that the contributor is an independent contractor, not an employee or agent of the protocol entity; (2) a warranty from the contributor that participation in the network complies with local licensing, telecommunications, data-protection and tax law, and an indemnity from the contributor to the protocol entity for claims arising from the contributor's breach of local law; (3) an acknowledgment that the contributor is responsible for securing any necessary local approvals, registrations or licences and for maintaining insurance adequate to cover the risks of providing infrastructure services; (4) a data-processing clause that, where personal data is involved, designates the contributor as a processor acting on the instructions of the protocol entity (as controller), requires the contributor to implement security measures and to execute a data-processing agreement where required by the GDPR, and prohibits the contributor from processing data for any purpose other than delivering the infrastructure service; (5) a service-level expectation or uptime target, with the protocol entity reserving the right to suspend or remove a contributor who fails to meet the expectation; (6) a clause permitting the protocol entity to suspend or terminate the contributor's access to the network if the contributor is located in a jurisdiction where operation without a licence exposes the protocol entity to liability, or if the contributor engages in prohibited conduct (fraud, misuse of network resources, violation of the terms of service); (7) a choice-of-law and dispute-resolution clause that specifies the jurisdiction whose law governs the agreement and provides for arbitration or exclusive jurisdiction in a named forum, reducing the risk that contributors in multiple jurisdictions bring claims in their local courts under their local consumer-protection regimes.

The agreement is typically implemented through a click-through acceptance during the onboarding process, with contributors required to confirm they have read the terms, understand the compliance obligations and agree to be bound. The structure is not bulletproof – a court or regulator may find that the agreement is a contract of adhesion, that the warranty and indemnity provisions are unenforceable against an individual contributor with limited legal sophistication, or that the choice-of-law clause is void as contrary to the mandatory consumer-protection or employment law of the contributor's jurisdiction. But the agreement serves three functions: it creates a documentary trail demonstrating that the protocol entity made reasonable efforts to allocate compliance obligations, it permits the protocol entity to argue that contributors act independently and that the protocol entity is not vicariously liable for contributors' regulatory breaches, and it provides a contractual basis for removing contributors who create unacceptable risk. OBOLUS routinely structures contributor agreements to include a jurisdiction schedule: a list of jurisdictions in which the protocol entity has determined that unlicensed participation creates material exposure, with contributors from those jurisdictions either excluded from the network or required to provide proof of local registration or licensing as a condition of onboarding. The jurisdiction schedule evolves as regulatory risk changes: if a regulator in a major market issues guidance stating that DePIN node operators require a licence, the protocol entity updates the schedule to exclude or constrain contributors from that jurisdiction, reducing the risk of enforcement action premised on widespread unlicensed activity.

When to engage structuring counsel

The legal perimeter for a DePIN protocol is determined at design stage, before the token is issued, before contributors are onboarded and before users begin paying for infrastructure services. Post-launch restructuring is expensive, slow and often impossible: a token that has been publicly distributed as a work reward cannot be recalled and reissued under a securities prospectus; a protocol that has processed personal data without data-processing agreements in place cannot retroactively cure the GDPR breach; an operator that has onboarded contributors in a jurisdiction requiring telecommunications licensing cannot undo months of unlicensed activity. The decision to engage counsel is not whether, but when: before the whitepaper is published, before the smart contracts are deployed to mainnet, or after the first enforcement letter arrives.

Counsel is engaged early in three scenarios. First, where the protocol design includes features that create ambiguous classification risk – revenue-sharing, staking yields, pre-launch token sales, centralised control over network parameters – and the team requires a legal opinion on whether the token meets the definition of a security or a financial instrument in the target jurisdictions. The opinion process involves reviewing the token distribution mechanics, the governance model, the marketing materials and the post-launch roadmap, and delivering a written analysis of classification risk across the relevant frameworks (SEC, MiCA, MAS, SFC). The opinion is not a guarantee, but it permits the team to make an informed decision on whether to proceed with the planned structure, to modify the token mechanics to reduce securities risk, or to restrict the offering to professional investors under a prospectus exemption. Second, where the protocol involves personal data processing – storage of user files, transmission of user traffic, processing of transaction metadata – and the team requires guidance on whether the protocol can be designed to avoid GDPR controller or processor obligations or, if not, what contractual and technical measures are necessary to comply. The guidance shapes the encryption model, the key-management architecture, the data-residency logic and the contributor terms of service, all of which are difficult to retrofit once the network is live and user data is distributed across nodes. Third, where the protocol targets a specific licensing jurisdiction – Switzerland, Singapore, Hong Kong, Dubai – and the team requires a scoped assessment of the licensing path, the timeline, the capital requirement and the likelihood of approval before committing to the entity-formation and banking costs.

The second engagement scenario is reactive: the protocol is live, tokens have been distributed, and a regulator or exchange has raised a classification or licensing issue. The issue may be a request for information from the SEC, a refusal to list the token by a major exchange pending a legal opinion, a cease-and-desist letter from a national competent authority in the EU asserting that the protocol operates without a CASP authorisation, or a complaint to a data-protection authority alleging that the protocol processes personal data without a legal basis. At this stage, the legal work is defensive: preparing a response to the regulator, negotiating a no-action position or a consent order, applying for a licence on a remedial basis, or restructuring the token to cure the compliance defect and applying for delisting and relisting under the new terms. Reactive work is more expensive than proactive work, because it operates under time pressure and with a public record of the compliance failure, and the outcome is less certain: a regulator who has already determined that the protocol violates the law is less likely to accept a good-faith compliance proposal than a regulator approached before launch with a detailed plan. The cost differential is often an order of magnitude: a pre-launch structuring engagement covering entity formation, token classification and licensing strategy in three jurisdictions runs in the range of mid-five figures to low six figures; a post-enforcement restructuring – involving responses to multiple regulators, licence applications, token restructuring, contributor off-boarding and potential settlement negotiations – runs in the range of mid-six figures to seven figures.

For a protocol at the concept or whitepaper stage, the engagement brief is strategic: map the classification risk, identify the licensing triggers, propose a jurisdiction for the entity and the token issuer, draft the contributor agreement and data-processing terms, and deliver a go/no-go assessment. For a protocol preparing to launch on mainnet, the engagement is execution: register the entity, apply for the necessary licences, execute banking and exchange agreements, implement AML and KYC procedures, draft the terms of service and the privacy policy, and coordinate the listing process with exchanges. For a protocol facing an enforcement issue, the engagement is remedial: assess the regulator's position, prepare the response, negotiate the outcome, and if necessary restructure the token or the protocol to comply. OBOLUS advises across all three scenarios, with digital assets and decentralised infrastructure the whole of our practice. To map the structure before you commit, write to info@oboluslaw.com.

FAQ

Can a decentralised protocol be regulated?

Yes. Regulators in the United States, the EU, Singapore and Hong Kong have stated that decentralisation of governance or operation does not eliminate legal personality for regulatory purposes. The entities or individuals who publish the protocol, control the smart contracts, market the service or derive economic benefit from the protocol remain subject to licensing, anti-money-laundering and consumer-protection obligations. A pure DAO structure – with no legal entity and no identified management – does not shield the protocol founders or token holders from liability; it creates ambiguity about which persons are responsible for compliance, and regulators typically target the persons with the greatest control or economic interest.

Who is liable when a smart contract fails?

Liability for a smart-contract failure depends on the nature of the failure and the contractual relationship between the parties. If the failure results from a bug or exploit in the contract code, the entity that deployed the contract may be liable for negligence if the code was not audited or if known vulnerabilities were not disclosed. If the failure results from a protocol design flaw – such as an economic-incentive misalignment that permits market manipulation – the protocol entity or governance token holders who approved the design may be liable under consumer-protection law or under a breach-of-contract theory. Where the smart contract is a component of a regulated service – such as a token-trading protocol – the licensed entity is typically held responsible for failures in any part of the service stack, including smart-contract failures, and cannot disclaim liability by arguing that the code operates autonomously.

What wrapper suits this structure?

The choice of legal entity for a DePIN protocol depends on the regulatory perimeter, the tax treatment and the need for credibility with institutional users and capital providers. A Swiss foundation offers legal personality, tested token-issuance frameworks and tax transparency for non-profit entities, and is recognised by global banks and EU authorities. A Cayman foundation company or BVI business company offers tax neutrality, flexibility in governance and lower entity-maintenance costs, but may face reputational challenges with institutional counterparties. A DAO-wrapped foundation – a Swiss or Cayman foundation with certain governance decisions delegated to token-holder voting – combines legal personality with credible decentralisation and is the preferred model for protocols requiring both on-chain governance and the ability to contract, license and bank. The structure is typically paired with regulated subsidiaries in Singapore, Hong Kong or Dubai to hold digital-asset licences and with local registrations in the EU, UK and the United States to comply with consumer-protection and data-protection rules.

About OBOLUS

OBOLUS is an independent digital-asset law boutique acting only for businesses. We advise exchanges, custodians, token issuers and funds on licensing across more than seventy jurisdictions, on disputes and on-chain asset recovery across twenty-five forums, and on the tax, banking and compliance that sit around them. Digital assets are the whole of our practice. We assess token classification against the substance of rights, not the marketing label, and we advise crypto exchanges, custodians, token issuers and funds on the legal architecture for decentralised infrastructure projects across borders. To discuss your situation, contact info@oboluslaw.com or write via the contact page.

By Roman Levitt, Technology & DeFi Counsel – advising on protocol structuring, smart-contract legal risk and decentralised infrastructure compliance across digital-asset regulatory frameworks.

This publication is general information about the law and does not constitute legal advice. It is not a substitute for advice tailored to your circumstances. OBOLUS accepts no liability for action taken or not taken on the basis of this material. For advice on your situation, contact info@oboluslaw.com.

Discuss your matter with OBOLUS

Tell us about the business, the jurisdictions in scope and the deadline. Every brief is confidential and we reply within two hours.

Or email info@oboluslaw.com. We treat your brief as confidential.

Tell us the task — we'll map your options in 30 minutes.

Fixed-fee packages with defined scope and SLAs. The first call is free and under NDA. Business clients only.

Map your optionsinfo@oboluslaw.com · reply < 2 hours