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

# Security types

The instrument types the protocol can issue are the `SecurityClass` enum in [`src/CyberCorpConstants.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/CyberCorpConstants.sol). A `LedgerEntryToken` cert printer (formerly `CyberCertPrinter`) is created for a specific `SecurityClass` (and `SecuritySeries`).

## `SecurityClass`

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

## `SecuritySeries`

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

`NA` is used where a series is not applicable; `ACE` marks securities issued through an ACE offering.

## `SecurityStatus`

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

A cyberCERT's status; `Void` is set by `LedgerEntryToken.voidCert`.

## Security classes (`SecurityClassInfo`)

Class-level designations for Ledger Entry Tokens 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; classIds are sequential starting at `1` (`0` = unclassified). `setPrinterClass` assigns a cert printer (the series scope) to a class; multiple printers can share one class.

## Instrument-specific metadata

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


---

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