KYV Know Your Validator

Who this is for: node and validator operators, and anyone evaluating the infrastructure counterparties an RWA application relies on.

What it verifies

KYV checks the identity and standing of infrastructure-level counterparties (validators, node operators, custodians, and similar ecosystem participants) rather than end users or transactions. It answers "who is running this piece of infrastructure, and are they trustworthy," which matters for RWA applications that depend on those counterparties behaving correctly (a validator attesting, a custodian holding an underlying asset).

Where it applies

KYV is a named compliance primitive in the same taxonomy as KYC, KYB, and KYT, but it targets infrastructure operators rather than token holders. For readers running node infrastructure on Lumia, see Run a Node for the generic operator docs (RPC node, zkNode, DA light client). This page does not restate that setup content. There is no KYV process a Lumia node operator must complete. KYV appears here as part of the compliance taxonomy an issuer may need to reason about, not as a requirement Lumia imposes on operators. Running a node on Lumia carries no identity or vetting step.