EST · MMXXVI
Home/Insights/Technology & DeFi/DePIN Token Classification and Contributor Incentives
DeFi, Tokenization & Smart-Contract Law

DePIN Token Classification and Contributor Incentives

DePIN Token Classification and Contributor Incentives. Independent digital-asset law for exchanges, issuers and funds. Cross-border scope, fixed-fee engagements

A protocol that wants to incentivise storage operators, bandwidth providers or sensor-node hosts with tokens discovers that the legal classification turns on what the token represents, not on what the founder calls it. When contributor rewards carry a profit expectation tied to the protocol's success, the line between a decentralised utility and a regulated investment instrument moves. Where the protocol sits, where token recipients operate and whether a functional network existed before the first distribution each shift the analysis.

DePIN – decentralised physical infrastructure networks – issues tokens to individuals who contribute compute, bandwidth, storage or data-capture hardware to a shared network. The legal question is whether those tokens are securities, whether the protocol operator needs a VASP or exchange licence, and what happens if the structure is challenged. Across the major hubs, regulators apply the same substance-over-form tests that apply to any token, with added scrutiny where the network is nascent and early contributors rely on the protocol's development efforts for future value.

How classification turns on rights and expectations

Under the frameworks that dominate digital-asset regulation – MiCA in the EU, the Securities and Futures Ordinance administered by the SFC in Hong Kong, the Payment Services Act supervised by MAS in Singapore, and the Howey test applied by the SEC in the United States – a token is classified by the rights it confers and the expectations it creates, not by the label the issuer assigns. A DePIN token that functions as payment for bandwidth consumed by network users may qualify as a utility or a means of payment. A DePIN token distributed to early hardware contributors with the promise that its value will rise as the network scales, where the protocol foundation controls development and the contributor does nothing but plug in hardware, looks like an investment contract.

The classification sits on a spectrum. At one end, a participant earns tokens for each gigabyte of storage delivered, the tokens trade freely and can be spent immediately within the network. At the other, a participant receives tokens subject to a vesting schedule, the whitepaper forecasts token appreciation tied to adoption, and the founding entity retains decision authority over protocol upgrades. The first structure argues for a payment or utility classification; the second argues for a security under every major test.

In our cross-border practice, we routinely advise protocol teams building DePIN networks, and the pattern is consistent: the classification question is resolved before the token-generation event, not after an enforcement action. Where the token crosses into security territory, the protocol faces prospectus obligations under MiCA, registration or exemption requirements under the SEC, or licensing as a trading facility if it operates a secondary market.

The Howey test applied to contributor incentives

The Howey test – an investment of money in a common enterprise with profits derived from the efforts of others – remains the primary analytical framework in the United States and the foundation for parallel tests in other common-law jurisdictions. A DePIN structure meets the first two prongs if the contributor purchases hardware or stakes capital to participate and if token value depends on the collective success of the network. The decisive question is whether profits derive predominantly from the efforts of the founding team or from the contributor's own operational input.

Where the protocol is young, the codebase evolves under foundation control, and the contributor's role is passive – running prepackaged software with no material decision-making – courts and regulators are likely to find that value derives from the promoter's efforts. Where the network is live, decentralised governance is operational, the contributor configures and maintains hardware with discretion, and token value reflects real-time service delivery, the security classification weakens.

Timing matters. A token distributed at network launch, when the protocol has no users and the roadmap promises future functionality, presents higher risk than the same token distributed two years later when throughput is established and the contributor joins a functioning marketplace. The SEC's framework for digital assets, published in 2019 and applied in subsequent enforcement actions, explicitly considers whether a functional network exists at distribution.

A protocol we assessed in early 2025 planned to distribute tokens to sensor operators contributing environmental data. The initial structure granted tokens based on nodes deployed, with locked vesting over eighteen months and a whitepaper section titled "anticipated token economics" that projected price appreciation as corporate buyers entered the data marketplace. That structure satisfied all four Howey prongs. The revised model introduced a live data feed consumed by pilot buyers before any public token sale, compensated node operators with tokens unlocked daily and spendable within the ecosystem, and removed forward-looking price commentary. The revised structure moved the token materially away from security classification under U.S. analysis, though it did not eliminate risk entirely.

MiCA classification and the ART/EMT distinction

