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 for the full architectural explanation, and Compliance model overview for how the four named checks (KYC, KYB, KYT, KYV) fit into that model.

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; for the institutional summary, see /institutions/compliance-posture. Both link back here rather than duplicating this content.

Compliance model overview

The KYC/KYB/KYT/KYV taxonomy explained together, and how each check fits Lumia's permissionless-base/permissioned-app architecture.

KYC (Know Your Customer)

What KYC verifies and where it applies on Lumia (a concept page, not an implementation guide).

KYB (Know Your Business)

What KYB verifies and when an issuer or institutional counterparty typically goes through it.

KYT (Know Your Transaction)

What KYT verifies (transaction-level risk screening) and where it fits an asset's servicing lifecycle.

KYV (Know Your Validator)

What KYV verifies: the standing of infrastructure counterparties like validators and node operators.

Permissionless base, permissioned app layer

The architectural pattern that lets open DeFi and gated RWA applications run on the same Lumia chain.