4K/ Introducing: WACI (Wallet And Credential Interaction)
Introducing: WACI (Wallet And Credential Interactions)
Tuesday 4K
Convener: Jace Hensley (Bloom)
Notes-taker(s):
Tags for the session - technology discussed/ideas considered:
VCs, Presentation Exchange, Credential Manifest
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
https://specs.bloom.co/wallet-and-credential-interactions/
https://specs.bloom.co/wallet-and-credential-interactions/versions/v0.1.0
We reviewed the spec above,
Orie linked this related github issue and discussion:
https://github.com/w3c-ccg/universal-wallet-interop-spec/issues/84
Also related: https://w3c-ccg.github.io/vp-request-spec/#format
Use cases support mobile wallets, backend services and web apps.
Supports chaining of requests…. Relies on credential manifest and presentation exchange
W3C CCG work seems focussed on the “vc-http-api” and “vp-request-spec” as the solutions to this problem…
We reviewed IoT / Web / API considerations for presentation exchange.
We notes the following hypothetically viable non interoperable solutions to this problem:
1. DIDComm v1 (IIW ticket flows?)
2. vp-request-spec + CHAPI
3. vc-http-api + …. ? / w3c ccg traceability API.
4. OIDF vp-token spec?
Leave your email if you want to be contacted about WACI:
orie@transmute.industries
