> 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/ecosystem/lumia/compliance.md).

# Compliance

**Who this is for:** issuers and developers who need to understand how compliance fits into Lumia's architecture before deciding what to build. These are concept pages: for jurisdiction- or license-specific claims, none are made here; see the note below.

Lumia separates two layers:

* **A permissionless base layer.** The chain itself (sequencing, execution, the DA layer) applies no identity or permission gate. Anyone can transact, deploy a contract, or run a node, the same as any general-purpose EVM chain.
* **A permissioned application layer, chosen per app.** Compliance is enforced by the contract or application an issuer deploys, not by the protocol. An issuer picks the gate their asset needs; the chain does not impose one global regime on every contract.

See [Permissionless base, permissioned app layer](broken://pages/dd092175644a89b7d8a7857dac68f3b073fec647) for the full architectural explanation, and [Compliance model overview](broken://pages/210a2df6ee5b1813f7f44c7caa0b21b75de5e908) for how the four named checks (KYC, KYB, KYT, KYV) fit into that model.

{% hint style="info" %}
**What this section does not claim:** none of these pages state that Lumia is licensed, registered, or compliant with any specific regulator, jurisdiction, or asset class. That is a legal determination, not a documentation one. For the issuer-facing compliance summary, see [`/tokenize/legal/compliance-overview`](file:///tokenize/legal/Compliance-overview-for-issuers.md); for the institutional summary, see [`/institutions/compliance-posture`](file:///institutions/Compliance-posture.md). Both link back here rather than duplicating this content.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Compliance model overview</strong></td><td>The KYC/KYB/KYT/KYV taxonomy explained together, and how each check fits Lumia's permissionless-base/permissioned-app architecture.</td><td><a href="broken://pages/210a2df6ee5b1813f7f44c7caa0b21b75de5e908">Broken link</a></td></tr><tr><td><strong>KYC (Know Your Customer)</strong></td><td>What KYC verifies and where it applies on Lumia (a concept page, not an implementation guide).</td><td><a href="broken://pages/3f0c1814aaf218aab7cae0c1ceaf99d9e47049cb">Broken link</a></td></tr><tr><td><strong>KYB (Know Your Business)</strong></td><td>What KYB verifies and when an issuer or institutional counterparty typically goes through it.</td><td><a href="broken://pages/1c404b728a0e4b865a04eb664c5ecb418bd2f6c8">Broken link</a></td></tr><tr><td><strong>KYT (Know Your Transaction)</strong></td><td>What KYT verifies (transaction-level risk screening) and where it fits an asset's servicing lifecycle.</td><td><a href="broken://pages/91b028eb877a57221a1a7e7a4d53b61d78c9eac6">Broken link</a></td></tr><tr><td><strong>KYV (Know Your Validator)</strong></td><td>What KYV verifies: the standing of infrastructure counterparties like validators and node operators.</td><td><a href="broken://pages/ed79b1986f67305518ca253741857cc99af948a1">Broken link</a></td></tr><tr><td><strong>Permissionless base, permissioned app layer</strong></td><td>The architectural pattern that lets open DeFi and gated RWA applications run on the same Lumia chain.</td><td><a href="broken://pages/dd092175644a89b7d8a7857dac68f3b073fec647">Broken link</a></td></tr></tbody></table>