MiCA – the Markets in Crypto-Assets Regulation effective across the EU from 2024 – divides tokens into three categories: asset-referenced tokens (ARTs), e-money tokens (EMTs), and "other" crypto-assets. A DePIN reward token almost never meets the ART or EMT definitions, because it is not redeemable at par for fiat and does not reference a basket of assets. It falls into the "other" category, which triggers the whitepaper and disclosure regime but not the capital and reserve requirements that apply to stablecoin issuers.

The material question under MiCA is whether the token confers rights comparable to transferable securities under the EU's Markets in Financial Instruments Directive. Where it does, ESMA expects the issuer to comply with the Prospectus Regulation, not just the MiCA whitepaper rules. The test turns on whether the token grants a share in future revenues, a governance right over distributions, or an expectation of appreciation tied to the issuer's efforts – factors that mirror Howey but framed within EU financial-instrument definitions.

A DePIN protocol distributing tokens to bandwidth providers in multiple EU member states must assess whether those tokens create an investment expectation. If the whitepaper emphasises adoption and scarcity, if early tokens are locked and released on a schedule correlated to milestones, and if recipients cannot immediately use the tokens for their stated utility, the token risks triggering both MiCA's transferable-security analysis and the broader prospectus regime. In that scenario, the issuer needs either a CASP authorisation or an exemption, and the legal costs and timelines extend well beyond a simple whitepaper filing.

Contributor status: employee, contractor or community participant

A separate but equally significant question is whether the DePIN contributor is an employee, an independent contractor, or an unaffiliated participant in a decentralised network. The classification affects tax withholding, labour protections, intellectual-property assignment and liability for operational failures. Where the protocol entity exerts control over how, when and where the contributor operates hardware, the relationship begins to resemble employment. Where the contributor operates autonomously, sets pricing or service parameters and bears the cost of infrastructure, the relationship looks like an independent service provider or a decentralised participant.

The factors regulators examine include the degree of supervision, the exclusivity of the arrangement, whether the entity provides the hardware or the contributor owns it, and whether compensation is fixed or performance-based. A storage protocol that ships hard drives to participants, mandates uptime through an enforced SLA, and penalises downtime through slashing resembles a contractor model. A protocol that allows anyone to join with their own hardware, imposes no service-level obligation beyond consensus rules, and compensates purely based on verified work looks more like a decentralised utility.

In jurisdictions with strict labour protections – most EU member states, Singapore, Hong Kong – misclassifying a contributor as a community participant when the relationship is substantively one of control can expose the protocol to back-taxes, social-insurance contributions and wrongful-termination claims. In a matter we handled in late 2024, a protocol that described node operators as "independent community members" faced a tax audit in an EU jurisdiction where the authority re-characterised ten operators as disguised employees, triggering six-figure withholding liabilities. The protocol had mandated software versions, imposed uptime penalties and provided detailed operational instructions – facts that supported the reclassification.

Licensing questions for the protocol operator

Where a DePIN protocol distributes tokens that are classified as securities or regulated financial instruments, the entity distributing them and any entity operating a secondary market must hold the appropriate licence. Under MiCA, that means a CASP authorisation for operating a trading platform or providing custody of crypto-assets on behalf of third parties. Under the Singapore Payment Services Act, it means a Digital Payment Token service licence if the protocol operates an exchange or facilitates token transfers for users. Under the SFC regime in Hong Kong, it means a VATP licence if the platform allows secondary trading of virtual assets that qualify as securities.

Even where the token is not a security, the protocol may need a licence if it operates a marketplace, holds user tokens in custody, or facilitates fiat on-ramps. The line between a decentralised protocol and a regulated service provider is drawn at the point where an identifiable entity exercises control over user funds, maintains an order book, or provides settlement services. A protocol that is genuinely decentralised – where the code runs autonomously on public infrastructure, users custody their own keys, and no entity controls transaction execution – generally sits outside VASP licensing perimeters. But most DePIN projects retain a foundation, a development company or an operator entity that controls initial distribution, upgrades the protocol and manages partnerships, and that entity can be the licensing target.

