> For the complete documentation index, see [llms.txt](https://docs.lumia.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lumia.org/tokenize/standards/token-standards-for-rwa.md).

# Token standards for RWA

**Who this is for:** issuers and developers choosing how to represent an asset on-chain. This page describes standards used broadly across the RWA and DeFi space. Lumia is a general-purpose EVM chain, so any of them can be deployed on it.

### Core representation standards

Because Lumia is EVM-compatible, contracts implementing the standard interfaces below run the same way they would on any EVM chain. That is a property of EVM compatibility, not a Lumia-specific RWA product.

| Standard | Token model                | Typical RWA use                                                                                           |
| -------- | -------------------------- | --------------------------------------------------------------------------------------------------------- |
| ERC-20   | Fungible                   | Fund shares, a pool of receivables, or any asset best represented as divisible units                      |
| ERC-721  | Non-fungible               | A single unique asset: one property, one serialized note                                                  |
| ERC-1155 | Semi-fungible, multi-token | Several distinct asset classes or batches in one contract, for example serialized notes with shared logic |

See [Stage 1: Issue](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/tokenize/the-asset-lifecycle/stage-1-issue) for how this choice fits into defining the asset, and [EVM differences on Lumia](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/build-on-lumia/smart-contracts/evm-differences-on-lumia) for how Lumia's EVM environment differs from mainnet Ethereum at the implementation level.

### Vault standards

Yield-bearing or pooled positions are sometimes represented with a vault standard layered on top of a base token: **ERC-4626** (tokenized vaults with synchronous deposit/withdraw) is the established pattern; **ERC-7540** (asynchronous vaults, for positions that can't settle instantly) is a newer extension used where redemption isn't immediate.

### Transfer-restricted standards

Some RWA issuers use a dedicated permissioned-token standard (for example, ERC-1400's partitioned-transfer model or ERC-3643's identity-registry model) instead of layering restriction logic onto a plain ERC-20. Lumia does not mandate a standard: the permission gate is the issuer's to design, as described in [Permissionless base, permissioned app layer](https://app.gitbook.com/s/chmhPiVNAafGw48c4oU2/ecosystem/lumia/compliance/permissionless-base-permissioned-app-layer).