Verifiable Identity for Decentralized Cloud (VEID)

Infrastructure is a high-consequence market. Tenants may run sensitive workloads, providers expose valuable capacity, and validators help secure settlement. Pseudonymous accounts alone cannot answer every question participants need to ask about counterparties.

At the same time, publishing identity documents to a public ledger would be a serious privacy failure. VirtEngine's identity layer, VEID, is designed around evidence and scoped verification rather than public document storage.

Capture should prove presence

Identity assurance starts before a document is analysed. On-device capture and active liveness checks help establish that a real person is present and responding during the verification flow. This reduces the value of replayed media and static submissions.

Sensitive inputs stay encrypted

Identity material is encrypted for the validators authorised to assess it. Validators evaluate required scopes and submit results; the public protocol records the resulting verification state and trust signals, not a readable copy of the applicant's documents.

That separation lets the network use identity evidence without turning the chain into a central repository of personal data.

Verification is scoped

Different roles need different evidence. A tenant account, an infrastructure provider, and a validator do not necessarily require the same checks. Scoped verification makes the policy legible: participants can see which requirements were satisfied without assuming that one universal score answers every risk question.

Identity is one signal among many

Identity does not replace provider audits, hardware benchmarks, performance history, reviews, or dispute records. It complements them. A resilient trust model combines who a participant has proven itself to be with evidence about what it can deliver and how it has behaved.

Explore the VEID overview or read the implementation documentation for the technical path.