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

# CyberShares

* **Source:** [`src/CyberShares.sol`](https://github.com/MetaLex-Tech/cybercorps-contracts/blob/develop/src/CyberShares.sol)
* **Inherits:** `ERC20Upgradeable`

> **Partly implemented.** Several functions, including `safeMint` and `certificateTokenURI`, have their bodies commented out or return empty values. This page describes the intended shape; check the source before relying on it.

## Purpose

`CyberShares` is an ERC-20 share token for a single security class that also carries certificate-formation logic: fungible shares can be formed into individual certificates and voided back into shares.

## Functions

```solidity
function mint(address to, uint256 amount) external onlyIssuanceManager;
function burn(address from, uint256 amount) external onlyIssuanceManager;
function voidToShares(uint256 certId) external;          // burn a certificate back to shares
function formCertificateFromShares(uint256 amount, CertificateDetails details) external;
function setGlobalRestrictionHook(address hookAddress) external onlyIssuanceManager;
function setTransferable(bool _transferable) external onlyIssuanceManager;
function setCertThreshold(uint256 _threshold) external onlyIssuanceManager;
function decimals() public view returns (uint8);
function certThreshold() public view returns (uint256);
function sharesUri() public view returns (string);
```

It also exposes `certificate*` helpers (`certificateOwnerOf`, `certificateApprove`, `certificateTransferFrom` and others) that mirror an ERC-721 surface for the formed certificates.

## Events

`SharesMinted`, `SharesBurned`, `CertificateFormed`, `SharesFromCertificate`, `SharesFromVoidedCertificate`, `GlobalRestrictionHookSet`, `TransferableSet`, `CertThresholdSet`, plus `Certificate*` events.

## Share counts

`CyberShares` keeps no `authorized`, `outstanding` or `reserved` counters. The register of holders is the set of Ledger Entry Tokens (LETs) on the company's [LedgerEntryToken](/building-on-the-protocol/reference/contracts/ledgerentrytoken.md) contracts, and share counts are read from there.


---

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