VARA in Dubai, FSRA in the ADGM, and the Bank of Lithuania under the MiCA transition have each taken the position that if a token functions as a means of exchange or store of value and if an entity in their jurisdiction facilitates its distribution or secondary trading, that entity needs authorisation. The analysis does not stop at whether the token is a security; it extends to whether the activities conducted around the token fall within the regulated perimeter.

A practical checkpoint before launch: map which entity issues the token, which entity (if any) operates a marketplace or provides liquidity, and where those entities and their key personnel are located. Cross-reference that map against the VASP and exchange-licensing regimes in each relevant jurisdiction. If any activity falls within a regulated category and no exemption applies, licensing or restructuring is required before the token-generation event.

Vesting, lockups and the timing of economic interest

The timing and structure of token vesting significantly affect classification. A token granted to a contributor but locked for twelve months, released linearly and subject to forfeiture if the contributor ceases to operate hardware, begins to resemble deferred compensation tied to future performance – a fact pattern that strengthens the argument for an employment or contractor relationship and, in some analyses, a security classification where value depends on the protocol's continued development.

Conversely, a token that vests immediately, is freely tradable and can be used within the network from day one presents a stronger utility argument. The immediate economic interest and the absence of dependence on future efforts shift the analysis away from investment-contract territory. The design question is whether the lockup serves a legitimate network-security purpose – such as preventing a flash attack by a malicious node operator – or whether it functions primarily to align contributor interest with the protocol's long-term success, which introduces a profit-expectation element.

Slashing provisions – where tokens are forfeited if the contributor fails to meet service commitments – add a further layer. A slashing mechanism that operates autonomously through smart-contract logic, based on objectively verifiable metrics such as uptime or bandwidth delivery, is a technical feature of the protocol. A slashing provision that requires discretionary review by the foundation or that applies penalties based on subjective quality assessments looks like employer supervision and can support reclassification of the contributor relationship.

Geographic realities: where the token is offered and where contributors sit

A DePIN protocol that distributes tokens to participants in seventy countries faces seventy sets of securities, tax and labour rules. The default position – that a decentralised protocol has no single jurisdiction and therefore no single regulator – does not survive first contact with enforcement reality. Regulators assert jurisdiction where the token is offered to their residents, where the issuer or a key operational entity is located, or where secondary trading occurs on a platform accessible to local users.

In the EU, offering tokens to residents without the required MiCA whitepaper triggers liability for the issuer and potential enforcement by any member-state NCA. In the United States, offering unregistered securities to U.S. persons, even through a decentralised protocol, exposes the founding entity and its directors to SEC enforcement. In Singapore, operating a DPT service without a licence is a criminal offence. The fact that the protocol is decentralised or that the contributor base is globally distributed does not create a safe harbour; it multiplies the compliance surface.

The structuring answer is to determine at the outset which jurisdictions the protocol will serve, which it will block, and where the entity will be domiciled. A protocol domiciled in a jurisdiction with a clear token framework – Switzerland, the ADGM, Singapore under the Payment Services Act – and that applies robust geo-blocking to high-risk jurisdictions can narrow its compliance obligations. A protocol that takes no position on where users access it, that makes no effort to exclude any geography, and that conducts no KYC faces enforcement risk in every major market.

When decentralisation is not a defence

Protocol teams frequently argue that because the DePIN network is decentralised, no single entity can be held responsible for compliance failures. That argument has been tested and rejected in multiple enforcement actions. The SEC's position, articulated in cases involving decentralised exchanges and DeFi protocols, is that if an identifiable group of people initiated the protocol, controls its governance, profits from its operation or has the ability to modify its code, that group is the liable party for purposes of securities and exchange regulation.

Courts in the United States have found that a protocol marketed as decentralised but controlled by a small team, with tokens distributed heavily to insiders and governance votes that reliably reflect the founders' positions, is functionally centralised for regulatory purposes. The same principle applies under MiCA and under Singapore's Digital Payment Token framework: if a protocol entity exercises de facto control, it is the regulated actor, regardless of how the whitepaper describes the governance model.

True decentralisation – where no entity can unilaterally change the protocol, where governance is distributed across a broad and unaffiliated token-holder base, and where the founding team has exited operational control – can create a different analysis. But that state is rarely achieved at launch and often not for years after. During the period of functional centralisation, the protocol must comply as if it were a traditional issuer and service provider.

Tax treatment of contributor rewards

