Valera – VC-K-powered CMP Identity Wallet App for iOS and Android

Valera is a single-codebase Compose Multiplatform Identity Wallet for iOS and Android. It lets you load, store and present W3C Verifiable Credentials — your PID, driving licence, health insurance card and more — straight from your phone, powered end-to-end by VC-K.

It is the holder side of a complete, self-contained EUDIW playground:

🪪 Issuer → 📲 Valera (this app) → ✅ Relying Party

Provision credentials from the demo issuer, keep them in your wallet, and present them to the demo verifier — all speaking the same emerging eIDAS 2 / EUDIW protocols.

⛔️ Not for production — read before you tap
Valera is a Technology Demonstrator and testbed. Do not load real identity data into it. See Limitations.

Valera tracks the emerging eIDAS 2 technical specification — a regulation that is still very much a moving target when it comes to technical details. Even so, it already interoperates with the EU reference issuing service and EU verifier, and lets you experience first-hand what an EU Digital Identity Wallet (EUDIW) can look and feel like.

✨ What's new in 5.9

Built on VC-K 9, the 5.9 line is all about trust: Valera now checks who it is talking to, and tells you what it found.

• 🏛️ Trust lists — Valera loads the EU Lists of Trusted Entities (LoTE) and uses them to decide which issuers, relying parties and status lists to trust. You can turn the acceptance, development and production stages on or off one by one, and refresh all lists from the settings.
• 🧾 Relying-party validation — Valera checks every presentation request against the relying party's access certificate (WRPAC) and registration certificate (WRPRC), over OpenID4VP, the DC API, BLE and NFC. The consent screen lists every check. Issues like an untrusted, expired, revoked or unlinked certificate, or a request for data the relying party has not registered, show up as warnings. A request that fails its integrity check (e.g. a bad signature) is rejected.
• 🪪 Issuer validation — Before issuance, Valera requests signed issuer metadata and shows whether the issuer is trusted and registered for the offered credentials. Every issued credential is checked with VC-K's CredentialValidator: signature, issuer trust per credential type, validity period, status, and mandatory claims. If any check fails, Valera tells you why and asks before storing the credential.
• 🔍 Validation in the credential details — A stored credential's details show its full validation report. Revoked credentials can now be refreshed too, not only expired ones.
• 🧠 Zero-knowledge mdoc proofs — Valera answers ISO mdoc zero-knowledge proof requests (DCQL mso_mdoc_zk) using the Longfellow-ZK backend. A badge on the consent screen shows whether the request is for a plain mdoc or a ZK proof.
• 📦 Batch issuance — Choose credentials from an offer with checkboxes. Valera requests all selected credentials under one authorization and shows each issued credential on the result screen.
• 🚀 EU Launchpad links — Valera opens eu-eaa-offer and eu-eaap links on Android and iOS.
• 🌐 More accurate DC API matching — The Android matcher now handles SD-JWT claim paths with array indices, null wildcards, whole objects and typed values. Each credential the system picker selects is presented only for the query it was picked for.
• ⚡ Leaner and snappier — Parsing, trust evaluation and credential decoding no longer run on the UI thread. Memory use in the iOS Identity Document Provider extension dropped sharply.

See the CHANGELOG for the full list.

Features

Valera fetches credentials from wallet-issuer.a-sit.plus in a range of formats — even beyond what the upcoming EUDIW targets — and presents them to verifiers over multiple transports.

Get credentials (issuance)

• 📜 OpenID4VCI issuance (authorization code & pre-authorized code flows), including several credentials of one offer at once
• 🌐 Browser-native issuance via the Digital Credentials API
• 🏛️ Issuer validation against signed issuer metadata, registration certificates and the Lists of Trusted Entities
• 🔄 Refresh expired or revoked credentials, with per-credential prompts
• 🛡️ Hardware-backed holder keys, biometric/passcode-gated, with WUA key attestation

Show credentials (presentation)

• 🪪 OpenID4VP with both SD-JWT VC and ISO mDoc presentation
• 🧮 DCQL and ISO DeviceRequest queries — verifiers specify the credentials and data elements to request
• 🧠 Zero-knowledge proofs for ISO mdoc requests (mso_mdoc_zk)
• 📡 Proximity presentation to a verifier over Bluetooth Low Energy and NFC (ISO/IEC 18013-5), with reader authentication
• 🌐 Digital Credentials API presentation on Android and iOS, including ISO 18013-7 Annex C
• 🧾 Relying-party validation of access (WRPAC) and registration (WRPRC) certificates, with every check shown before you consent
• 🔎 Built-in technical detail view to inspect a credential's claims, validity, status and validation report — great for debugging interop
• ✅ Freshness & status indicators backed by token status lists signed by trusted providers

