> For the complete documentation index, see [llms.txt](https://docs.metalex.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.metalex.tech/web-app-using-the-apps/metadao.md).

# MetaDAO — entity formation

The **MetaDAO** page is a narrow, single-purpose integration: it forms the legal entity for a token launched through [MetaDAO](https://metadao.fi). It is **not** a governance or prediction-market surface — it does one thing, once.

## When you'd use it

You would not navigate to this page directly. You arrive at it from the **MetaDAO launch flow**, via a link that carries the details of your token and enterprise. Opening the page without those details just shows an error.

## What it does

The page presents a **formation agreement** for your entity — specifically a *Segregated Portfolio of a Futarchy Governance SPC*, a Cayman Islands structure. Almost every field is **pre-filled and locked**, carried over from the MetaDAO form:

* the enterprise and company name,
* the company type (a segregated portfolio of a segregated portfolio company),
* the jurisdiction (Cayman Islands),
* the token name and ticker,
* the founder/operator address (set to the wallet you connect),
* the network (Base).

The only fields you fill in are the **founder/operator name and contact details**. The agreement itself is shown alongside the form for review.

## The steps

1. Arrive from the MetaDAO launch flow (the page opens with your details already populated) and **connect your wallet** — it becomes the operator address.
2. Enter the founder/operator name and contact details.
3. **Sign the formation agreement** — a free signature.
4. **form cyberCORP.** MetaLeX submits the formation transaction and pays the gas — you pay nothing.
5. A **Formation Summary** page confirms the cyberCORP was minted: the entity's details, the operator account, the network, and links to the executed **Formation Agreement** and **Board Resolutions**. Bookmark it — then **Back to MetaDAO** returns you to continue the launch.

Right after formation the summary data can lag the chain by a minute; if so, the page says the summary is still syncing and asks you to refresh — the formation itself has already succeeded.

That's the whole flow. Once the entity is formed, you manage it like any other cyberCORP — see [The cyberCORPs app](/web-app-using-the-apps/mainframe.md).

## Under the hood

Submitting forms a cyberCORP structured as a Cayman Segregated Portfolio Company, and anchors two documents: the formation agreement and the board resolutions. At the protocol level this is the **MetaDAO / SPC** path — see the [MetaDAOFactory](/protocol-reference/factories.md) reference and, for how a single legal entity can hold multiple independently-governed portfolios, [Legal mappings across jurisdictions](/protocol-explanation/legal-mappings.md). The futarchy *governance* of the entity happens on MetaDAO's own platform; this page only handles the onchain legal-entity formation.

## Good to know

* This page is a **handoff**, not an app you spend time in.
* **Formation costs you no gas** — MetaLeX submits the transaction.
* For everything you do *after* formation — issuing securities, raising — you use the [cyberCORPs app](/web-app-using-the-apps/mainframe.md) and [cyberRAISE](/web-app-using-the-apps/cyberraise.md) like any other company.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.metalex.tech/web-app-using-the-apps/metadao.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.