VirtEngine

Identity layer

Identity verified by consensus, revealed by proof

VEID turns identity verification into a protocol function: encrypted identity scopes are scored by the validator set's shared machine-learning models, and users prove what matters with zero-knowledge proofs — nothing more.

identity.org.au VEID documentation

Pipeline

From device to ledger

Six stages take a user from document capture to a consensus-committed trust score they can use across the marketplace.

fig 01 — capture → liveness → attestation → encryption → consensus scoring → ZK tiers

  1. Capture

    The VEID mobile wallet captures identity documents with OCR and a selfie, entirely on the user's device.

  2. Liveness

    Active liveness challenges confirm a real, present human — not a photo, replay, or injection attack.

  3. Hardware attestation

    Biometric hardware attestation (fingerprint or iris) plus device integrity checks — Play Integrity on Android, App Attest on iOS — bind the capture to trusted hardware.

  4. Encrypted submission

    Identity scopes are sealed with public-key encryption and signed by both an approved client and the user before upload — only validator recipients can decrypt.

  5. Consensus scoring

    Validators decrypt, score the data with shared machine-learning models, and commit an identity trust score to the ledger by consensus — the patented core of the protocol.

  6. ZK verification

    Zero-knowledge proofs (x/veid/zk) let users prove facts about their verified identity — score thresholds, attributes — without revealing the underlying data.

Design principles

Privacy is the architecture, not a policy

x/encryption

Encrypted end to end

Raw identity data is never public on-chain. Scopes are public-key encrypted so only intended validator recipients can decrypt — in transit and at rest.

x/config

Approved clients only

Validators verify that uploads were produced by an approved client interface and signed by the user. The approved-client list is chain configuration, governed on-chain.

x/veid/zk

Selective disclosure

Zero-knowledge verification tiers mean a counterparty learns that your score clears a threshold or that an attribute holds — never the document, biometric, or score itself.

In the marketplace

Why a cloud marketplace needs identity

Marketplace access is identity-dependent by design: providers verify tenants before workloads land on their hardware, and tenants verify providers before trusting them with workloads — cutting fraud in both directions. Sensitive transactions, including account recovery, are additionally protected by on-chain multi-factor authentication (x/mfa). Validators are compensated for identity work through governance-controlled, conservative network incentives.

The VEID wallet reference implementation lives in the protocol repository at mobile/veid-capture-app/. The consumer-facing identity program is presented at identity.org.au.

The full VEID explainer x/veid module reference VEID source