Which entity should issue your token, and why it decides everything else.

Most token projects choose an issuing vehicle late, under time pressure, on the recommendation of whoever formed the last one. The consequences arrive in a fixed order: a bank declines the treasury account, an exchange's compliance team declines the listing, the founders discover the token sale was taxable where they live, and an acquirer's diligence finds that the intellectual property and the token are held by different entities with no agreement between them.

Each of those outcomes traces back to the same decision. The issuer determines the legal characterisation of the token in the jurisdictions where it was offered, and therefore who may lawfully hold it. It determines whether proceeds are corporate income, capital, or a liability against future delivery. It determines which regulator, if any, supervises the activity, which in turn determines banking acceptance. And it determines the liability perimeter around the individuals who signed.

There is also a governance dimension that founders underweight. A vehicle chosen for tax reasons and controlled entirely by two founders will be read by sophisticated participants — and by regulators — as a company selling a security, whatever the whitepaper says. A vehicle with genuine independent governance and a defined purpose reads differently. The structure is part of the substance of the claim, not decoration around it.

This guide sets out the vehicle families actually used, how the operating company and the issuer should relate to each other, where intellectual property should sit, how treasury and token allocations should be held, the tax events founders miss, what exchanges and banks look at, and how to sequence the whole thing.

It is written for founders who intend the project to still exist in five years and to survive diligence when it matters.

Most well-structured token projects separate the issuer from the operator. The issuer holds and issues the token, holds the token treasury, and carries the obligations attached to the token. The operating company employs the team, owns or licenses the technology, contracts with customers and suppliers, and earns service revenue.

The separation exists for four reasons. Liability: claims attaching to the token do not automatically reach the operating business, its contracts or its staff. Regulation: the issuer's activity is characterised separately from the operator's, which allows each to sit in the jurisdiction that fits its activity. Tax: service revenue and token proceeds have very different profiles and are best not commingled. Commercial: an acquirer can buy the operating business without inheriting the token's obligations, and investors can take equity in the operator without buying token exposure.

The separation only works if it is documented. The relationship between the two entities needs real agreements: a development or services agreement under which the operator builds and maintains the protocol for the issuer, a licence agreement for intellectual property, and transfer pricing that reflects what independent parties would charge. Two entities with no agreements between them are treated as one by tax authorities and are a diligence failure for acquirers.

Where founders get this wrong is usually in the direction of paperwork minimalism: forming the second entity and never papering the relationship, or invoicing between them at arbitrary amounts. Both create tax exposure in the jurisdiction where value is actually created, which is generally where the team sits.

For very early projects a single entity is sometimes defensible, provided the migration path is planned. Migrating later is possible but the transfer of token treasury and intellectual property between entities is itself a taxable event in many systems, which is why doing it before value accrues is dramatically cheaper.

Foundation-type vehicles, used in several jurisdictions, have no shareholders and a defined purpose in their constitution, governed by a council or board. Their appeal is genuine: they support a credible claim that no owner captures the token's value, which helps the decentralisation narrative and is well understood by exchange compliance teams. The cost is loss of control by design — the council governs, and founders who want a foundation that they in fact control have neither the benefit nor a defensible position.

Company limited by guarantee and similar non-share-capital companies serve a comparable function with a different legal mechanism, and in some jurisdictions with lower running costs and a more familiar governance form for auditors and banks.

Ordinary limited companies in credible jurisdictions are the pragmatic choice for projects where the token is openly a product or utility of a business, where the offering was structured with counsel to avoid a public-offering problem, and where the founders are prepared to be identified as the controlling owners. Simpler, cheaper, better understood by banks; weaker for a decentralisation claim.

Purpose trusts and hybrid structures appear where assets must be held for beneficiaries who are not identifiable, such as protocol treasuries intended for future token holders. They are specialist, they need experienced trustees, and they are frequently used where a simpler vehicle would do.

DAO-adjacent legal wrappers now exist in several jurisdictions, giving on-chain governance a legal personality that can contract, hold assets and limit member liability. They are the right answer where governance genuinely sits with token holders. They are the wrong answer where a small team decides everything, because the mismatch between the wrapper and reality is what a regulator or an acquirer's counsel notices first.

The choice among these should follow the honest answer to one question: who actually controls the protocol and its treasury, now and in eighteen months. Structures that misdescribe control fail at the moment they are examined.

