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

# Welcome

Private securities recorded as Ledger Entry Tokens, anchored in each issuer's governing law, and the MetaLeX apps that run on them.

cyberCORPs is MetaLeX's smart-contract protocol for keeping a company's securities onchain, together with the apps built on it. A company joins as a **cyberCORP**: its governing documents designate the protocol's contracts as the register for the shares they tokenize, and those contracts issue its securities, record transfers, run fundraising rounds and settle trades. For those shares the onchain record is the register itself, and the tokens do not point at a register kept somewhere else.

The protocol works for any entity type and jurisdiction. Delaware C-corp stock is the most complete implementation, and LLC membership interests, LP interests, segregated portfolio company shares and non-US equity use the same contracts. The apps support Ethereum, Base, Arbitrum and selected workflows on Robinhood Chain. [Network availability](/using-the-apps/webapp.md#network-availability) depends on the workflow and the targeted company’s deployed contracts.

## Core terms

* A **cyberCORP** is the company's onchain presence: its `CyberCorp` contract plus the managers that issue its securities, run its rounds and settle its deals.
* A **Ledger Entry Token (LET)** is an ERC-721 token that records one entry on the register: who holds how many units of which class or series, on what terms and restrictions. Each class or series has its own **LET contract**.
* **Scrip** is a fungible ERC-20 token that tracks a LET's units in a fixed ratio. A holder moves units from a LET into scrip and can convert scrip back into a LET. The rights scrip carries come from the company's governing documents and the scrip's terms: under MetaLeX-form bylaws, scrip is not stock and gives no stockholder rights on its own.
* **cyberSign** supports onchain, fully offchain and mixed execution. Its onchain flows record agreements in the `CyberAgreementRegistry`. When a party signs directly (`signContract`, `signContractFor`), the registry verifies the party's EIP-712 signature. When an agreement's finalizer, such as a DealManager, submits a signature it holds in escrow (`signContractWithEscrow`), the registry checks only that the finalizer sent the call. Rounds, deals and trades are signed there.

[Ledger Entry Tokens and scrip](/how-cybercorps-works/lets-and-scrip.md) explains how the two forms relate, and the [glossary](/building-on-the-protocol/reference/glossary.md) defines the rest.

## How this book is organized

| Part                         | Written for                                                                | Start with                                                                                                  |
| ---------------------------- | -------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Using the apps**           | Founders, officers, investors and holders using the MetaLeX apps. No code. | [Getting started](/using-the-apps/webapp.md)                                                                |
| **How cyberCORPs works**     | Anyone evaluating the model: lawyers, investors, integrators.              | [Constitutive vs. pointer tokenization](/how-cybercorps-works/constitutive-vs-pointer.md)                   |
| **Building on the protocol** | Developers integrating with or extending the contracts.                    | [Guides](/building-on-the-protocol/how-to.md), then the [reference](/building-on-the-protocol/reference.md) |

## What runs on the protocol

| Product            | What it does                                                                                                           | Guide                                                                              |
| ------------------ | ---------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **cyberCORPs app** | Form a company or bring an existing one onchain, then run its cap table, board, grants and securities.                 | [Run your company](/using-the-apps/company.md)                                     |
| **cyberRAISE**     | Primary fundraising rounds: SAFEs, SAFTs, SAFTEs, token warrants and priced equity.                                    | [cyberRAISE](/using-the-apps/cyberraise.md)                                        |
| **ACE**            | Rounds paid in a token community's own token.                                                                          | [ACE](/using-the-apps/ace.md)                                                      |
| **cyberSign**      | Propose and sign agreements with public or private documents and a stated onchain, offchain or mixed execution policy. | [cyberSign](/using-the-apps/cybersign.md)                                          |
| **LeXcheX**        | Accredited-investor and compliance credentials attached to a wallet.                                                   | [LeXcheX](/using-the-apps/lexchex.md)                                              |
| **cyberTRADE**     | Settlement of negotiated secondary trades under an elected exemption pathway.                                          | [Run a secondary trade](/building-on-the-protocol/how-to/run-a-secondary-trade.md) |
| **LiquiLeX**       | Uniswap v4 liquidity pools for scrip.                                                                                  | [Deploy a LiquiLeX pool](/building-on-the-protocol/how-to/deploy-liquilex-pool.md) |

## Source code

The contracts are in [MetaLex-Tech/cybercorps-contracts](https://github.com/MetaLex-Tech/cybercorps-contracts), and the apps in [MetaLex-Tech/metalex-webapp](https://github.com/MetaLex-Tech/metalex-webapp).

Reviewed against contract and webapp source on **November 4, 2026**. See [Documentation status and source review](/building-on-the-protocol/reference/documentation-status.md) for the prior update dates, inspected revisions and deployment limits.


---

# 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/readme.md?ask=<question>&goal=<user_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.