Introduce a client, earn up to 20% of our fees for two years. No cap, on every matter they instruct.The referral programme →
BVI · Digital assets

The DeFi protocol legal stack.

Serious DeFi protocols do not run on one company. They run on a small stack of entities, each holding one function and one set of risks: a token issuer, a development company, a governance foundation, and often a separate front-end operator. Here is the standard architecture, why it is built this way, and where the BVI fits.

The architecture

One function per entity, one set of risks per entity.

The design principle is isolation. A DeFi project generates several distinct kinds of legal exposure: securities-law risk on the token, contract and employment liability in the development operation, regulatory pressure on whoever operates the user-facing interface, and the simple concentration risk of a treasury worth real money. Put all of that in one company and every risk contaminates every asset. Split it correctly and a problem in one box stays in that box.

The standard stack has settled into a recognisable pattern. The token issuer is a BVI Business Company, usually owned by the foundation rather than the founders, following the architecture in our Cayman Foundation and BVI issuer guide. The development company, DevCo or LabsCo, holds the team, the contracts and usually the IP until it is licensed or transferred to the protocol; BVI is the low-cost default, and ADGM is increasingly chosen where the team wants UAE visas, an onshore presence and a substance story in Abu Dhabi. Governance and treasury sit in an ownerless foundation, Cayman by default, Panama as the cheaper alternative, so that no individual owns the protocol's value and token-holder governance has a legal anchor.

Protocol functionTypical entityWhy
Token issuanceBVI BC (owned by the foundation)Issuer pattern outside VASP registration; clean listing opinions
Development, team, IPDevCo / LabsCo: BVI BC or ADGMContracts, payroll, IP assignment; ADGM where UAE presence needed
Governance and treasuryCayman or Panama foundationOwnerless, purpose-driven; anchors DAO governance
Front-end / interface operationSeparate opco, often BVIAbsorbs interface-level regulatory risk away from treasury
Treasury operations (staking, LP, yield)Subsidiary of the foundationActive balance-sheet risk kept off the governance layer
Grants and ecosystem fundingFoundation directly, or a grants subsidiaryPurpose spending documented against the foundation's objects

Not every protocol needs every row on day one. Most launches start with three entities and add the operational subsidiaries as the treasury and user base grow.

Regulatory analysis

Where DeFi sits under the VASP Act.

The BVI VASP Act 2022 registers businesses providing virtual asset services for or on behalf of third parties: operating an exchange, transferring assets between accounts, holding client assets in custody. A genuinely non-custodial protocol maps poorly onto those definitions. Where smart contracts execute peer-to-peer, no entity in the stack takes possession of user assets, matches orders as a business, or executes transfers on instruction. On the standard analysis, the protocol itself, and the issuer that deployed its token, fall outside VASP registration. The same issuer logic is covered from the token side in BVI for token issuance.

The entity that deserves the most careful watching is the front-end operator. Regulators worldwide have shown that when they cannot reach a protocol, they reach for the interface: the company hosting the website, setting fee switches, curating token lists and holding the domain. Whether that activity amounts to a virtual asset service is fact-specific, and the answer is drifting toward more scrutiny rather than less. This is precisely why the front-end sits in its own entity, with its own directors and its own modest balance sheet. If the perimeter moves, the interface company can register, geo-fence, restructure or wind down without touching the token, the treasury or the DevCo.

Two adjacent traps are worth naming. A protocol whose team routes user funds through team-controlled wallets, even briefly, has custody risk regardless of what the whitepaper says. And a treasury operation that starts managing outside money, rather than the protocol's own assets, has walked into fund territory under SIBA; the line is the same one drawn in our crypto trading guide, and the fund-side answer is in the crypto fund guide.

Operations

Contributors, treasury and the paper trail.