The jurisdiction decision runs on six inputs, in roughly this order of importance. First, whether the jurisdiction's legal framework recognises the vehicle type and the activity of token issuance, and whether an offering can be structured there without triggering a public-offering or licensing requirement for the token in question.

Second, banking acceptance. An issuer that cannot open a treasury account and cannot receive fiat conversion proceeds is not a working structure, and this is decided by how the jurisdiction's reputation reads to correspondent banks — not by its legislation.

Third, exchange acceptance. Listing compliance teams have de facto views on issuer jurisdictions because their own banking partners and regulators do. A jurisdiction that makes a Tier-1 listing harder is an expensive saving.

Fourth, substance and corporate residency. Economic-substance regimes require real local activity, and corporate tax residency generally follows management and control — so an issuer incorporated in one place and directed from a founder's home in another risks being taxed in the second, with penalties for the years it did not file there. Real local governance is what answers both.

Fifth, the founders' own tax positions, including controlled-foreign-company rules that can attribute the issuer's profits to a founder personally regardless of where the entity sits. Sixth, ongoing cost and administrative burden: local directors, audit, registered office, filings and the professional support the vehicle needs each year.

Almost every bad outcome in this area comes from optimising the sixth input and ignoring the second, fourth and fifth.

Intellectual property placement determines where profit is properly earned and how an acquisition is structured. The common patterns are: IP owned by the operating company and licensed to the issuer; IP owned by the issuer and developed under a services agreement by the operator; or IP in a separate holding entity licensed to both. Each has different tax and commercial consequences and each requires arm's-length pricing.

What does not work is unallocated IP — code written by contractors with no assignment, protocol documentation in a founder's personal accounts, trademarks registered to an individual, domains held personally. Diligence finds all of these, and remediation after the fact requires cooperation from people whose interests may have changed.

The token treasury should sit in the issuer, under custody arrangements with a signing policy and role separation, not in an exchange account or a founder's wallet. Allocation tranches — team, investors, ecosystem, liquidity, reserves — should be held in identified addresses that reconcile exactly to the published allocation table and vesting schedule, ideally under contract-enforced vesting rather than a promise.

Founder and team allocations deserve their own structuring thought, because the timing of the tax event depends on how the entitlement is granted, when it vests, whether it is transferable, and the rules of the jurisdiction where each individual is resident. This is one of the few places where getting the paperwork right at grant is worth an order of magnitude more than optimising afterwards.

And every one of these arrangements should exist in writing before a token exists on a public chain, because on-chain reality is the record a regulator, an exchange and an acquirer will test the documents against.

The receipt of sale proceeds is the obvious event, and even that has variation: depending on structure and jurisdiction, a pre-launch sale can be treated as revenue on receipt, as a liability against future delivery recognised over time, or as something else again. The treatment changes the cash tax profile materially and it should be agreed with the auditor before the sale, not after.

Then the events that surprise people. Transfers of token treasury or IP between group entities during a restructuring. Token-for-token swaps and migrations to a new contract. Providing tokens to a market maker under a loan-and-option structure, which may be a disposal in some systems. Staking and other protocol rewards received by the issuer. Payment of contractors and staff in tokens, which typically creates employment or service tax obligations at grant or vesting in the individual's country.

For founders personally: the vesting of an allocation, the disposal of any part of it, and — for anyone contemplating relocation — the exit charges that can crystallise on unrealised token gains when tax residency ends. Relocating after a token appreciates is often the single most expensive sequencing error available.

Corporate residency exposure runs underneath all of it. If the issuer is effectively managed from a country the founders live in, that country may treat it as resident and tax the proceeds at its own rate, with interest and penalties for unfiled years. CFC rules can achieve a similar result without needing to establish residency at all.

None of this is exotic, and all of it is manageable when it is modelled before the sale. The projects that pay the most tax are usually the ones that were structured for a tax outcome without qualified local advice in the countries that actually had a claim.

An exchange listing committee's compliance function reads a structure looking for reasons to decline. What reassures them: an issuer in a jurisdiction their banking partners accept, a clear ownership and control chain with identified beneficial owners, a legal classification analysis from recognised counsel, an allocation table that reconciles to on-chain addresses, contract-enforced vesting, treasury under custody with governance, and no undisclosed related-party allocations.

What causes a decline: opaque ownership, an issuer in a jurisdiction with no supervision their banks respect, early allocations to entities with no disclosed relationship to the project, vesting that does not match the chain, treasury in a personal account, and a decentralisation claim that the governance documents contradict.

