> 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/tokenize-faqs.md).

# Tokenize FAQs

**Who this is for:** issuers and institutions with a specific question before reading the whole Tokenize section end to end.

<details>

<summary>Can I issue a real-world asset on Lumia today?</summary>

There is no confirmed, self-serve issuance path documented for Lumia today: no published tokenization SDK, contract template, or hosted issuance product. What Lumia does document is a standard EVM execution environment, deployment tooling ([Quickstart: your first contract on Lumia](file:///5838283/build/Quickstart-your-first-contract-on-Lumia.md)), and an on-chain KYC verifier pattern ([Integrate on-chain KYC (dev guide)](file:///5838283/build/identity/Integrate-on-chain-KYC-dev-guide.md)) you can build on. See [What is RWA tokenization on Lumia?](broken://pages/17159c5d39a744bce4558707aff4b6edbf068813) for the full breakdown of what's confirmed versus not, and [talk to us](file:///5838283/institutions/Talk-to-us.md) if you're ready to move forward with your own team or counsel.

</details>

<details>

<summary>What compliance do I need to have in place first?</summary>

Lumia enforces compliance at the application layer, not the protocol layer. Your contract, not the chain, checks identity. Start with [Compliance overview for issuers](broken://pages/a0bd23ed075e595ee18010595f46b9ab483cf959) for the questions to resolve with your own counsel, and [Compliance model overview](file:///5838283/lumia/compliance/Compliance-model-overview.md) for the KYC/KYB/KYT/KYV taxonomy those questions draw on.

</details>

<details>

<summary>How is an RWA token different from a generic ERC-20?</summary>

Mechanically, often not much at the level of the base standard. Many RWA tokens are ERC-20s (see [Token standards for RWA](broken://pages/181e8e649768fbeb0c3a5d515bc3c228bf912b74)). The difference is what's built around the token: a transfer-restriction hook that checks eligibility, an attestation anchoring the asset's backing, and an off-chain legal structure that makes the token's claim enforceable. Those are the pieces covered stage by stage in [The asset lifecycle](broken://pages/1e90ccf260352f3d56b480b9cfbc9ef41a713a5a).

</details>

<details>

<summary>Where do I ask something this page doesn't answer?</summary>

General platform support questions go to [Frequently asked questions](file:///5838283/support/Frequently-asked-questions.md). Questions specific to tokenizing your asset go to [Talk to us](file:///5838283/institutions/Talk-to-us.md).

</details>
