# Welcome

**cyberCORPs** is MetaLeX's smart-contract protocol for turning a legal entity (a Delaware C-corp or LLC, a Cayman LLC or SPC, a BVI fund, an English company, or any analogous structure) into an *onchain entity* that issues legally constitutive digital securities, maintains its register of holders, conducts fundraising rounds, and settles deals through a composable system of contracts.

In a cyberCORP, **the blockchain IS the official register** — not a pointer to one.

The protocol is entity-type and jurisdiction agnostic. Delaware C-corp stock is the most fully worked-out reference implementation. LLC membership interests, LP interests, segregated-portfolio-company shares, and non-US equity all flow through the same primitives.

Live on **Ethereum mainnet**, **Arbitrum**, and **Base**.

## How this documentation is organised

This book has two parts.

**Part 1 — Protocol** documents the smart contracts ([`cybercorps-contracts`](https://github.com/MetaLex-Tech/cybercorps-contracts)). It follows the [Diátaxis](https://diataxis.fr/) framework:

| Section                                                              | When to read it                                                  |
| -------------------------------------------------------------------- | ---------------------------------------------------------------- |
| [**Tutorials**](/metalex-docs/protocol-tutorials/tutorials.md)       | You're new and want to *learn by doing*. Start here.             |
| [**How-to Guides**](/metalex-docs/protocol-how-to-guides/how-to.md)  | You have a specific goal and want a recipe.                      |
| [**Reference**](/metalex-docs/protocol-reference/reference.md)       | You need the dry technical facts (contract APIs, roles, events). |
| [**Explanation**](/metalex-docs/protocol-explanation/explanation.md) | You want to *understand why* the protocol is the way it is.      |

**Part 2 — Web App** is for people *using* the cyberCORPs apps — issuers, investors, and token communities. No code, no setup: just what each app does and how to use it.

| Guide                                                                       | For                                                   |
| --------------------------------------------------------------------------- | ----------------------------------------------------- |
| [Using the cyberCORPs apps](/metalex-docs/web-app-using-the-apps/webapp.md) | Everyone — start here.                                |
| [The Mainframe](/metalex-docs/web-app-using-the-apps/mainframe.md)          | Issuers managing their cyberCORP.                     |
| [cyberRAISE](/metalex-docs/web-app-using-the-apps/cyberraise.md)            | Issuers raising capital; investors funding rounds.    |
| [ACE](/metalex-docs/web-app-using-the-apps/ace.md)                          | Token communities converting to equity; investors.    |
| [LeXcheX](/metalex-docs/web-app-using-the-apps/lexchex.md)                  | Anyone who needs to prove accredited-investor status. |
| [MetaDAO](/metalex-docs/web-app-using-the-apps/metadao.md)                  | Participants in futarchy-governed entities.           |

## The two-minute version

1. A **cyberCORP** is an onchain entity whose constitutional documents designate the onchain contract system as the entity's official register of holders.
2. A **cyberCERT** (ERC-721) is a *Ledger Entry Token* — a single entry on that register.
3. A **cyberSCRIP** (ERC-20) is the *fungible* form of that same security, minted from a cyberCERT and convertible back.
4. A growing **application stack** runs on this single contract suite — **cyberRAISE**, **cyberTRADE**, **ACE**, **LiquiLeX**, **cyberSign** — all surfaced through the cyberCORPs **Mainframe**. Part 2 explains how to use them.

## Protocol repository

[github.com/MetaLex-Tech/cybercorps-contracts](https://github.com/MetaLex-Tech/cybercorps-contracts)


---

# Agent Instructions: 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:

```
GET https://gabriel-j-shapiro.gitbook.io/metalex-docs/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.