Banks read the same structure differently. They are underwriting fiat flow: which entity receives money, from whom, in what amounts, for what stated purpose, and whether the beneficial owners' residencies and the entity's jurisdiction combine into a file their committee can approve. They also care whether any activity in the group requires a licence it does not hold, because unlicensed regulated activity is a termination event.

The practical implication is that the structure should be built to be read by these two audiences from the beginning. Both will see it, both have institutional memory, and both are considerably harder to persuade the second time.

This is also why the assembled file — entity documents, ownership chain, classification opinion, allocation reconciliation, custody arrangements, inter-company agreements — is an asset. Built once, it serves every exchange, bank, investor and acquirer that asks.

One: define the token honestly — what it does, what rights it carries, who it will be offered to and in which countries, and what the roadmap needs it to do in two years. Two: obtain legal classification analysis in the jurisdictions of offering, from counsel whose opinions exchanges and banks recognise.

Three: design the group — issuer vehicle and jurisdiction, operating company, IP placement, inter-company agreements, and the founders' personal positions, all modelled together with local counsel in each country that has a claim. Four: incorporate and paper it, including the governance the vehicle claims to have.

Five: banking, before the sale. Treasury account, operating account, fiat conversion path and contingency. This is the step most often left until proceeds exist, and it is the step most likely to fail.

Six: token deployment with contract-enforced vesting and identified allocation addresses matching the published table. Seven: distribution, structured to match the classification analysis. Eight: liquidity and listings, with the market making mandate contracted before submission. Nine: ongoing operation — filings and audit in each jurisdiction, substance maintained, treasury policy enforced, allocation and unlock calendar communicated.

Timelines: classification and design four to ten weeks; incorporation and papering two to six; banking three to ten; deployment and audit two to eight. Realistically three to six months from a clean start to being ready to distribute, and longer where an existing structure has to be unwound first.

Choosing the vehicle for tax and describing it as decentralised while two founders control it. Forming a foundation and then treating it as a personal company, which forfeits the benefit and creates a governance record that contradicts itself.

Two entities with no agreements between them, so tax authorities and acquirers treat them as one. Arbitrary inter-company invoicing with no transfer-pricing basis.

IP left with contractors, or trademarks and domains held personally. Treasury on an exchange account. Allocation tables that do not reconcile to on-chain addresses. Vesting promised in a whitepaper but not enforced by contract.

Leaving banking until after the sale, then holding proceeds nowhere a bank will accept them. Signing a market maker loan-and-option agreement without modelling whether it is a disposal for tax.

And the most expensive: relocating personally after the token appreciates rather than before, and structuring the entity for a tax outcome without qualified advice in the country where the founders actually live.

The first deliverable is a structure paper, not a formation. It sets out the honest control position, the token's characterisation risk in the jurisdictions of offering, a recommended issuer vehicle and jurisdiction with the trade-offs written down, the operating company and IP placement, the inter-company agreements required, the founders' personal exposures including CFC and exit-tax risk, and the banking acceptance we expect for the finished structure.

We then execute it with qualified local counsel in each relevant jurisdiction: incorporation of the issuer and operator, foundation or wrapper governance documents and council appointments where applicable, IP assignment and licence agreements, development and services agreements with transfer pricing that stands up, and the founder and team allocation documents drafted with the tax event in mind in each individual's country of residence.

Banking is part of the mandate and it happens before the distribution. Working from a network of more than 120 banking and payment institutions whose current appetite for digital-asset issuers we track, we build the file to institutional standard and arrange treasury and operating accounts, a fiat conversion path and a contingency relationship. Institutions decide independently, and we say so before we start.

On the token itself, we prepare the file exchanges and banks actually read — classification analysis, ownership chain and beneficial-owner disclosure, allocation reconciliation to on-chain addresses, contract-enforced vesting, custody and signing governance — and we specify the treasury policy that will govern it afterwards.

Where the project needs liquidity, listings or execution, those run as connected mandates: market maker selection and mandate negotiation including the tax and disposal analysis of loan-and-option structures, exchange introductions through our Institutional Access Program for projects whose file is genuinely ready, and OTC and treasury execution for converting proceeds without moving your own market.

Send us the token's design, where you intend to offer it, where the team and founders are resident, and the current entity position. We will come back with the structure we would build, what it costs, how long it takes, and the specific risks we would not take on. Compliance-first throughout, coordinated with qualified local counsel — and this page is general information, not legal or tax advice.