> 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/protocol-tutorials/incorporate-a-cybercorp.md).

# Incorporate a cyberCORP

In this tutorial you deploy a new cyberCORP, create a certificate printer for its Common Stock, and issue the first cyberCERT to a founder.

At the end you will have a `CyberCorp` and its suite (`IssuanceManager`, `DealManager`, `RoundManager`, plus a `BorgAuth` ACL), one certificate printer for Common Stock, and one cyberCERT held by the founder.

> **Naming note:** the certificate printer contract is now called `LedgerEntryToken` in the source (formerly `CyberCertPrinter`). The rename is source-level only — the ABI and storage layout are unchanged, and the docs still say "cert printer" for the deployed instances.

> Code here is **illustrative of the flow** and uses the real contract signatures from `cybercorps-contracts` (`develop`). Confirm structs and parameters against the source before deploying.

## 1. Deploy the cyberCORP

New cyberCORPs are deployed by the **`CyberCorpFactory`**. A single `deployCyberCorp` call deploys the BorgAuth ACL and the whole suite.

```solidity
import {CompanyOfficer} from "src/CyberCorpConstants.sol";

CyberCorpFactory factory = CyberCorpFactory(FACTORY_ADDR);

CompanyOfficer memory officer = CompanyOfficer({
    eoa:     founder,
    name:    "Jane Founder",
    contact: "jane@acme.example",
    title:   "Chief Executive Officer"
});

(
    address cyberCorp,
    address auth,
    address issuanceManager,
    address dealManager,
    address roundManager
) = factory.deployCyberCorp(
    keccak256("acme-cyberco-v1"),     // salt (must be non-zero)
    "Acme CyberCo, Inc.",            // companyName
    "corporation",                   // companyType (free-form text)
    "Delaware",                      // companyJurisdiction
    "legal@acme.example",            // companyContactDetails
    "Delaware Court of Chancery",     // defaultDisputeResolution
    founder,                          // companyPayable
    officer
);
```

The factory grants the founder BorgAuth role `200` (officer) and grants the IssuanceManager / DealManager / RoundManager role `99`. See [Access control](/protocol-reference/access-control.md). It emits `CyberCorpDeployed`.

## 2. Create a Common Stock certificate printer

The `IssuanceManager` creates one cert printer (`LedgerEntryToken`) per security series.

```solidity
import {SecurityClass, SecuritySeries} from "src/CyberCorpConstants.sol";

string[] memory legend = new string[](1);
legend[0] = "These securities have not been registered under the Securities Act of 1933...";

address commonPrinter = IIssuanceManager(issuanceManager).createCertPrinter(
    legend,                       // default legend
    "Acme CyberCo Common Stock",  // name
    "ACME-CS",                    // ticker
    "ipfs://acme-cert-art",       // certificate URI
    SecurityClass.CommonStock,
    SecuritySeries.NA,
    SHARE_EXTENSION_ADDR,         // certificate extension for this series
    ""                            // seriesData — extension-encoded series-scope
                                  // payload; empty when the extension has none
);
```

## 3. Issue the genesis cyberCERT

Mint a cyberCERT to the founder with `createCertAndAssign`. The metadata is a `CertificateDetails` struct (defined in [`ILedgerEntryToken.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/interfaces/ILedgerEntryToken.sol)).

```solidity
import {CertificateDetails} from "src/interfaces/ILedgerEntryToken.sol";

CertificateDetails memory details = CertificateDetails({
    signingOfficerName:                  "Jane Founder",
    signingOfficerTitle:                 "Chief Executive Officer",
    investmentAmountUSD:                 0,
    issuerUSDValuationAtTimeOfInvestment: 0,
    unitsRepresented:                    8_000_000e18, // 8,000,000 shares (18-decimal)
    legalDetails:                        "Founder common stock",
    extensionData:                       ""   // ABI-encoded per the extension
});

uint256 tokenId = IIssuanceManager(issuanceManager).createCertAndAssign(
    commonPrinter,
    founder,
    details
);
```

`createCertAndAssign` mints the ERC-721 *and* records the founder as the registered owner. (`createCert` mints without assigning a registered owner; other `createCert*` variants also attach a name, an endorsement, or a signature — see [IssuanceManager](/protocol-reference/contracts/issuancemanager.md).)

## 4. Inspect the register

```solidity
LedgerEntryToken printer = LedgerEntryToken(commonPrinter);

string  memory uri        = printer.tokenURI(tokenId);     // onchain JSON + SVG
address         tokenHolder = printer.ownerOf(tokenId);     // ERC-721 holder
address         registered  = printer.legalOwnerOf(tokenId);// registered owner of record
```

Note the two owners: `ownerOf` is the NFT holder; `legalOwnerOf` is the registered owner of record. They are kept distinct on purpose — see [The dual-token model](/protocol-explanation/dual-token-model.md).

## What you just did

* Deployed a cyberCORP and its full contract suite in one call.
* Created a Common Stock certificate printer.
* Issued the first register entry as a cyberCERT.

## Next

* [Run a cyberRAISE round](/protocol-tutorials/run-a-cyberraise-round.md).
* Reference: [IssuanceManager](/protocol-reference/contracts/issuancemanager.md), [LedgerEntryToken](/protocol-reference/contracts/ledgerentrytoken.md).


---

# 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/protocol-tutorials/incorporate-a-cybercorp.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.