The trust gap
Why a valid signature is not enough
A signed credential proves it wasn't tampered with. It does not tell you whether the issuer is a real, accredited authority, or whether the verifier asking for your data is one you should trust. Verana closes that gap.
Verifiable Credential
A tamper-proof digital claim — here, a Foundational Resident ID issued by MOSIP Inji Certify.
Decentralized Identifier (DID)
A self-owned identifier for each party — the issuer, the verifier, the ecosystem — that the resolver evaluates.
Trust Registry
The on-chain record of who may issue or verify what, under an ecosystem. Here: the MOSIP Pilot Authority's registry.
Accreditation
An issuer/verifier is accredited for a specific credential type — and it can be delegated, metered, and revoked.
The MOSIP Pilot Authority ecosystem
One trust anchor, the official Inji components, a thin Verana layer
Owns the trust registry, the Resident ID schema and the governance framework (EGF).
Issues the Foundational Resident ID as a Verifiable Credential.
Checks the credential, then a Verana add-on shows whether the issuer is accredited.
Holds the credential and checks the verifier before presenting.
OIDC authorization for the wallet's credential download.
Answers, on-chain: is this party trusted, and authorized for this credential?
Check trust live
Ask the resolver yourself — no curl required
Pick a party below. The page queries the live Verana Trust Resolver in your browser — resolve (is it trusted?) and issuer/verifier-authorization (is it accredited for this credential?) — and renders the verdict. This is the same check Inji Verify and the wallet make.
The MOSIP Inji Certify deployment that issues the Foundational Resident ID. Should resolve as a trusted, accredited issuer for this credential.
Issue & verify a Resident ID
Phases 0 and 1 — the credential, and the trust verdict on top
Inji Certify issues the Foundational Resident ID; Inji Verify confirms the signature. The Verana add-on then adds the verdict that matters: who issued it, and are they accredited?
Try it on the live Inji Verify UI — upload one of these sample QRs and watch the verdict change:
Accredited issuer
Untrusted issuer
Not accredited here
Invalid signatureProtect the holder
Phase 2 — verify the verifier, before anything is shared
Before the Inji Web wallet presents a credential over OpenID4VP, it asks Verana whether the relying party is a trusted, authorized verifier (the Verifier check in the widget above). The wallet shows the holder who is asking and defaults to blocking unknown or over-asking verifiers — so trust is checked before any attribute leaves the device, not after.
Governance & economics
Phase 3 — a network that scales and stays accountable
Delegated accreditation
A grantor accredits a second issuer with no transaction from the ecosystem root — it still resolves as authorized.
Fees & deposits
Issuance/verification fees and trust deposits are collected on-chain via permission sessions.
Revocation
Permissions can be revoked on-chain, and slashing backs the trust guarantees with real accountability.
Multiple ecosystems
A second trust registry coexists on the same network, each resolving under its own ecosystem.
The whole point
Authenticity is not legitimacy
At every step — issue, verify, present, govern — a participant can ask the chain whether the other party is actually trusted and authorized, and gets a fail-closed answer. Official MOSIP Inji components, a thin Verana trust layer, no forks.