Web3 Company Legal Structure: Operating Company, Foundation, Token

Founders ask "where do I incorporate?" as if the answer is one company in one country. A Web3 project is usually a structure: an operating company that builds, a foundation or wrapper that holds the protocol and shields participants, and a token. The cost of getting it wrong is concrete — an unwrapped DAO can be a general partnership. This guide is the structure map, heavily hedged, because every line of it is a counsel question.

TL;DR

• A Web3 project is usually not one entity: operating company (builds, employs) + foundation/wrapper (protocol/IP, regulators, liability shield) + token (its own instrument).
• Unwrapped DAO risk: in Samuels v. Lido DAO a US federal court (California law) indicated an unwrapped DAO could be a general partnership → participant personal liability.
• Which entity issues the token, and where, is a securities/tax counsel decision — no universal answer.
• "Offshore = no tax" is false — economic substance, CFC rules, place of effective management, and the founders' own tax residence all bite.
• Decide the structure before token issuance / fundraising — it interacts with the fundraising stack and cap table.
• Fact-specific, substance-dependent, jurisdiction-specific — confirm with legal and tax counsel per jurisdiction. Not legal/tax advice.

Three functions, often three entities

The functions are distinct; 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

The reason 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 is jurisdiction- and fact-specific and must be assessed with counsel — but the exposure of going unwrapped is real, and it is the wake-up call behind 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: equity and token ledgers sit in (potentially) different entities.

The "offshore = 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 bite 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 (e.g. 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 — not 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 token-issuer entity and jurisdiction with securities + tax counsel — no template.
4. Treat "offshore" as a substance/compliance question, never an automatic tax saving.
5. Sequence structure before fundraising/issuance — it constrains the stack and cap table.
6. Confirm with legal and tax counsel per jurisdiction — fact-specific; not legal/tax advice.

How vendor tools handle the structure

Pulley and Carta record entities, cap tables and instruments (Pulley covers token + equity; Carta equity broadly) and can model the structure's ownership and dilution. They record and model the structure — they do not determine its legal characterisation, securities status or tax treatment, which remain counsel determinations.

How Wag3s helps

Wag3s HR keeps the structured, auditable record behind the chosen structure — entities, contributor and cap-table data, instrument terms — feeding accounting and reporting with an audit trail, while the legal, securities and tax characterisation of the structure stays counsel-confirmed. 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

• Web3 projects commonly structured as operating company (build/employ) + foundation or DAO wrapper (protocol/IP/regulator/liability) + token (distinct instrument) — functions distinct, structure fact-specific
• Samuels v. Lido DAO (2024) — US federal court applying California law indicated an unwrapped DAO could be treated as a general partnership, exposing participants to personal liability (jurisdiction- and fact-specific)
• Token-issuer entity/jurisdiction is a securities- and tax-counsel determination; structure interacts with the fundraising stack and cap table and should be sequenced before issuance/raise
• "Offshore = no tax" is false — economic substance, CFC regimes, place of effective management and founders' own tax residency apply regardless of registry; not legal/tax advice, confirm per jurisdiction