Compliance overview for issuers
Who this is for: issuers about to design a token contract who need to know what compliance groundwork is theirs to do first.
This page lists questions, not answers. It states no regulatory, licensing, or jurisdictional position, Lumia's or otherwise. Every question below is one your own legal counsel resolves, not this documentation.
The architecture, briefly
Lumia separates a permissionless base layer (the chain itself imposes no identity gate) from a permissioned application layer (the issuer's own contract enforces whatever gate the asset needs). The full explanation lives at Permissionless base, permissioned app layer; the four named checks issuers commonly build on top of that split (KYC, KYB, KYT, KYV) are explained together at Compliance model overview. This page doesn't repeat either; it exists to name what an issuer still has to decide once they understand that architecture.
Questions to resolve with your own counsel
What this page does not do
It does not tell you which of these questions apply to your asset, does not state an answer to any of them, and does not describe Lumia's own regulatory or licensing position. No page in this documentation set makes a jurisdictional, licensing, or regulatory claim, by design. Those questions belong to you and your counsel.
Last updated
Was this helpful?