> 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-reference/contracts.md).

# Core contracts

Contract roles, as implemented in [`cybercorps-contracts`](https://github.com/MetaLex-Tech/cybercorps-contracts) (`develop`). Each core contract carries its own `DEPLOY_VERSION` constant (currently `"4"` for most, `"4.1"` for IssuanceManager, `"4.0.1"` for DealManager) — see the individual pages.

```mermaid
flowchart TD
    F["CyberCorpFactory"] --> AUTH["BorgAuth<br/>(numeric-level authority)"]
    F --> CORP["CyberCorp<br/>(the onchain entity)"]
    F --> IM["IssuanceManager"]
    F --> DM["DealManager<br/>(deals + secondary offers)"]
    F --> RM["RoundManager<br/>(fundraising rounds)"]
    IM -- "each printer represents<br/>a security class / series" --> LET["LedgerEntryToken printers<br/>(cyberCERTs, ERC-721)"]
    IM -. "optional — deployCyberScrip,<br/>at most one per printer" .-> SCRIP["CyberScrip<br/>(ERC-20 scrip)"]
    DM --- REG["CyberAgreementRegistry<br/>(templates + signed agreements)"]
    RM --- REG
    AUTH -. "authorises" .-> IM
    AUTH -. "authorises" .-> DM
    AUTH -. "authorises" .-> RM
```

| Contract                                                                                  | Role                                                                                                                                                                                                                                                                            |
| ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**CyberCorp**](/protocol-reference/contracts/cybercorp.md)                               | The onchain entity. Stores the company name, type, jurisdiction, contact details, dispute-resolution default, officers, escrowed officer signatures, an optional corp-level extension, and the addresses of the IssuanceManager / DealManager / RoundManager. UUPS-upgradeable. |
| [**CyberCorpFactory**](/protocol-reference/factories.md)                                  | Deploys a cyberCORP and its full suite (BorgAuth, IssuanceManager, DealManager, RoundManager) in one call.                                                                                                                                                                      |
| [**IssuanceManager**](/protocol-reference/contracts/issuancemanager.md)                   | Issuance authority. Creates LedgerEntryToken printers, mints/assigns cyberCERTs, registers security-class designations, deploys CyberScrip, runs scripification and de-scripification, manages recertification approvals, and effectuates secondary-trade ownership changes.    |
| [**LedgerEntryToken**](/protocol-reference/contracts/ledgerentrytoken.md)                 | ERC-721 of cyberCERTs (Ledger Entry Tokens). Formerly named CyberCertPrinter; one printer per security series. Mutated by its IssuanceManager (or BorgAuth admins for administrative functions).                                                                                |
| [**CyberScrip**](/protocol-reference/contracts/cyberscrip.md)                             | ERC-20 fungible form of a security, deployed per LedgerEntryToken printer. USDC-style compliance powers (force transfer, force burn, freeze) with one-way disable toggles.                                                                                                      |
| [**CyberShares**](/protocol-reference/contracts/cybershares.md)                           | An ERC-20 share token with certificate-formation logic. Partly in-progress — see the page.                                                                                                                                                                                      |
| [**DealManager**](/protocol-reference/contracts/dealmanager.md)                           | Deal lifecycle: propose, sign, finalise, void/revoke — plus the secondary-trading venue (post/accept/cancel offers, settlement escrows, exemption pathways). Built on the agreement registry.                                                                                   |
| [**RoundManager**](/protocol-reference/contracts/roundmanager.md)                         | Multi-investor fundraising rounds: create, submit EOIs, allocate, reject/recall, close.                                                                                                                                                                                         |
| [**LeXscroWLite**](/protocol-reference/contracts/lexscrowlite.md)                         | The escrow layer used at deal/round close. Implemented as the `LexScrowStorage` library shared by DealManager and RoundManager — see the page.                                                                                                                                  |
| [**CyberAgreementRegistry**](/protocol-reference/contracts/cyberagreementregistry.md)     | Onchain registry of agreement templates and executed, multi-party-signed contracts, with signing delegation and void-request tracking.                                                                                                                                          |
| [**SafeCertificateConverter**](/protocol-reference/contracts/safecertificateconverter.md) | Computes a SAFE→equity conversion plan from round data. **Currently a stub.**                                                                                                                                                                                                   |
| [**LexChex / LeXcheXBadge**](/protocol-reference/contracts/lexchex.md)                    | ERC-5484 soulbound credentials: the legacy LeXcheX accreditation NFT and the unified LeXcheXBadge credential registry.                                                                                                                                                          |
| [**CertificateUriBuilder**](/protocol-reference/contracts/certificateuribuilder.md)       | Builds the onchain JSON + SVG token URI for cyberCERTs.                                                                                                                                                                                                                         |

See [Factories](/protocol-reference/factories.md) for the specialised factories (PumpCorp, MetaDAO, ParentCo).


---

# 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-reference/contracts.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.