Open TheTechmage opened 2 weeks ago
Can you expand on the Pickup - 3.0 or 4.0 protocol?
Is credential issuance/presentation on the roadmap?
Can you expand on the Pickup - 3.0 or 4.0 protocol?
I copied the list from my email that was sent out. At present, https://github.com/decentralized-identity/didcomm.org/pull/110 has not been merged in as I believe we were still waiting on some comments or updates to be made.
Is credential issuance/presentation on the roadmap?
Not for the interopathon. The goal was to get people moved over and communicating via DIDComm V2 instead of V1. Implementing credential issuance/verification is way more work than what can be done in ~1 month's worth of time. Once we've achieved "basic communication", it should be more feasible to do something a bit more advanced.
Does this sound about right, @dbluhm?
This makes sense to me and I agree. I was sort of wondering if the pickup protocol could be used as an intermediary way to offer a credential to be "picked up" at an endpoint. This is a fairly common pattern in education, where an application/vc resource is temporarily hosted at an endpoint for a holder to pickup.
But from reading the issue/pr this is more of a message-pickup
and not an arbitrary resource.
Yep, interopathon goals are deliberately narrower than our overall ambitions. Support for more protocols will come.
ACA-Py currently supports the bare minimum of DIDComm V2 communication (we respond with a problem report). The DIF is hosting an Interop-a-thon for DIDComm V2 before the end of the year. We're working to implement the features to support DIDComm V2 before the interop occurs.
Goal/Theme: "DIDComm V2 Communication Basics" Must support:
Bonus: