Why do I need a token issuance vehicle?

If you are launching a token, you probably need a legal entity to issue it from. In many jurisdictions, launching a token is a regulated activity. Launch without a token issuance vehicle, and launch it without a token issuance vehicle in a web3 friendly jurisdiction, and you will have severe regulatory exposure. There are other reasons: issuing a token without a wrapper exposes you personally to the liabilities the token generates, locks you out of the exchanges and banking relationships your project may need, and - if you are dealing with regulated counterparties - signals that you do not understand what you are doing.

The technical act of deploying a smart contract and minting tokens takes minutes. The legal consequences of doing so can last years. A token issuance vehicle is how you ensure those consequences land somewhere you designed, not somewhere you didn't.

Why this matters 

Token issuance is easier than ever, but the rules around it are growing much more complicated. The EU's MiCA regulation is now fully in force. VARA in Dubai introduced a dedicated licensing category for asset-referenced token issuers in May 2025. The US SEC issued updated guidance on token classification in 2025. Regulators globally are paying closer attention to who issued a token, from where, under what legal framework, and with what investor protections in place. 

Tax authorities are also paying attention. Individuals who launched tokens without a wrapper are potentially liable to large tax bills. Given that these are launched on blockchain networks, they are fully transparent and trackable; all it takes is a tax authority with the resources and drive to look, and many founders will be facing issues. 

This does not mean launching a token is harder than it used to be; on a technical level, the opposite is true. What it does mean is that the gap between a properly structured issuance and an unstructured one has widened significantly. It is a legal gap, and a commercial gap - exchanges, institutional investors, and banking partners have all raised their expectations of what a credible token project looks like. The minimum bar is a proper legal entity. Everything below that threshold is becoming commercially as well as legally untenable.

What happens if you issue without one?

Founders should take this question seriously. The answer varies between jurisdictions, but the broad picture is the same. 

Personal liability. Without a corporate entity between you and the token, you are the issuer. Claims by token holders - for losses, for misrepresentation, for failure to deliver promised utility - are claims against you personally. In a securities law context, personal liability for founders issuing unregistered securities has resulted in regulatory action, disgorgement of proceeds, and civil penalties. In a civil litigation context, token holders in multiple jurisdictions have successfully pursued founders individually where no entity existed to absorb the claim.

Regulatory exposure. In most jurisdictions, a regulated activity conducted without authorisation is illegal regardless of whether the person conducting it knew they needed a licence. In many cases, issuing a token without authorisation is against the rules. Particularly severe consequences can arise if these tokens turn out qualify as securities. If you don’t structure it right, the regulatory exposure will hit founders personally. 

Tax exposure: A token launch is a takeable event, one that creates wealth for the launcher. If an individual launch a token without a corporate wrapper, that tax liability will accrue to the individual personally.

Counterparty rejection. Centralised exchanges require a legal entity to list a token. They require KYC/AML documentation, corporate structure evidence, and in many cases legal opinions on token classification. An individual cannot satisfy these requirements. Banking partners - even crypto-friendly ones - will not open accounts for unincorporated token issuers. Without a bank account, managing the proceeds of a token sale becomes a practical impossibility that creates further legal risk.

No structural separation. If your token project fails, or is subject to regulatory action, or faces investor claims - and no legal entity exists - everything is co-mingled. Your personal assets, your operating business, your other projects, your co-founders' exposure: all of it is in the frame. A properly structured entity limits the blast radius.

What does a token issuance vehicle actually do?

A token issuance vehicle is a legal entity specifically established to:

Issue the token. The entity deploys the smart contract, mints the tokens, and is the counterparty to all investor subscription agreements. Token holders' legal rights run against the entity, not the founders.

Hold associated assets. Proceeds from the token sale, reserve assets backing the token, treasury funds, or underlying real-world assets are held in the entity's name. This provides legal separation between the token project and the founding team's personal and other business assets.

Manage the legal relationship with token holders. The token terms and conditions, the token offering memorandum, and the investor subscription agreements are contracts between the entity and each token holder. The entity is the party that can be sued, that can hold funds, that can be regulated, and that can enter into commercial agreements on behalf of the project.

Provide regulatory positioning. The jurisdiction of incorporation determines the primary regulatory framework applicable to the issuance. A BVI entity issuing tokens benefits from specific BVI legislative features. A Panama entity benefits from the SMV's position that tokens are not securities under Panamanian law. A VARA-licensed entity in Dubai benefits from the ARVA framework's explicit regulatory authorisation. The choice of entity and jurisdiction is a structural decision, not an administrative one.

The two main structural options

Structure 1: Holding company + token issuance Company

The most common structure for web3 projects. A holding company - often in the BVI, Cayman, or the founder's preferred jurisdiction - sits at the top of the stack and owns the token issuance vehicle below it. The token issuance vehicle is typically incorporated in a crypto-friendly offshore jurisdiction: the BVI and Panama are the most common choices for rapid offshore issuances.

Why this works:

The holding company provides the institutional-facing legal anchor - the entity that investors, VCs, and acquirers deal with. It also means that the ultimate controllers of the project don’t directly own the token issuance vehicle. The token issuer is a purpose-built vehicle with a clean balance sheet, no legacy liabilities, and a legal domicile chosen for its token-issuance characteristics. Keeping them separate means a problem in one does not automatically become a problem in the other.

This structure is cost-effective, fast to establish, and familiar to legal counsel globally. It is the right starting point for most early and mid-stage token projects.

