Web3 Company Legal Structure: Operating Company, Foundation, Token

"Where do I incorporate?" is the wrong first question, because it assumes the answer is one company in one country. A Web3 project is usually a structure with three distinct parts: an operating company that builds and employs, a foundation or wrapper that holds the protocol and shields participants, and the token itself. This guide maps how those three functions split across entities and why the split matters; for the choice between specific wrappers see the wrapper comparison, and for where to base the whole thing see the jurisdiction guide. The cost of getting the structure wrong is concrete: an unwrapped DAO can be treated as a general partnership. Every line here is a counsel question.

The structure in brief

• A Web3 project is usually not one entity but three functions: an operating company (builds, employs), a foundation or wrapper (protocol/IP, regulator interface, liability shield), and a token (its own instrument).
• The unwrapped-DAO risk is real: in Samuels v. Lido DAO, a US federal court applying California law indicated an unwrapped DAO could be a general partnership, exposing participants to personal liability.
• Which entity issues the token, and where, is a securities and tax counsel decision with no universal answer.
• "Offshore equals no tax" is false. Economic substance, CFC rules, place of effective management and the founders' own tax residence all apply.
• Decide the structure before token issuance and fundraising, because it interacts with the fundraising stack and the cap table.
• The whole thing is fact-specific, substance-dependent and jurisdiction-specific. Confirm with legal and tax counsel in every relevant jurisdiction. This is not legal or tax advice.

Three functions, often three entities

The functions are distinct, and collapsing them or skipping the wrapper concentrates legal, tax and liability risk. The split is fact-specific, not a template.

The unwrapped-DAO liability problem

This is why wrappers exist. In the Samuels v. Lido DAO matter, a US federal court applying California law indicated an unwrapped DAO could be treated as a general partnership, which can expose participants to personal liability for the organisation's obligations. That analysis is jurisdiction- and fact-specific and must be assessed with counsel, but the exposure of going unwrapped is real, and it is the case that drives the foundation/wrapper choice.

Who issues the token, and where

Whether the operating company or a foundation/wrapper is associated with the token is one of the most consequential decisions, touching securities, tax and governance. There is no universal answer; it is a securities- and tax-counsel determination on the specific facts and jurisdictions. It also drives the cap table, since equity and token ledgers may sit in different entities.

The "offshore equals no tax" misconception

Registering an entity in a low-tax jurisdiction does not make a project tax-free. Economic-substance rules, controlled-foreign-company (CFC) regimes, place-of-effective-management tests, and the founders' own personal tax residency all apply regardless of the registry. Structure is a compliance and liability question first; any tax effect is jurisdiction-specific. See the offshore substance myth.

Sequence it before the raise

The structure interacts with the instruments raised (for example a SAFE plus a token warrant) and the token plan. Restructuring after a token is live, or after a priced round, is materially harder. Design the structure, the fundraising stack and the cap table together with counsel rather than sequentially.

Practical guidance

1. Map the three functions (build, protocol/token, value instrument) before choosing entities.
2. Do not run a DAO unwrapped; assess the general-partnership exposure with counsel.
3. Decide the token-issuer entity and jurisdiction with securities and tax counsel, since there is no template.
4. Treat "offshore" as a substance and compliance question, never an automatic tax saving.
5. Sequence the structure before fundraising and issuance, because it constrains the fundraising stack and the cap table.
6. Confirm with legal and tax counsel per jurisdiction. This is fact-specific and not legal or tax advice.

Choosing a tool to model the structure

Because the structure spans an operating company, a foundation or wrapper and a token, you need somewhere that can hold all three and their instruments rather than just an equity cap table. Pulley covers token and equity; Carta is equity-focused. Both record entities, cap tables and instruments and can model ownership and dilution. When choosing, confirm the tool can represent equity and token ledgers that may sit in different entities, since that separation is central to this kind of structure. The tool records and models; it does not determine the structure's legal characterisation, securities status or tax treatment, which remain counsel determinations.

Where Wag3s fits

Wag3s HR keeps the structured, auditable record behind the chosen structure: the entities, contributor and cap-table data, and instrument terms that feed accounting and reporting, with an audit trail. The legal, securities and tax characterisation of the structure stays confirmed by counsel; Wag3s supports that determination rather than substituting for it. See the HR product page.

Further reading

• DAO Legal Wrapper Comparison
• Cayman Foundation for a Token Project
• Crypto Company Jurisdiction Guide
• Offshore Crypto Company: the Substance Myth
• Web3 Fundraising Instrument Stack
• Entity vs Personal Wallet Separation

Sources

The operating-company / foundation / token pattern is a structuring practice rather than a single codified rule, so there is no one official authority to cite for it. The points below are descriptive context to confirm with counsel.

• Web3 projects are commonly structured as an operating company (build and employ) plus a foundation or DAO wrapper (protocol/IP, regulator interface, liability shield) plus a token (a distinct instrument). The functions are distinct and the structure is fact-specific.
• The liability driver is the Samuels v. Lido DAO matter, in which a US federal court applying California law indicated an unwrapped DAO could be treated as a general partnership, exposing participants to personal liability. The analysis is jurisdiction- and fact-specific.
• The token-issuer entity and its jurisdiction are a securities- and tax-counsel determination; the structure interacts with the fundraising stack and the cap table and is best sequenced before issuance and fundraising.
• "Offshore equals no tax" is false: economic substance, CFC regimes, place-of-effective-management tests and the founders' own tax residency apply regardless of where an entity is registered. Confirm with legal and tax counsel per jurisdiction; this is not legal or tax advice.