> For the complete documentation index, see [llms.txt](https://lumiwave-inno.gitbook.io/lumiwave-protocol-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lumiwave-inno.gitbook.io/lumiwave-protocol-whitepaper/glossary.md).

# Glossary

* **LumiWave Protocol (LWP)**\
  The dedicated IP-focused blockchain protocol and network pursued by LumiWave.
* **Protocol**\
  The set of rules the network agrees on and executes, including state transitions, transaction processing, and resource/fee policies.
* **Mainnet**\
  The production network environment where real assets and activities are operated.
* **Testnet**\
  A network environment used for validation, integration testing, and iterative experimentation.
* **Consensus**\
  The mechanism by which network participants agree on a single canonical state.
* **Validator**\
  A participant that contributes to consensus by proposing/validating blocks and plays a critical role in network security and stability.
* **Node**\
  A running instance that synchronizes network data, relays and validates transactions, and supports network access and operations.
* **Infrastructure Operator**\
  An operator that supports network usability and access through services such as RPC, indexing, and data pipelines.
* **RPC (Remote Procedure Call)**\
  An interface used by external applications to query blockchain data and submit transactions to nodes.
* **Indexing / Indexer**\
  The data layer (and the system) that collects and transforms on-chain events/state to enable efficient querying.
* **Observability**\
  Operational capability to measure, diagnose, and respond using monitoring, logs, alerts, and tracing.
* **Upgrade**\
  A version change to the protocol or its components, typically involving compatibility, stability, and migration considerations.
* **Governance**\
  A decision-making process that determines protocol direction and policies through proposals and voting.
* **Proposal**\
  A submitted unit of change or execution request for governance deliberation and decision-making.
* **DAO (Decentralized Autonomous Organization)**\
  A governance structure coordinated through on-chain rules and community participation (in context, the LWP governance body).
* **Vault**\
  A custody/accumulation structure where assets may be accrued and managed under defined rules, potentially administered through governance processes.
* **Infrastructure Operating Vault**\
  A vault concept associated with network and ecosystem operations, managed under governance principles.
* **Inflation**\
  A policy-driven supply expansion mechanism defined by the network (specific parameters are defined elsewhere in the document).
* **Reward Routing**\
  The policy-defined flow by which rewards are distributed and/or accrued along specific paths (e.g., validators and/or operational vaults).
* **RWA (Real-World Assets)**\
  An expansion concept that connects real-world rights, benefits, value, or reported outcomes (e.g., settlement and reporting) to an on-chain economy.
* **Attestation**\
  The act of verifying and submitting off-chain facts, outcomes, or rights in an evidentiary form.
* **Attestor**\
  An actor or system that performs attestations.
* **Oracle**\
  A mechanism or provider that delivers external data into the on-chain environment.
* **Schema / Registry**\
  The data structure (schema) and its management/versioning framework used to represent rights, benefits, or outcomes on-chain.
* **Off-chain Data Adapter**\
  An adapter layer (APIs/pipelines) that connects external systems (rights management, settlement, reporting) to on-chain components.
* **Auditability**\
  The property that records and evidence remain traceable for verification and audit.
* **Provenance**\
  The property that the origin and creation path of data/rights are traceable and explainable.
* **Merkle Proof**\
  A cryptographic proof method that can verify inclusion of an item without publishing the full dataset on-chain.
* **Commitment (Hash/Commitment-based Evidence)**\
  An evidence approach that enables later verification (e.g., via hashes/commitments) without directly disclosing sensitive data.
* **Walletless Experience**\
  An onboarding/usage experience designed so wallet installation and seed management are not prerequisites for participation.
* **zk-based Login (ZK Login)**\
  An onboarding approach that uses zero-knowledge–enabled authentication flows to reduce friction.
* **Passkey**\
  A device-native authentication method that reduces reliance on passwords or seed phrases.
* **Session Key**\
  A constrained-permission, time-scoped key used to reduce repeated signing friction for frequent interactions.
* **Gas Abstraction / Sponsored Execution**\
  Execution patterns that reduce direct fee handling or awareness at the UX layer (e.g., sponsored transactions).
* **Transaction Batching**\
  A pattern that groups multiple actions into a single flow to simplify user experience.
* **Transparency & Reporting**\
  An operational principle where governance decisions and execution outcomes are summarized and shared in a traceable and comparable way.
* **Change Log**\
  A record that tracks upgrades, compatibility changes, and operational/policy changes over time.