Structure 2: Foundation + token issuance company

Projects seeking meaningful decentralisation - particularly DAO launches, protocol tokens, and governance token issuances - often use a non-shareholder foundation as the top layer instead of a holding company. The foundation holds the treasury, owns any intellectual property, and provides a governance framework that reflects the decentralised nature of the project. A token issuance company sits below it and issues the tokens.

Foundation structures are used to signal - and in many cases to create - genuine separation between the founding team and the protocol. This matters for regulatory positioning (a truly decentralised protocol is treated differently from a centrally controlled one in most jurisdictions) and for the long-term governance credibility of the project.

Common foundation jurisdictions include Cayman Islands (the Cayman Foundation Company, used by Uniswap, dYdX, and many others), Panama (the Private Interest Foundation under Law 25 of 1995), and Switzerland  - though it should be noted that Swiss based projects are now mainly using Associations rather than foundations. 

See our DAO and protocol wrappers use case page for a full breakdown of foundation options and when each is appropriate.

Which jurisdiction for the token issuance vehicle?

The jurisdiction choice is where structural strategy becomes specific. The key variables are:

What type of token is being issued? A utility token, a governance token, and a security token have different regulatory profiles and therefore different optimal jurisdictions. A debt-style token benefits from the BVI's SIBA debenture exclusion. An ARVA token in Dubai benefits from VARA's dedicated framework.

Who are the investors? The laws of investor jurisdictions apply to the offering regardless of where the issuer is incorporated. An offshore issuer reaching EU investors must still analyse MiFID II and the Prospectus Regulation. An issuer reaching US persons must still analyse US securities law. The issuer jurisdiction choice affects the issuer's own compliance obligations; it does not affect the obligations triggered by the investor's location.

What does the project need the structure to do? Speed and cost-efficiency point toward BVI or Panama. Regulatory credibility with institutional investors points toward a licensed jurisdiction. EU market access points toward Malta or another web3 friendly EU jurisdiction. Gulf capital and institutional MENA relationships point toward VARA or ADGM in the UAE.

The BVI and Panama are the two most commonly chosen jurisdictions for rapid, cost-effective offshore token issuances. See our detailed comparison at BVI vs Panama for token issuance and our jurisdiction-specific guides for the legal specifics that make each one appropriate for different structures.

When should you set this up?

Before you do anything else - before you issue your whitepaper, before you sign contracts with exchanges, and certainly you raise from investors. Ideally, before you deploy a smart contract.

The reason is simple: the entity is the issuer. If you have already distributed tokens without an entity in place, you have either issued them personally (creating the personal liability problems described above) or issued them through an entity that was not purpose-built for the function (creating structural problems that are expensive to unwind).

Setting up a token issuance vehicle at the right time costs a fraction of what it costs to restructure after the fact - and restructuring becomes significantly harder once token holders are in the picture.

FAQ

Can I use my existing operating company to issue the token? You can, but it is almost always the wrong approach. An operating company has existing assets, existing liabilities, existing shareholders, and an existing purpose. Using it as the token issuer co-mingles the token project with all of those. If the token project faces regulatory action or investor claims, the operating company's assets are in frame. If the operating company has existing contractual obligations that restrict token issuance or fundraising, those restrictions bind the token project. A purpose-built SPV avoids all of this.

What is the minimum I need to set up before issuing a token? At minimum: a properly incorporated legal entity in an appropriate jurisdiction, token terms and conditions governing the legal relationship with holders, a subscription agreement for investors, an AML/KYC process for onboarding, and a legal opinion on token classification. A Token Offering Memorandum is strongly recommended for any raise above a trivial amount. A smart contract audit is expected by most serious counterparties.

Is the BVI or Panama better for a token issuance vehicle? It depends on the token type, the investor base, and the budget. The BVI offers a regulated environment with specific legislative features — particularly the SIBA debenture exclusion for debt-style token issuances and the ability to maintain an on-chain share register. Panama offers faster and cheaper formation and a securities regulator that has confirmed it does not treat tokens as securities, with territorial jurisdiction that does not reach purely offshore offerings. See our BVI vs Panama comparison article for a detailed head-to-head.

Do I need a different entity for each token I issue? Not necessarily, but it is often cleaner to use separate vehicles for separate token projects. A single entity issuing multiple tokens creates co-mingling of assets and liabilities across those projects. BVI Segregated Portfolio Companies (SPCs) offer one solution: multiple segregated portfolios within a single entity, each legally isolated from the others. For most early-stage projects, a single purpose-built entity per token project is the cleaner approach.

What if I have already issued tokens without an entity? You need legal advice specific to your situation. The exposure varies significantly depending on what the token is, who holds it, where it was offered, and what has happened since issuance. In some cases, a retrospective restructuring — wrapping the existing token project in a new entity with appropriate documentation — is achievable. In others, the prior issuance has created obligations or exposure that need to be addressed directly. Do not delay getting advice on this.

This article is for informational purposes only and does not constitute legal or financial advice. The appropriate structure for a token issuance vehicle varies significantly by token type, investor base, and jurisdiction. Always seek qualified legal advice before issuing a token.

FormationLayer advises web3 founders and international counsel on token issuance structuring and entity formation across the BVI, Panama, UAE, and EU. We work with projects from first token to institutional-scale issuances.

Ready to set up your token issuance vehicle? Book a consultation with our team — we will help you choose the right structure and jurisdiction before you issue, not after.