> 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/reference/glossary.md). # Glossary | Term | Meaning | | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ACE (Asset Conversion to Equity)** | MetaLeX's product for converting a token community into equity stakeholders, at [ace.metalex.tech](https://ace.metalex.tech). Built on `PumpCorpFactory` and `ACESAFEExtension`. See [ACE](/using-the-apps/ace.md). | | **Agreement id** | The `bytes32` id of an agreement in `CyberAgreementRegistry`: a deal, an EOI, a secondary settlement, or a standalone cyberSign agreement. On Ethereum, Base and Arbitrum the registry derives it from the template id, salt, global values, parties, secret hash and finalizer; the zkSync Era registry uses only the first four. See [CyberAgreementRegistry](/building-on-the-protocol/reference/contracts/cyberagreementregistry.md). | | **BorgAuth** | MetaLeX's role-based access control framework. Each cyberCORP has its own BorgAuth with numeric role levels. See [Access control](/building-on-the-protocol/reference/access-control.md) and [borg-core](https://github.com/MetaLex-Tech/borg-core). | | **Cap table** | The ownership record the cyberCORPs app assembles, displays and exports: every position from every source (offchain entries, LETs, scrip) in one view. It is an app record. Whether it, the chain or another record is the company's *securities ledger* depends on the company's governing documents. See [The cap table](/using-the-apps/company/captable.md). | | **Constitutive tokenization** | Token issuance where the entity's governing documents designate the onchain record as the official register, so the chain *is* the register. Contrast with pointer tokenization. | | **cyberCORP** | An onchain legal entity that issues legally constitutive digital securities through this protocol. | | **cyberCORPs app** | MetaLeX's issuer-facing app at `cybercorps.metalex.tech`. A company's sidebar sections are **mission control**, **Incorporation Hub**, **Documents**, **boardRoom**, **capTable**, **grants**, **cyberRaise**, **Tokenization Hub** and **cyberSign**. See [Run your company](/using-the-apps/company.md). | | **cyberRAISE** | Onchain primary fundraising, built on `RoundManager`, `DealManager` and the LeXscroWLite escrow (`LexScrowStorage`). The cyberCORPs app's sidebar entry for it reads **cyberRaise**. See [cyberRAISE](/using-the-apps/cyberraise.md). | | **cyberSign** | MetaLeX's app for signing and executing legal agreements, built on `CyberAgreementRegistry`. See [cyberSign](/using-the-apps/cybersign.md). | | **cyberTRADE** | Settlement for negotiated secondary trades of private securities, through the `DealManager` offer and acceptance flow (with an elected exemption pathway) and the LeXscroWLite escrow. | | **DGCL** | Delaware General Corporation Law, the most fully worked-out statutory reference for the protocol. | | **Documents** | The cyberCORPs app section that collects a company's formation mail, notices and filings, with links to the boardRoom's governance documents and to cyberSign. See [Run your company](/using-the-apps/company.md). | | **Endorsement** | A signed record on a LET naming an endorser and an endorsee, optionally bound to an agreement registry and agreement id. An issuance endorsement names the first holder. Title moves to a new holder of record only on delivery to the endorsee of the latest live endorsement. See [LedgerEntryToken](/building-on-the-protocol/reference/contracts/ledgerentrytoken.md). | | **EOI (Expression of Interest)** | An EIP-712-signed message in which an investor declares intent to take part in a cyberRAISE round on stated terms. | | **Exemption pathway** | The securities-law exemption a secondary trade settles under (`RULE_144`, `SECTION_4A7`, `SECTION_4A1HALF`, `RULE_144A` or `REGULATION_S`), elected per trade and enforced by per-pathway [condition](/building-on-the-protocol/reference/conditions.md) sets on the `DealManager`. | | **Holder of record** | The address registered as a LET's legal owner (`legalOwnerOf`). It can differ from the wallet in possession of the token (`ownerOf`). | | **Incorporation Hub** | The cyberCORPs app section that holds a company's onchain formation record and founding documents, plus the private state formation record for a company formed through the app. See [Run your company](/using-the-apps/company.md). | | **Ledger Entry Token (LET)** | An ERC-721 token minted by a LET contract. Each LET is one entry on a cyberCORP's register of holders, recording the holder of record, units and details of one position. Its onchain image renders the certificate. See [LedgerEntryToken](/building-on-the-protocol/reference/contracts/ledgerentrytoken.md) and [LETs and scrip](/how-cybercorps-works/lets-and-scrip.md). | | **Legal terms** | The legal class, series and versioned terms recorded behind a security class in the cyberCORPs app. One current officer wallet approves an exact version before it activates, and the cap table and its exports read the activated version. See [The cap table](/using-the-apps/company/captable.md). | | **LET contract** | The `LedgerEntryToken` deployment that mints a class's or series' LETs. Each class or series has its own LET contract, created by the company's IssuanceManager (`createCertPrinter`). | | **LeXcheX** | MetaLeX's onchain accreditation and KYC/AML credential system: soulbound, wallet-bound NFT credentials. See [LeXcheX](/using-the-apps/lexchex.md). | | **LeXcheXBadge** | The unified soulbound credential registry (LeXcheX v2, `src/creds/lexchexBadge.sol`): fact-keyed credential attributes with expiries, read by the badge-scoped secondary-trading [conditions](/building-on-the-protocol/reference/conditions.md). | | **LeXscroWLite** | The atomic deal-closing escrow, implemented as the `LexScrowStorage` library linked into `DealManager` and `RoundManager`. See [LeXscroWLite](/building-on-the-protocol/reference/contracts/lexscrowlite.md). | | **LiquiLeX** | AMM-native secondary liquidity for scrip, using Uniswap v4 pools and the `MetalexIssuerFeeHook`. See [Deploy a LiquiLeX pool](/building-on-the-protocol/how-to/deploy-liquilex-pool.md). | | **MetaDAO** | A futarchy-governed token launchpad that prescribes the legal entity a project uses: a segregated portfolio of a Cayman Islands segregated portfolio company. `MetaDAOFactory` deploys the structure, and the cyberCORPs app has a formation page for it. See [Launchpads](/using-the-apps/launchpads.md). | | **mission control** | The cyberCORPs app's company dashboard. It shows what is true about the company now and what needs action, such as contract upgrades, formation steps, annual reports and cap table checks. See [Run your company](/using-the-apps/company.md). | | **Pointer tokenization** | Token issuance where the chain is a notification layer and the official register lives offchain. Contrast with constitutive tokenization. | | **Public company page** | A wallet-free page for every cyberCORP at `cybercorps.metalex.tech/company/{chainId}/{address}`, showing what the chain and the public indexer record about it. See [Run your company](/using-the-apps/company.md). | | **PumpCorp** | A cyberCORP variant deployed by `PumpCorpFactory` for ACE. | | **Reg D / Reg S** | Two exemption frameworks for private securities under the US Securities Act of 1933. Reg D is the US-investor framework (accreditation-driven); Reg S is the non-US-investor framework. | | **Scrip** | A fungible ERC-20 token that tracks a LET's units in a fixed ratio; a holder converts LET units into scrip and back. Its rights come from the company's governing documents and the scrip's terms; under MetaLeX-form bylaws scrip is not stock and confers no stockholder rights on its own. Each LET contract has at most one `CyberScrip` contract. See [Tokenization Hub](/using-the-apps/company/tokenization-hub.md) and [CyberScrip](/building-on-the-protocol/reference/contracts/cyberscrip.md). | | **Scripification** | Converting units of a LET into scrip (`scripifyCert`). De-scripification converts scrip back into a LET (`convertScripToCert`). | | **Securities ledger** | The company's legally definitive record of its securities. Which record that is (the chain, the app's cap table, or something else) depends on the company's governing documents, such as its bylaws; it never follows from tokenization or from where data is stored. | | **SegCo** | A segregated portfolio of a Cayman Islands segregated portfolio company (SPC). | | **Tokenization Hub** | The cyberCORPs app section that configures, issues and manages the company's LETs and scrip. Reference UI at [`apps/cybercorps-web`](https://github.com/MetaLex-Tech/metalex-webapp/tree/develop/apps/cybercorps-web). See [Tokenization Hub](/using-the-apps/company/tokenization-hub.md). | | **Tokenized / untokenized** | Whether units have a token onchain (a LET or scrip). Says nothing about where a record is stored or which record is definitive. | | **Umia** | A token launchpad that, like MetaDAO, prescribes the legal entity a project uses: a segregated portfolio of Umia Launcher SPC. The cyberCORPs app has a password-protected formation page for it. See [Launchpads](/using-the-apps/launchpads.md). | | **Unregistered scrip** | Scrip in a holder's wallet beyond what recorded grants' withdrawals explain: beneficial units with no registered position accounting for them. The cyberCORPs app flags it for review. | | **zkPassport** | Privacy-preserving passport credential used by `NonUSNationalityCondition`. | --- # 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/reference/glossary.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.