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

# CyberScrip

The ERC-20 fungible form of a cyberCORP security. One CyberScrip is deployed per [LedgerEntryToken](/protocol-reference/contracts/ledgerentrytoken.md) printer, via `IssuanceManager.deployCyberScrip`.

* **Source:** [`src/CyberScrip.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/CyberScrip.sol)
* **Inherits:** `ERC20Upgradeable`, `BorgAuthACL`
* **Pattern:** beacon proxy
* **`DEPLOY_VERSION`:** `"4"`

Scripification and de-scripification are driven through the IssuanceManager, so `mint` / `burnFrom` are `onlyIssuanceManager`. The compliance controls are `onlyIssuanceManagerOrAdmin`, so a cyberCORP admin calls them on the scrip directly.

## Mint / burn

```solidity
function mint(address to, uint256 amount) external onlyIssuanceManager;
function burnFrom(address account, uint256 amount) external onlyIssuanceManager;
```

## Compliance powers

CyberScrip supports **three** compliance powers. There is **no blocklist**.

| Power          | Function                          | Gate             | Enabled at deploy by  | Disable (one-way)        |
| -------------- | --------------------------------- | ---------------- | --------------------- | ------------------------ |
| Force transfer | `forceTransfer(from, to, amount)` | manager or admin | `enableForceTransfer` | `disableForceTransfer()` |
| Force burn     | `forceBurn(account, amount)`      | manager only     | `enableForceBurn`     | `disableForceBurn()`     |
| Freeze         | `setFrozen(account, isFrozen)`    | manager or admin | `enableFreeze`        | `disableFreeze()`        |

Each `disable*` function is irreversible — once a power is disabled it cannot be re-enabled. A power can only be exercised while its `can*` flag is true; otherwise the call reverts `ComplianceFeatureDisabled`.

Since every one of these functions is `onlyIssuanceManager`, officers and admins exercise them through the IssuanceManager's wrappers (`forceScripTransfer`, `forceScripBurn`, `setScripFrozen`, `setScripRestrictionHooks`, `disableScripForceTransfer` / `disableScripForceBurn` / `disableScripFreeze`) — see [IssuanceManager](/protocol-reference/contracts/issuancemanager.md).

## Transfer restrictions

`setRestrictionHook(ITransferRestrictionHook[])` installs an array of [transfer hooks](/protocol-reference/hooks.md). Every transfer runs each hook's `checkTransferRestriction`; a `false` result reverts `RestrictedTransfer`. Frozen accounts (when `canFreeze`) revert `AccountFrozen`.

## Holder cap

`setMaxHolderCount(uint256)` sets a maximum holder count (`0` = unlimited). Transfers that would exceed it revert `HolderLimitExceeded`.

{% hint style="warning" %}
The setter is `onlyIssuanceManager`, and the IssuanceManager currently exposes no wrapper that calls it — so on production deployments the cap remains at its default `0` (unlimited).
{% endhint %}

## Views

`certPrinter`, `issuanceManager`, `transferRestrictionHooks(i)`, `transferRestrictionHooksLength`, `canForceTransfer`, `canForceBurn`, `canFreeze`, `frozen(account)`, `holderCount` / `currentHolderCount`, `maxHolderCount`, `remainingSlots`, `canTransfer(from, to, amount)`, `willCreateNewHolder(to, amount)`.

## Events

`ForceTransfer`, `ForceBurn`, `FreezeStatusUpdated`, `ComplianceFeatureDisabledEvent`, `MaxHolderCountUpdated`.

## Errors

`RestrictedTransfer`, `NotIssuanceManager`, `ComplianceFeatureDisabled`, `AccountFrozen`, `HolderLimitExceeded`.


---

# 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/contracts/cyberscrip.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.