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

# Security types

The `SecurityClass` enum in [`src/CyberCorpConstants.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/CyberCorpConstants.sol) lists the instrument types the protocol can issue. Each LET contract (a `LedgerEntryToken` deployment) is created for one `SecurityClass` and one `SecuritySeries`.

## `SecurityClass`

```solidity
enum SecurityClass {
    SAFE,
    SAFT,
    SAFTE,
    TokenPurchaseAgreement,
    TokenWarrant,
    ConvertibleNote,
    CommonStock,
    StockOption,
    PreferredStock,
    RestrictedStockPurchaseAgreement,
    RestrictedStockUnit,
    RestrictedTokenPurchaseAgreement,
    RestrictedTokenUnit,
    MembershipInterest,
    SAFO
}
```

New values are appended, so the values 0 to 12 keep their meaning. A deployed contract decodes only the values that it was compiled with. Before you use `MembershipInterest` (13) or `SAFO` (14), verify the target company's deployed component versions. Native SAFO issuance also needs the coordinated SAFO component upgrades and template registration in the [SAFO extension specification](https://github.com/MetaLex-Tech/cybercorps-contracts/tree/develop/docs/reference/safo-extension.md#validation-limits-and-release-gates).

## `SecuritySeries`

```solidity
enum SecuritySeries {
    SeriesPreSeed,
    SeriesSeed,
    SeriesA,
    SeriesB,
    SeriesC,
    SeriesD,
    SeriesE,
    SeriesF,
    NA,
    ACE
}
```

`NA` marks a security with no series; `ACE` marks securities issued through an ACE offering.

## `SecurityStatus`

```solidity
enum SecurityStatus { Unassigned, Assigned, Void }
```

The status of a Ledger Entry Token (LET). `LedgerEntryToken.voidCert` sets `Void`, and the IssuanceManager calls it when it voids an emptied LET (`voidEmptyCerts`, or a seller's LET fully sold in a secondary trade). A void LET keeps its holder and units but cannot be registered to a new holder.

## Security classes (`SecurityClassInfo`)

Class-level designations for LETs are registered on the `IssuanceManager`:

```solidity
struct SecurityClassInfo {
    SecurityClass classType;
    string documentURI;    // class-level governing document
    address dataExtension; // optional ICertificateExtension-style decoder/renderer
    bytes classData;       // extensionData-style opaque payload
}
```

`IssuanceManager.defineSecurityClass` (`onlyOwner`) registers a class. Each `SecurityClass` value has at most one class, and several LET contracts can share it. The [IssuanceManager](/building-on-the-protocol/reference/contracts/issuancemanager.md#security-class-registry) page covers class ids, assignment and updates. `ShareExtensionV3` reads `classData` as the class-wide layer of every LET in a share class; see [Certificate extensions](/building-on-the-protocol/reference/extensions.md).

## Instrument-specific metadata

Each security class is paired with a [certificate extension](/building-on-the-protocol/reference/extensions.md) that encodes its instrument-specific terms. `CyberCorpConstants.sol` also defines supporting enums for token-warrant and vesting instruments: `ExercisePriceMethod`, `TokenCalculationMethod`, `UnlockStartTimeType`, `UnlockingIntervalType`.


---

# 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/security-types.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.