> ## Documentation Index
> Fetch the complete documentation index at: https://docs.quantumapi.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Token standards

> Quantum Chain token standards (QRC family) supported or planned by Qustody Token Management.

Quantum Chain defines a family of QRC token standards that mirror the operational shape of widely-used Ethereum-style standards. Contracts are written in Solidity, executed by the [QVM](/quantum-chain/qvm-vs-evm), and authorized with post-quantum signatures.

## Standards summary

| Standard   | Type                           | Typical use case                                           | Key operations                                    |
| ---------- | ------------------------------ | ---------------------------------------------------------- | ------------------------------------------------- |
| `QRC-20`   | Fungible token                 | Stablecoins, utility tokens, institutional balances        | `transfer`, `mint`, `burn`, `approve`             |
| `QRC-721`  | Unique non-fungible token      | Unique assets, certificates, ownership records             | `mint`, `transfer`, `burn`                        |
| `QRC-1155` | Multi-token collection         | Mixed token sets, batched assets, gaming-style collections | `mintBatch`, `transferBatch`, `burnBatch`         |
| `QRC-1400` | Regulated security-style asset | Issuance and redemption flows with transfer controls       | `issue`, `redeem`, `controllerTransfer`           |
| `QRC-3643` | Permissioned regulated token   | Identity- and compliance-aware assets                      | `mint`, `burn`, `freeze`, permissioned `transfer` |
| `QRC-4626` | Tokenized vault                | Vault shares, tokenized strategies                         | `deposit`, `withdraw`, `redeem`                   |
| `QRC-3525` | Semi-fungible token            | Financial positions, tranches, structured products         | `mint`, `split`, `merge`, `transfer`              |

## What every QRC standard inherits

* Address format: 20 bytes, derived as `Keccak-256(publicKey)[12:32]` from a post-quantum public key.
* Bytecode and opcodes: identical to Ethereum at the [QVM](/quantum-chain/qvm-vs-evm) layer.
* Authorization: every transaction is signed with a [post-quantum signature](/concepts/quantum-safety) and verified by the precompile at `0x0b`.
* Gas accounting: the gas table matches the EVM Berlin/London rule sets.

## What changes vs Ethereum

* The `ecrecover` precompile is **removed**. Any QRC contract that needs in-contract signature verification must call the post-quantum precompile at `0x0b`. See [QVM vs EVM](/quantum-chain/qvm-vs-evm).
* Tooling that derives keys via BIP-32 / BIP-44 is **not applicable** to post-quantum keys. Wallet integrations must use Quantum Chain key generation.
* `EIP-2612` style permits are not portable as-is and are tracked as a future workstream.

## Picking a standard

* **Want a fungible balance with mint/burn?** Start with `QRC-20`.
* **Need uniqueness or non-fungibility?** `QRC-721`.
* **Mixed inventories or batch operations?** `QRC-1155`.
* **Regulated workflow with controller transfers?** `QRC-1400`.
* **Identity-bound investor list?** `QRC-3643`.
* **Tokenized vault / yield-bearing share?** `QRC-4626`.
* **Tranches / structured positions?** `QRC-3525`.

## Related

* [Token management overview](/qustody/token-management/overview)
* [Managed Token API reference](/api-reference/tokens/list-token-standards)
* [Advanced contracts](/qustody/token-management/advanced-contracts)
* [QVM vs EVM](/quantum-chain/qvm-vs-evm)