identity.org.au

The service

Verify on VirtEngine

VEID is an optional, privacy-preserving trust signal. Keep original identity document images on your device and choose whether to present a disclosed proof for a specific offer.

The VirtEngine network is a decentralised cloud marketplace: tenants deploy workloads, providers lease capacity, and the chain settles between them. VEID is not a general participation requirement. Where a deployed protocol and client support it, a provider may request a specific proof for an individual offer. You decide whether to provide that proof or choose another listing.

Your wallet ON YOUR DEVICE Document capture Front and back, OCR checked Selfie + liveness Blink, head turn, smile Hardware biometrics Fingerprint or iris, attested Encrypted here first Nothing leaves in the clear Encrypted evidence VEID on the VirtEngine chain Scoring runs inside attested enclaves x/veid — scoring Composite checks → score 0–100 Tier from score Basic · Standard · Trusted x/veidregistry Governance-approved verifiers Consent records Every grant and revocation, timestamped and auditable Tier + score only — never documents VirtEngine marketplace ONLY IF THE OFFER ASKS Requested claim only Proof meets the stated condition No source image or full OCR Proof matches offer You choose whether to proceed Offer-specific request Other listings can remain open No universal VEID gate If an offer asks for proof, your wallet explains it — you choose to share it or select another listing Source images stay local · submitted data is scoped · proofs disclose only the requested claim
Original document images stay on your device; only separately approved data may be submitted, and any proof request is specific to an offer.

The flow, end to end

  1. Step 1 of 5: Create your wallet

    Set up the Identity Wallet — the mobile app for capture, the web wallet at my.identity.org.au for management. Every wallet starts Unverified.

    • No identity checks yet — just keys created on your device.

  2. Step 2 of 5: Complete verification levels

    Work through the evidence steps your target level needs: document capture and liveness for Standard; hardware biometrics and device attestation for Trusted. Everything is encrypted on your device before it moves.

    • Each step is consented separately, and you review before anything is submitted.
    • You only climb as high as the actions you want actually require.

  3. Step 3 of 5: The network scores and records

    Governance-approved verifiers process your encrypted evidence and the VEID module computes a composite score. Your tier — Basic, Standard, Trusted — is derived from that score and recorded on-chain.

    • The chain records results and encrypted references, never readable evidence.
    • Scoring logic is open source — the model is inspectable, not a black box.

  4. Step 4 of 5: Choose whether to present a proof

    VEID is not a universal marketplace gate. Where supported, an individual offer may ask for a clearly disclosed proof; you can choose to meet it or select another offer.

    • A proof request applies to that offer, not every marketplace action.

  5. Step 5 of 5: Present the requested claim — not your documents

    When you choose an offer with a VEID requirement, present only the requested proof. The provider does not receive your original document image or full OCR output; do not assume every service uses VEID.

What a provider can learn from a proof

The limited information a provider may receive from a proof requested by an individual offer
Only if you present the requested proof Not included in that proof
The claim or threshold result requested by that offer Your original document images and full OCR output
A proof that the requested threshold is met Your exact score history and unrelated attributes
A zero-knowledge result for the specific question, where supported Biometric templates or raw biometric evidence
Only the claim you separately approved for presentation Data from scopes you did not approve for that purpose

When an individual offer asks for a proof

VEID does not gate the marketplace as a whole. Where the active protocol and client support offer-specific requirements, a provider must disclose the requested claim and purpose before you commit. You can satisfy that request or choose a different listing. Sensitive protocol roles may have separate requirements from marketplace offers.

Examples of proofs that may be supported at each verification level; these are not universal marketplace permissions
Your tier Possible scoped use
Unverified Browsing services that accept the wallet · Activities that do not need identity checks
Basic A specific offer's disclosed proof request, when the current service supports it · Other services that do not require VEID remain available
Standard Age and attribute proofs (for example, proving you are over 18) · An individual marketplace offer's disclosed proof request, where supported · Listings that do not require VEID remain available
Trusted Protocol roles or services with separately disclosed, supported proof requirements · A specific offer's disclosed higher-assurance proof request; not a universal marketplace gate

If an offer requests a higher-assurance proof

A supported offer must show its requested proof before you commit. Your wallet should explain what the proof means and what data it uses; you can decline and choose an offer without that requirement. See verification levels for the evidence behind each tier.

Network status honesty

The VirtEngine network and the wallet are open-source infrastructure rolling out together. Offer-specific proof support depends on the active protocol and client; requirements may evolve through network governance. This page describes the policy model, and the technical documentation tracks the current parameters.