Last updated 3 August 2026
Behind your verification level sits a score: a number from 0 to 100 that the network computes from your verification evidence. You do not need to manage it — the wallet surfaces your tier, which is what services actually use — but understanding it helps the system feel less like a black box, which is exactly what an identity score must never be.
What feeds the score
The scoring model is part of the open-source codebase, so the weighting of these signals is public and inspectable — auditable by anyone, not asserted by us.
- Document authenticity signals — tamper checks, format validity, security features read during capture.
- Face match — how confidently your live selfie matched your document portrait.
- Liveness results — the outcome of the blink / head-turn / smile challenges.
- Hardware biometric and device attestation results, at the levels that include them.
- Verification history — sustained successful verification over time strengthens the picture.
From score to tier
Tiers are bands over the score, recorded on-chain: reach a band's threshold and you hold that tier. Services see the tier — or, if they require a specific threshold, a yes/no or zero-knowledge proof that your score meets it. They do not see the number itself, and they never see the signals beneath it.
This is deliberate layering: the evidence stays encrypted, the score summarises the evidence, the tier summarises the score — and each audience sees only the layer it needs.
If your score seems wrong
Scores change only when verification evidence changes — a re-verification, an expired document, a revoked consent. If your tier dropped and you do not know why, check your wallet's history first: the triggering event is recorded. Most fixes are re-verification with current evidence.
If you believe a verification outcome is genuinely incorrect, the network has an appeal path for disputed results, and failure never creates a penalty score — retrying is always safe. See if verification fails for the practical checklist.