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.
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.
A few months ago, we announced our plans to become an EUDI wallet while still retaining our original privacy-by-design technology.
Since that announcement, we've come a long way, and today it's time to announce the release of the first major step towards true crypto agility: the support for the OpenID4VP protocol and the SD-JWT VC credential format in the Yivi app. In this blog, we'll dive into how we did this and what it means for you.
One of the main goals for Yivi is to become the worlds most user friendly identity wallet. We've already done a lot to help this cause, like allowing the user to directly start issuing missing credentials while they're trying to dislose so they stay in the flow.
In this blog we'll look ahead at some of the plans we have for the near future to improve the user experience.
Authentication and identification are critical components of digital services. This can be done with Yivi, our privacy-friendly ID-Wallet. It provides multiple options for verifying user identities. However, a significant challenge in implementing Yivi is the identifier used for authentication. Government and healthcare organizations can use the BSN (Burger Service Nummer), but private entities must explore alternative options. Below, we discuss potential authentication methods using Yivi, their advantages, and their limitations.
Hey everyone!
As we approach the end of 2024, our team is working hard to deliver as much progress on the project as possible. In keeping with our commitment to the community, we’re excited to share some of the improvements we’ve been working on. A lot of work has been put into getting a production grade hosting environment, but next to that we also delivered on some other areas.