Tokenize FAQs

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

Can I issue a real-world asset on Lumia today?

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), and an on-chain KYC verifier pattern (Integrate on-chain KYC (dev guide)) you can build on. See What is RWA tokenization on Lumia? for the full breakdown of what's confirmed versus not, and talk to us if you're ready to move forward with your own team or counsel.

What compliance do I need to have in place first?

Lumia enforces compliance at the application layer, not the protocol layer. Your contract, not the chain, checks identity. Start with Compliance overview for issuers for the questions to resolve with your own counsel, and Compliance model overview for the KYC/KYB/KYT/KYV taxonomy those questions draw on.

How is an RWA token different from a generic ERC-20?

Mechanically, often not much at the level of the base standard. Many RWA tokens are ERC-20s (see Token standards for RWA). 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.

Where do I ask something this page doesn't answer?

General platform support questions go to Frequently asked questions. Questions specific to tokenizing your asset go to Talk to us.