Contributor payments are where clean structures most often get messy. The pattern that works: the DevCo signs contractor or employment agreements with every contributor, pays in fiat or stablecoins on invoices, and administers token allocations under written vesting agreements granted by the issuer. Contributors get a real counterparty they can name to a bank or a tax authority; the project gets IP assignment clauses that actually bind; and the foundation stays out of payroll entirely, which keeps its governance role clean. Paying core contributors ad hoc from a multisig, with no agreements, is the single most common defect we are asked to repair after the fact, usually when an exchange, auditor or investor asks who owns the code.

Treasury operations follow the same logic. The governance layer holds and votes; a subsidiary transacts. Where the treasury runs staking, liquidity provision or yield strategies, those positions sit in an operating subsidiary so that counterparty and smart-contract risk does not sit on the same balance sheet as the protocol's reserves. Economic substance obligations in the BVI are assessed per entity against the nine Relevant Activities, and holding-only entities carry a reduced test; the economic substance guide covers the framework. None of this structure changes onshore tax outcomes for founders and contributors, who remain taxable where they live; the stack is about liability and governance, not about making income disappear.

How ArxSetup runs the file: the engagement is partner-led, fees are fixed and quoted in writing, and BVI entities are filed directly with the FSC through our licensed registered-agent partners, typically incorporating in 5 to 7 days. We sequence the full stack (foundation, issuer, DevCo, intercompany IP and services agreements), coordinate BVI counsel where a token legal opinion is needed for listing, and make banking introductions for the entities that need fiat rails. For protocols moving toward token-holder governance, the BVI DAO guide covers the wrapper question.

Reviewed by the ArxSetup editorial team

Reviewed by qualified counsel within ArxSetup and our affiliated practices, Neo Legal (UAE) and Cornwalls (Australia). Figures verified against primary regulator sources. Last reviewed: September 2026. DDA Licence 107229 · Dubai Media City. How we review →

Frequently asked

Common questions.

The questions clients ask most before committing. Current to 2026, reviewed by counsel.

What is the standard legal structure for a DeFi protocol?

A multi-entity stack: a token issuer company (typically a BVI Business Company), a development company or LabsCo holding the team, IP and contracts (BVI or ADGM are common), and a foundation for governance and treasury (Cayman or Panama). Larger protocols add separate entities for the front-end operator and treasury operations. No single entity should hold every function.

Does a DeFi protocol need VASP registration in the BVI?

Generally not for the protocol itself. A genuinely non-custodial protocol, where smart contracts execute peer-to-peer and no entity holds user assets or executes trades for users, generally falls outside the VASP Act's definition of providing virtual asset services for third parties. The analysis is fact-specific: front-end operators, fee-collecting intermediaries and anything touching custody deserve close review.

Why do the front-end and the treasury sit in separate entities?

Because they carry different risks. The front-end operator faces the regulatory perimeter in every jurisdiction where users access the interface, and it is the entity most likely to be pressured or sued. The treasury holds the protocol's value. Separating them means an action against the interface operator does not put the treasury or the token contracts at risk.

How are DeFi contributors paid through the structure?

Usually by the DevCo under contractor or employment agreements, in fiat, stablecoins or token allocations subject to vesting. Running payments through the DevCo keeps the foundation's governance role clean, gives contributors a real counterparty, and creates the paper trail banks and future investors expect.

What does a full DeFi structure cost to set up?

As a guide: a BVI issuer or DevCo runs USD 8,500 in year one, a Cayman Foundation typically USD 18,000 to 25,000 all-in, and a token legal opinion USD 12,500 to 25,000. A complete three-entity stack with documentation is commonly in the USD 40,000 to 70,000 range in year one, fixed and quoted in writing before engagement.

This page is general information, reviewed September 2026. It is not legal, tax or immigration advice, and it does not create a client relationship. Advice specific to your circumstances is provided only under a signed engagement letter. Government fees are set by the relevant authority and may change without notice. Where local registered agents are required, we coordinate with licensed partners and disclose their role in writing.