> 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/support-and-community/glossary.md).

# Glossary

**Who this is for:** anyone who hits a term in these docs they don't recognize. At the end of this page you'll have a short definition and a link to the full page for anything that has one. Terms whose definition isn't confirmed yet are marked as such rather than guessed.

## A

**Account abstraction**: letting an account (wallet) be governed by programmable logic instead of only a private key, for example social recovery or gas sponsorship. See [Account abstraction](file:///5838283/lumia/architecture/Account-abstraction-and-intents.md).

**AggLayer**: Polygon's cross-chain settlement layer, used to connect Lumia to other CDK-based chains. See [How Lumia settles and bridges to Ethereum](file:///5838283/lumia/architecture/polygon/How-Lumia-settles-and-bridges-to-Ethereum.md).

## B

**Beam**: Lumia's public testnet. Not the same network as the retired "Lumia Testnet". See [Networks](file:///5838283/reference/Networks-and-endpoints.md) for its chain ID and RPC.

**Bridge**: the mechanism for moving assets between Lumia and another chain (e.g. Ethereum). See [Bridge assets to/from Lumia L2 (technical)](file:///5838283/build/bridge/Bridge-assets-to-from-Lumia-L2.md).

## C

**CDK (Polygon CDK)**: the Chain Development Kit Lumia is built on; the toolkit for building a zkEVM L2 settled via Polygon's stack. See [What Lumia's chain is built with](file:///5838283/lumia/architecture/polygon/What-the-Lumia-chain-is-built-with.md).

**Chain ID**: the number a wallet or app uses to identify which network it's talking to. See [Networks](file:///5838283/reference/Networks-and-endpoints.md) for Lumia's values.

**Compliance (KYC/KYB/KYT/KYV)**: the taxonomy Lumia uses for identity and transaction checks at the application layer; the chain itself stays permissionless. See [Compliance](file:///5838283/lumia/compliance/Compliance.md).

## D

**DA (Data Availability)**: where the data behind a transaction is published and guaranteed retrievable, distinct from where the transaction is executed. See [Data Availability](file:///5838283/lumia/architecture/data-availability/Data-availability.md).

## E

**Explorer**: the web UI for looking up transactions, blocks, and addresses on a given network. See [Explorers](file:///5838283/reference/Block-explorers-reference.md).

## G

**Gas**: the fee paid to execute a transaction. See [Gas & Fees](file:///5838283/reference/Gas-and-fees.md).

## H

**HyperNodes**: Lumia's commercial node product, kept explicitly distinct from the generic, self-run node infrastructure at Run a node. See [HyperNodes](file:///5838283/pulse/HyperNodes.md).

## I

**Indexer**: a service that reads chain data and makes it queryable (e.g. for a subgraph). See [Indexers](file:///5838283/ecosystem/Indexer-providers.md).

## J

**JSON-RPC**: the standard request/response API a wallet, script, or node client uses to talk to a blockchain node. See [JSON-RPC API](file:///5838283/reference/JSON-RPC-API.md).

## K

**KYB (Know Your Business)**: identity verification applied to a business/entity rather than an individual. See [KYB](file:///5838283/lumia/compliance/KYB-Know-Your-Business.md).

**KYC (Know Your Customer)**: identity verification applied to an individual user. See [KYC](file:///5838283/lumia/compliance/KYC-Know-Your-Customer.md).

**KYT (Know Your Transaction)**: monitoring transactions themselves for risk, rather than verifying the identity behind them. See [KYT](file:///5838283/lumia/compliance/KYT-Know-Your-Transaction.md).

**KYV (Know Your Validator/Vendor)**: verification applied to infrastructure participants (e.g. node operators or vendors) rather than end users. See [KYV](file:///5838283/lumia/compliance/KYV-Know-Your-Validator.md).

## L

**LUMIA**: the chain's native token. See [LUMIA token](file:///5838283/lumia/tokens/LUMIA.md).

## M

**Mainnet**: Lumia's live production network, also called Lumia Prism. See [Networks](file:///5838283/reference/Networks-and-endpoints.md) for its chain ID.

## O

**Oracle**: a service that brings off-chain data (e.g. prices) on-chain for contracts to use. See [Oracles](file:///5838283/ecosystem/Oracle-providers.md).

## P

**Permissionless base, permissioned app layer**: Lumia's architectural pattern. The base chain is open to anyone, while individual applications can require compliance checks per app. See [Permissionless base, permissioned app layer](file:///5838283/lumia/compliance/Permissionless-base-permissioned-app-layer.md).

**Portal**: a coming-soon Lumia section, not yet live. See [Portal](file:///5838283/portal/Portal.md).

**Pulse**: a coming-soon Lumia section covering HyperNodes, not yet live. See [Pulse](file:///5838283/pulse/Pulse.md).

## R

**Retired testnet**: an earlier "Lumia Testnet" that is no longer live. Its RPC and explorer are dead; it is not Beam. See [Retired testnet](file:///5838283/reference/Retired-testnet-1952959480.md) for its old chain ID and how to tell if you're still pointed at it.

**RWA (Real-World Asset)**: an off-chain asset (e.g. credit, real estate, commodities) represented and managed on-chain. Lumia's core focus area. See [Tokenize overview](file:///5838283/tokenize/What-is-RWA-tokenization-on-Lumia.md).

## S

**Sequencer**: the component that orders and batches transactions before they're proven and settled. See [Sequencer](file:///5838283/lumia/chain-security/Sequencer.md).

## T

**Testnet**: see Beam and Retired testnet above; Lumia has one live testnet (Beam) and one retired one, and they are not interchangeable.

## V

**Validium**: a scaling design where transaction data is kept off-chain (off the L1) while validity is still proven with zero-knowledge proofs. See [Validium](file:///5838283/lumia/architecture/data-availability/Validium.md).

**Volition**: a variant of Validium that lets each transaction choose where its data is made available, rather than committing the whole chain to one model. See [Volition](file:///5838283/lumia/architecture/data-availability/Volition-enhanced-validium.md).

## W

**Wallet**: the software or hardware a user holds keys in and signs transactions with. See [Getting a wallet](file:///5838283/use/wallets/Getting-a-wallet.md).

## Z

**zkEVM**: an EVM-equivalent execution environment whose correctness is proven with zero-knowledge proofs rather than re-executed by every verifier. See [Smart contracts overview](file:///5838283/build/smart-contracts/Smart-contracts-on-Lumia.md).

**zkML**: verifiable machine-learning inference, where a zero-knowledge proof attests the model ran correctly without revealing its internals. See [zkML overview](file:///5838283/tokenize/zkml/zkML-on-Lumia.md).

**zkProver**: the component that generates the zero-knowledge proofs validating transaction execution. See [zkProvers](file:///5838283/lumia/chain-security/zkProvers.md).