Web3 Entity Setup

A common pattern in Web3 is to split responsibilities across three entities so the project can be both "protocol-like" and still function like a normal business. The idea is simple: keep the day-to-day operating company separate from the governance and treasury layer, and ring-fence the riskiest activity (token issuance) into its own vehicle.

This separation helps with credibility (the protocol isn't "owned" by one cap table), risk management (token issuance liabilities don't contaminate everything else), and practicality (you can still hire, contract, and raise equity in a conventional way).

Token Issuance SPV is a purpose-built vehicle used to run the token generation/distribution mechanics and isolate the legal, regulatory, and civil risk that tends to cluster around token issuance. Its raison d'être is containment: if token-related issues arise, they are structurally kept away from the protocol steward and the operating business.

Governing Entity (Foundation) is the long-term steward of the protocol layer. It typically holds or controls key protocol rights and treasury assets, sets grant policies, and acts as the real-world counterparty for governance decisions.Its purpose is neutrality and continuity: it provides an accountable legal wrapper for the protocol without looking like a shareholder-owned company that "owns" the network.

Operating Company is the normal startup: it employs the team, signs customer and vendor contracts, builds and ships product, and can raise equity using familiar structures. It is usually funded via a services agreement and/or grants from the governing entity (and sometimes equity investment). Its reason for being is execution: it lets the project operate efficiently in the real world without entangling the protocol's governance and treasury with ordinary commercial activities.

These jurisdictions are common not because they are "magic", but because they are familiar, serviceable defaults for global teams.

BVI is often used for the token SPV because it's a widely understood offshore company form with mature professional infrastructure for simple SPVs and holding structures.

Cayman is often used for the governing foundation because foundation companies are a well-trodden tool for protocol stewardship and are broadly legible to international counsel and institutional counterparties.

A US operating company is common because it's practical: hiring, contracting, equity fundraising, and day-to-day operations tend to be simplest in an onshore, well-understood corporate environment—especially for teams, investors, vendors, and banks that already know how to work with US entities.