Tax authorities in major jurisdictions treat tokens received as compensation for services as ordinary income at the time of receipt, valued at fair market value. Where the token is illiquid or subject to a lockup, some jurisdictions allow deferral until the restriction lapses; others require immediate recognition. A contributor in the United Kingdom who earns tokens through running a storage node recognises income at receipt and, if the token later appreciates, recognises a capital gain on disposal. A contributor in Germany may receive more favourable treatment if the token qualifies as a payment for services rendered within a commercial activity, but the analysis turns on the contributor's overall tax status and the characterisation of the activity.

The protocol entity, if it is the payer, may have withholding obligations if the contributor is classified as an employee or, in some jurisdictions, as a contractor. Where contributors are globally distributed, the protocol must determine whether it has a taxable presence in each contributor's jurisdiction and whether it must file information returns or withhold tax at source. The compliance cost of operating a DePIN protocol with 10,000 contributors in 50 countries, each subject to local reporting rules, is material, and many protocols underestimate it at launch.

A protocol we advised in mid-2024 initially assumed it had no tax-reporting obligation because it characterised contributors as decentralised participants. A review of the operational structure revealed that the protocol entity maintained a list of approved node operators, set compensation rates and issued monthly statements – facts sufficient to create a payer relationship in multiple jurisdictions. The protocol restructured to make participation truly permissionless, removed the approval process and eliminated fixed compensation, shifting to a model where the smart contract compensated nodes autonomously based on verified deliveries. That restructuring reduced but did not eliminate the tax exposure; in some jurisdictions the protocol still needed to file information returns for payments above statutory thresholds.

Dispute scenarios: when a contributor relationship breaks

Disputes between DePIN protocols and contributors follow predictable patterns. A node operator claims unpaid rewards, alleging that the protocol's slashing mechanism applied penalties incorrectly. A protocol terminates a participant for violating terms of service, and the participant argues wrongful termination under local labour law. A contributor demands return of staked collateral, and the protocol refuses, citing ongoing service failures. Each scenario raises questions of which forum has jurisdiction, which law applies, and whether arbitration or blockchain-based dispute resolution is enforceable.

Where the protocol's terms of service include an arbitration clause and a choice-of-law provision, those terms are generally enforceable against contributors in commercial relationships, provided the terms were clear and the contributor had an opportunity to review them. Where the relationship is reclassified as employment, mandatory local-labour-law protections may override the arbitration clause, and the contributor can bring a claim in a local labour tribunal regardless of what the terms of service state.

In a recovery matter we handled in late 2024, a contributor to a bandwidth-sharing protocol staked a five-figure sum in tokens and operated nodes for six months before the protocol accused the participant of fraudulent traffic inflation and slashed the entire stake. The contributor challenged the decision in an English court, arguing that the protocol's terms were one-sided, that the slashing decision was made without notice or a hearing, and that the tokens represented property subject to conversion principles. The court granted interim relief freezing the slashed tokens pending a full trial. The case settled, but it illustrated that decentralised protocols are not immune from traditional property and contract enforcement.

Offshore foundation structures and the limits of insulation

Many DePIN protocols incorporate a foundation in a jurisdiction with favourable tax and regulatory treatment – commonly the Cayman Islands, the BVI, Switzerland or Liechtenstein – with the expectation that the foundation structure insulates the founding team from personal liability and narrows the compliance perimeter. That expectation is only partially correct. A foundation domiciled offshore still creates a taxable presence in any jurisdiction where it has employees, operates servers, or conducts marketing activity. It is still subject to securities regulation in any jurisdiction where it offers tokens to residents. And if the foundation is a shell with no independent governance and all decisions are made by the founding team, courts will pierce the structure and hold the founders directly liable.

The advantage of an offshore foundation is that it can serve as the token issuer, hold protocol intellectual property, and appoint independent supervisory boards that provide governance oversight. The disadvantage is that it requires genuine operational substance – board meetings, documented decisions, compliance policies – to be respected as a separate entity. In enforcement actions, regulators and courts routinely disregard foundations that exist only on paper.

For a protocol operating at scale, the structuring question is not whether to use an offshore entity but how to allocate functions among multiple entities: one to issue the token, one to provide development services under contract, one to operate contributor onboarding, and so on. That multi-entity approach increases complexity but can reduce the risk that any single entity is exposed to the full compliance burden or to liability for every aspect of the protocol's operation.