Verify credentials

• 📲 Proximity verifier mode — read and validate ISO mdoc documents from another wallet over BLE and NFC

Supported credentials

Credential	SD-JWT VC	ISO mDoc
Person Identification Data (PID)	✅	✅
Mobile Driving Licence (mDL)	✅	✅
European Health Insurance Card (EHIC)	✅
Age Verification	✅	✅
Power of Representation (PoR)	✅
Certificate of Residence (CoR)	✅
Tax ID	✅
e-Prescription	✅

Unknown schemes degrade gracefully via a fallback scheme, so even credentials Valera doesn't natively model can still be loaded and inspected. For full schema details, head over to the credentials collection repo.

The ecosystem

Valera is developed in lockstep with two companion reference services, so the whole issue → hold → present loop stays interoperable:

	What it is	Try it
🪪 Issuing Backend	A Spring Boot OpenID4VCI issuer (also issuance over the DC API) that mints wallet-ready PID, mDL, EHIC, Age Verification, PoR, CoR and Tax ID credentials as JWT VC, SD-JWT VC and ISO mDoc.	wallet-issuer.a-sit.plus · repo
✅ Relying Party	A Spring Boot OpenID4VP verifier that requests and validates presentations over QR, deep link and the DC API, with configurable DCQL and ISO DeviceRequest queries.	wallet-rp.a-sit.plus · repo

The demo relying party in particular lets you freely define how and which details of a credential are requested — the best way to explore verifiable presentation in all its (technical) glory.

Limitations — not for production

Valera is a testbed and technology demonstrator, not a shippable wallet. Concretely:

• ⚠️ Never load real identity data. Treat everything in the app as throwaway test data.
• 🧪 The demo issuer issues synthetic credentials — many claim values are random or placeholder, and the demo services use ephemeral, self-signed keys that change on restart. Nothing here is a trust anchor.
• 🎯 The specs are a moving target. eIDAS 2 / EUDIW, OpenID4VCI, OpenID4VP, HAIP and the DC API are still evolving; interop can and will break between drafts. Valera follows the latest drafts, not a frozen, certified profile.
• 🚧 No production hardening. It is not security-audited, not certified, and makes no guarantees around privacy, key management or data protection for real-world use.
• 📦 Limited scope. Only the credentials and transports listed above are supported.

It is, however, an excellent sandbox — actively used in teaching at TU Graz's Institute of Information Security.

Design Principles

Valera is designed with distinctly different goals in mind than the EU reference implementation. Most prominently, we follow a KMP-first approach. In a nutshell, this means that given the choice between using two platform-native libraries and glue code to get a job done and investing the blood, sweat and tears it takes to conceive a proper KMP solution, we go the distance and invest in the KMP solution.

In the end, this (at times) tiresome approach brings a couple of advantages to the table:

• Consistency across platforms
• Shared UI tests
• Common, consistent, and thoroughly tested VC-K-powered business logic across
  • Issuer
  • Verifier
  • iOS App
  • Android App
• As an immediate consequence: far less margin for mistakes
• Unified cryptographic functionality integrated with platform-native biometric and passcode-base authentication based on Signum.

This much tighter integration of all moving parts across all parts of back-end and front-end opens up makes experimenting with new features much easier compared to having multiple discrete codebases. As a consequence, introducing new credentials (and testing issuing, and presenting them) must only be done once. It is even possible to introduce new cryptographic algorithms or alter any part of certain workflows and propagate such changes with very little friction across back-end and front-end. As such, Valera, VC-K and Signum make for an ideal sandbox — a property actively used in teaching at TU Graz's Institute of Information Security.

Valera, the issuing service and the demo service provider are under active development and are updated in tandem with each other. Outside contributions are welcome (see CONTRIBUTING.MD)!

Development

To set up this project locally see DEVELOPMENT.md.

---

Co‑Funded by theEuropean Union	This project has received funding from the European Union’s Digital Europe Programme (DIGITAL), Project 101102655 — POTENTIAL.

---

The Apache License does not apply to the logos, (including the A-SIT logo) and the project/module name(s), as these are the sole property of A-SIT/A-SIT Plus GmbH and may not be used in derivative works without explicit permission!