> 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/building-on-the-protocol/how-to/deploy-metadao-spc.md). # Deploy a MetaDAO SPC Deploy a futarchy-governed Cayman segregated portfolio company and its SegCos through MetaDAOFactory A **MetaDAO** is a futarchy-governed entity structured as a Cayman Segregated Portfolio Company (SPC), and each of its portfolios (SegCos) has its own futarchy oracle. The **`MetaDAOFactory`** ([`src/MetaDAOFactory.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/MetaDAOFactory.sol)) deploys it. You need legal counsel familiar with Cayman SPCs and futarchy governance, and the MetaDAO Futarchy Governance templates from [`/templates`](https://github.com/MetaLex-Tech/cybercorps-contracts/tree/develop/templates/README.md) (search for `MetaDAO Futarchy Governance SPC`). ## How MetaDAOFactory deploys the SPC `MetaDAOFactory` deploys cyberCORP suites configured as an SPC-style entity through three entry points: * `createParentCorp(...)` creates the MetaDAO parent corp. Only the factory's owner can call it, and a second call reverts `ParentCorpAlreadyCreated`. * `deployMetaCorp(...)` deploys a suite (BorgAuth, CyberCorp, IssuanceManager, DealManager) with the same parameter shape as `CyberCorpFactory.deployCyberCorp`. * `deployMetaDAOContractFor(...)` deploys a SegCo suite and executes the SegCo and board-consent agreements in one transaction. It takes a `_segCoTemplateId` and `_boardConsentTempateId` (spelled that way in the source) plus the deployer officer's values and EIP-712 signature. Board-consent agreements recorded through the [CyberAgreementRegistry](/building-on-the-protocol/reference/contracts/cyberagreementregistry.md) approve each new SegCo. The deploy script ([`script/deploy-metadao-factory.s.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/script/deploy-metadao-factory.s.sol)) seeds the registry with the SegCo and Board Consent templates. The factory's full parameter lists are not reproduced here. The contract source is the authoritative reference for the MetaDAO deployment shape. See also [Factories](/building-on-the-protocol/reference/factories.md), [Agreement templates](/building-on-the-protocol/reference/templates.md), [Legal mappings](/how-cybercorps-works/legal-mappings.md), and [Launchpads](/using-the-apps/launchpads.md) for the MetaDAO formation pages in the app. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.metalex.tech/building-on-the-protocol/how-to/deploy-metadao-spc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.