What wrapper suits a DePIN structure

The choice of legal entity depends on whether the protocol will raise venture funding, distribute tokens widely, retain revenue or operate as a non-profit. A foundation suits a protocol that will operate as a public good, with no equity investors and with protocol revenue directed to development grants and ecosystem support. A Delaware C-corp or a Cayman exempted company suits a protocol that will raise equity rounds and that intends an eventual liquidity event for shareholders. A DAO LLC – available in Wyoming, the Marshall Islands and select other jurisdictions – suits a protocol that wants legal personality for the DAO itself, with members holding governance tokens that function as membership interests.

Each wrapper carries trade-offs. A foundation provides tax efficiency and alignment with decentralised ethos, but it makes equity financing difficult and governance cumbersome. A C-corp simplifies venture investment but creates U.S. tax exposure and subjects the protocol to Delaware corporate law. A DAO LLC bridges the gap but is still a developing legal form, and its recognition outside the jurisdiction of organisation is uncertain.

In our structuring practice, we routinely advise teams to begin with a hybrid: a foundation to issue and manage the token, and a separate operating company to employ the team, hold intellectual property under licence and contract with enterprise customers. That approach keeps token governance non-profit, allows the team to raise equity in the operating company, and provides a clean liability boundary between protocol development and commercial services. It requires careful drafting of the relationship between the entities and clear rules about how protocol revenue is allocated, but it is a tested model across multiple DePIN launches.

Before committing to a structure, map the economics across five years. Where will revenue flow? Will the foundation take fees from transactions, or will a separate entity sell access to the network? How will early contributors, employees and investors be compensated – through tokens, through equity, or through both? The entity structure must support the economic model, and restructuring after launch is expensive and sometimes legally impossible once tokens are distributed.

Practical steps before a DePIN token generation event

The time to assess classification, licensing and contributor-relationship questions is before the token-generation event, not after the first regulatory inquiry. A protocol that launches without resolving these questions and that later discovers its token is an unregistered security faces a choice: delist, restructure or face enforcement. Each option is costly, and none is guaranteed to preserve the project.

The assessment process follows a standard sequence. First, document what the token represents and what rights it confers – not what the whitepaper says, but what the smart contract enforces and what the contributor reasonably expects. Second, map that token against the securities tests in the jurisdictions where the protocol will operate or where it will offer tokens. Third, determine whether the contributor relationship creates employment, contractor or tax-reporting obligations. Fourth, identify which entity will issue the token and whether that entity or any affiliated entity needs a licence. Fifth, structure the vesting, distribution and governance model to support the intended classification.

If the analysis shows that the token is a security, the options narrow to registration, an exemption, or limiting distribution to institutional buyers under private-placement rules. If the analysis shows that the token sits outside the security definition but the protocol operates a marketplace, a VASP licence may still be required. If the analysis shows that contributors are effectively employees, restructuring to make participation autonomous is necessary before launch.

In a recent pre-launch assessment, a protocol building a decentralised sensor network planned to distribute tokens to participants who deployed IoT devices capturing air-quality data. The initial model granted tokens at deployment, locked them for eighteen months, and stated in the whitepaper that value would grow as the protocol signed data-purchase agreements with corporate buyers. We flagged that structure as a probable security under Howey and a transferable security under MiCA. The protocol revised to make tokens freely transferable from the moment of grant, tied value strictly to data delivered (not to future adoption), removed forward-looking commentary from marketing materials, and introduced a live marketplace with paying buyers before the public token sale. The revised model moved classification away from security territory, allowed the protocol to proceed with a MiCA whitepaper filing instead of a full prospectus, and avoided VASP licensing in the EU.

To map your options before the token generation event or if a prior classification assumption is being challenged, contact OBOLUS at info@oboluslaw.com.

How regulators are approaching infrastructure tokens

Across the jurisdictions where DePIN protocols have scaled – the EU under MiCA, Singapore under MAS, Hong Kong under the SFC, and the United States under the SEC – regulators are applying established frameworks to novel facts, not creating DePIN-specific rules. The consistent position is that the token's function, not its label, determines classification, and that a utility claim is credible only if a functioning utility exists when the token is distributed.

