2025-01-08 Wallet Interop SIG
Agenda: Let’s talk about Digital Trust in 2025 – what do you want to see happen? Goals? Expectations?
Call Time: 8am PT | 11am ET | 5pm CET
Zoom Link:
“A” Week – when call is at 7AM: https://zoom-lfx.platform.linuxfoundation.org/meeting/92188183208?password=defebcea-1cb8-4545-9730-4293450e3a92
“B” Week – when call is at 8AM: https://zoom-lfx.platform.linuxfoundation.org/meeting/98275141397?password=70e1e107-b571-4d7e-a227-8a7d4335cade
Call Recording: Recording of Meeting / Transcript
Welcome, Introductions and Announcements
Attendees:
Stephen Curran (BC Gov / Cloud Compass Computing Inc.) swcurran@cloudcompass.ca
~15 others
Agenda
Project updates – what’s happening in:
ACA-Py
Release 1.2.0 to be released (likely) today. This will be the new LTS.
An ACA-Py plugin for Cheqd is now available with DID and AnonCreds support
Next up is a refactoring of DID Management, and a plugin for did:webvh (and perhaps did:web)
Credo-TS
Annual report submitted, accepted by TAC
Working on 0.6
Bifold
OWL
Others…
Discussion: Digital Trust in 2025 – goals and expectations
Join us ready to discuss what you want to see happen in 2025.
Trend to more cloud-based wallet storage
People are using multiple wallets on a device because they’re in different ecosystems, need to synchronize - how to manage the synchronization. Resistance to the idea of an individual wallet that plugs into different ecosystems
Interop perspective - this is an important issue
Backup, recovery, transitioning between devices is something we haven’t gotten to yet
Considerations around moving private keys securely - in the cloud? copy between devices?
UK - Holder services
Google (likely Apple, too) has accepted that individuals will use multiple wallets on a device at a time, includes mechanisms for invoking the different wallets to see if they can successfully fulfill the request
Currently can use different wallets in parallel with Google and Apple, different backends - this is in production
Future WISIG topic: how does the wallet interop in that environment
OpenID Foundation will lead this group - how does the device find out which wallet can fulfill the request; wallets must be portable and able to be synchronized, across different devices and manufacturers
Digital lifespan
Independent testing and certification - this is fundamental to interoperability
Documention, suite of test scripts to support testing
Trend: shift away from decentralization towards federation
Less of a focus on blockchain and decentralization, public image of blockchain
Back to more “traditional” views of decentralization
Federation - OpenID Federation spec
did:webvh
Just released 0.5 version of the spec
Working on deployment to a did:webvh server
Plugins to ACA-Py to give controller the ability to use did:webvh
In line with the trend away from decentralization, towards traditional web-based systems
Expanding use cases in BCGov
Lawyer credential, person credential
Verifying the verifier
EU requirement that every verifier must register as a verifier
Protection for users, but roadblock for use of verified data overall
OWL Akrida
Adding support for new protocols - currently DIDComm, JSON-LD issuance/verification, adding OID4VC
Trend: use of VCs in supply chain, moving away from triangle of issuer-holder and verifier-holder interactions being separate
Issuers publish, users/anyone retrieve the information
UN Transparency Protocol: UN Transparency Protocol | UN Transparency Protocol
Digital Product Passports use this model
Presentations and interoperability
Verifiers are the driver of the ecosystem, how to remove roadblocks
Wallets and Agents SIG
Open Discussions
Important Links:
Discord: Join the OpenWallet Foundation Discord Server! (Click Accept Invite, check out the #wallet-interoperability-sig channel)
Community Calendar: LFX Meetings