A new credential cannot tell a wallet whether an older one has become obsolete. During ordinary issuance, revocation must provide that signal. A retained link makes automatic background refresh the exception.
August brought one Yivi app release and one release of the Go library underneath it. App version 8.2.0 was published on 14 August and reached the App Store, Google Play and F-Droid. Version 1.3.0 of irmago, the Go implementation doing the wallet's actual work, was published on 12 August, and app 8.2.0 pins that version.
A first look at the new trust system coming to the Yivi wallet: the ways an issuer or verifier can prove who it is, why a valid signature is not the same as a party you should trust, how the EU's new ETSI TS 119 602 trust lists became our backbone, and what it will take to earn the wallet's top trust level.
Two months ago we announced end-to-end OpenID4VC support in private beta. With Yivi 8.0 and irmago 1.0 shipping today, those protocols reach production — and the foundation underneath them has finally caught up.
This release is the structural moment Yivi stops being an IRMA wallet that speaks OpenID and becomes a credential-format-agnostic wallet that happens to also speak IRMA. It is the single biggest milestone in our transition toward a crypto-agile EUDI wallet.
With irmago 1.0 (currently in beta), the command-line tool you've been calling irma is shipped as yivi, and the Go package that issuer and verifier requestor servers import has moved with it. This post is for anyone running irma server, irma session, or the Docker image in production, and for anyone whose service imports github.com/privacybydesign/irmago to construct or sign session requests — what changes, what stays the same, and how to migrate.
After shipping OpenID4VP support last year and migrating all Privacy by Design issuers to SD-JWT VCs earlier this year, today we're closing the loop: Yivi now supports both OpenID4VCI and OpenID4VP. Issuers and verifiers can integrate with Yivi entirely using open standards.
We're opening a private BETA and inviting organizations to be among the first to integrate.
We're pleased to announce that all Privacy by Design Foundation issuers now issue SD-JWT Verifiable Credentials alongside traditional Idemix credentials. This marks a significant milestone in Yivi's transition to becoming a fully EUDI-compliant wallet.
We're excited to announce a new feature that makes managing your digital identity even simpler: you can now issue your phone number and email address without ever leaving the Yivi app.
We're thrilled to announce that Yivi now supports ID-cards and Dutch Driver Licenses as credentials. This expansion significantly broadens Yivi's international reach and makes the platform more accessible to users worldwide.
According to our mission, we are committed to transparency and accountability. This post-mortem is part of that commitment, detailing the events surrounding the outage of the 7th of January 2026.
We experienced significant degradated user experience on the 7th of January 2026, which affected our services for approximately 4 hours. During this time, users experienced inconsistent success rates in onboarding the Yivi app and or issuing credentials to them. The issue was caused by key rotation of the Yivi scheme and successive issues which arose from rotating the key.