ESMA has stated that tokens distributed before a network is operational, or where the network depends on the issuer's continued development efforts, are likely to meet the financial-instrument test. The SFC in Hong Kong has taken a similar view: if the token holder's return depends on the work of the issuer, the token is a security regardless of whether it also has a future utility function. MAS in Singapore looks to whether there is a genuine and immediate use for the token at the time of distribution and whether that use is independent of the issuer's post-distribution efforts.

The SEC's enforcement practice has targeted DeFi and infrastructure protocols that distributed governance tokens to early users with the representation that governance participation would drive token value. The SEC's theory is that even if the token confers voting rights, those rights are investment features if the tokenomics and marketing emphasise value appreciation. In settled enforcement actions, the SEC has required protocols to register tokens as securities, to file periodic reports, and to implement trading restrictions.

In late 2024, the SEC brought an action against a protocol operating a decentralised storage network, alleging that tokens distributed to storage providers were unregistered securities because contributors had no operational discretion, because tokens vested over time tied to network growth, and because the whitepaper repeatedly referred to token scarcity and anticipated demand from enterprise buyers. The protocol settled without admitting liability, but the settlement required a token burn, a cessation of U.S. distribution, and registration of a restructured token under Regulation A+. The legal cost and the delay destroyed the protocol's first-mover advantage in the market.

How a utility token stops being a utility

A token classified as a utility at launch can become a security if the protocol's operations change such that token value shifts from use-driven to investment-driven. If a protocol that originally compensated contributors for delivering bandwidth pivots to a model where token holders vote on treasury allocations and share in protocol revenue, that pivot can convert the token into a security even if it was not one at launch. The SEC and other regulators have indicated that classification is not static; it is reassessed when facts change.

Similarly, a token that was a security at launch can lose that status if the network becomes genuinely decentralised and the founding team exits. The SEC's 2019 framework contemplates a transition: a token may begin as a security when the network depends on the promoter's efforts, and it may cease to be a security when the network is functional, governance is distributed, and token value reflects use rather than the expectation of future work by identifiable others. But that transition is not automatic, and regulators expect the issuer to file for exemptive relief or to obtain a no-action letter before treating the token as no longer subject to securities regulation.

A protocol that wants to transition from a security to a utility must document that the protocol is operationally decentralised, that governance decisions are made by a broad and unaffiliated token-holder base, that the founding team no longer has discretionary control, and that token value is tied to network usage rather than to speculative appreciation. That documentation may form the basis for an exemption request or a regulatory filing, but it is not a unilateral declaration. In the current environment, making that transition without regulatory sign-off is high-risk.

Related at OBOLUS

FAQ

Can a decentralised protocol be regulated?

Yes. Regulators assert jurisdiction where an identifiable group initiated the protocol, controls its governance, profits from its operation, or can modify its code. True decentralisation – where no entity exercises control – may create a different analysis, but that state is rarely achieved at launch. During the functional-centralisation period, the protocol is subject to securities, VASP and tax rules in every jurisdiction where it operates or offers tokens to residents.

Who is liable when a smart contract fails?

Liability falls on the entity that deployed the contract, the entity that represents to users that the contract is safe, or the entity that exercises control over the protocol within which the contract operates. If a bug causes loss and a foundation, development company or identifiable team was responsible for auditing and deploying the code, that entity is the defendant in a negligence or misrepresentation claim. Disclaimers and decentralisation claims do not eliminate liability where control and responsibility are shown.

What wrapper suits this structure?

A foundation domiciled in Switzerland, Liechtenstein, the Cayman Islands or the BVI suits a protocol operating as a public good with no equity investors. A Delaware C-corp or Cayman exempted company suits a protocol raising venture rounds. A hybrid – a foundation for the token and a separate operating company for commercial services – provides tax efficiency and supports both token governance and equity investment. The choice depends on the economic model, the investor base, and where the team and infrastructure are located.

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 classification against the substance of rights, not the marketing label, and we structure protocols to withstand regulatory scrutiny before launch. To discuss your situation, contact info@oboluslaw.com.

By Roman Levitt, Technology & DeFi Counsel – Roman advises protocol teams and token issuers on smart-contract enforceability, DeFi regulatory classification, and cross-border structuring for decentralised infrastructure networks.

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