For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

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

Classification

How is this specific asset, in each jurisdiction where you intend to offer it, legally characterized, and what obligations follow from that characterization? This documentation makes no claim about how any asset class is or should be classified.

Eligibility

What investor category or verification threshold does that classification require, and how will you prove a given holder meets it? See Eligibility & investor tiers for the pattern, not the specific thresholds: those are jurisdiction-specific.

Verification provider

Who performs your KYC/KYB checks, what evidence do you retain, and for how long? See KYC (Know Your Customer) and KYB (Know Your Business) for what each check verifies.

Ongoing monitoring

What transaction-monitoring (KYT) obligations apply once the asset is live, and who inside your organization owns that ongoing process? See KYT (Know Your Transaction).

Custody and bailment

If the underlying asset is physical or requires a third-party custodian, what does that bailee agreement need to say? See Bailee agreements & common law.

Accountability

Who at your organization signs off on compliance before each issuance, distribution, and servicing event, and what happens if that sign-off is missed?

Redemption and wind-down

What legal obligations govern winding down the asset or the issuing entity, separate from the on-chain mechanics described in Stage 5: Redeem?

What this page does not do

Last updated

Was this helpful?