The VirtEngine network is a decentralised cloud marketplace: tenants deploy workloads, providers lease capacity, and the chain settles between them. Because real money and real infrastructure are involved, actions on the network are gated by identity assurance — and the Identity Wallet is how you provide it. Verifying makes you an approved client: an account whose verification tier satisfies the requirements of the actions it takes.
The flow, end to end
-
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.
-
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.
-
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.
-
You are an approved client
Marketplace actions carry tier requirements. When your tier meets an action's requirement, the network's eligibility check passes and the action proceeds — deployments, leases, marketplace participation.
- Approval is mechanical: tier meets requirement, action allowed.
-
Present your tier — never your documents
Providers and services on the network see your tier and that your score met their threshold. They never see your name, documents or biometrics unless you explicitly consent to share a specific verified claim.
What providers see — and never see
| Providers and the marketplace see | They never see |
|---|---|
| Your verification tier (Basic, Standard, Trusted) | Your identity documents or any images of them |
| That your score meets the threshold their offering requires | Your exact score history or the signals behind it |
| Zero-knowledge proof results they requested (for example, score above threshold) | Your biometric data — in any form, at any tier, ever |
| Verified claims you explicitly consent to share, one by one | Anything from scopes you did not consent to |
How tiers gate marketplace actions
Every offering type on the network carries a required tier, and the chain's eligibility check compares your recorded tier against it before the action executes. Low-risk activity needs little; sensitive roles need a lot — the proportionality principle applied mechanically.
| Your tier | Typically unlocks |
|---|---|
| Unverified | Browsing services that accept the wallet · Activities that do not need identity checks |
| Basic | Low-risk services and small transactions · Services that only need a real-person signal, not a strong identity |
| Standard | Most participating services · Age and attribute proofs (for example, proving you are over 18) · Marketplace activity that requires a verified identity |
| Trusted | Sensitive, high-trust roles — for example validator onboarding on the VirtEngine network · High-value transactions where the counterparty requires the strongest assurance |
If an action needs a higher tier
Nothing fails silently. Your wallet shows which level the action requires and exactly what evidence would raise yours — and climbing is always your choice, made when something you want actually requires it. 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. Tier requirements for specific offerings are set on-chain and may evolve through network governance — this page describes the mechanism, and the technical documentation tracks the current parameters.