DIDComm V2 Interopathon #3329
DIDComm V2 Interopathon #3329
Conversation
Signed-off-by: Micah Peltier <micah6_8@yahoo.com>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
|
Can you expand on the Pickup - 3.0 or 4.0 protocol? Is credential issuance/presentation on the roadmap? |
I copied the list from my email that was sent out. At present, decentralized-identity/didcomm.org#110 has not been merged in as I believe we were still waiting on some comments or updates to be made.
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 |
|
Yep, interopathon goals are deliberately narrower than our overall ambitions. Support for more protocols will come. |
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
- Respond to the target list via did resolution - Fix response to incoming messages (hack it till it works) Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
The complexity of a single protocol for DIDComm V2 was a bit much, and adding more protocols would cause unnecessary copy-pasting of boilerplate code that could otherwise be pulled out into their own function. For the time being, I'm planning to include all protocols for the DIDComm V2 Interop within the same protocol plugin (and the same file). In the future, I plan to break this logic out of this file and into their own respective files. I also had a discussion with @dbluhm today about future plans for retrieving our DID for DIDComm V2, as the current implementation is very fragile and requires that, not only is a DID of the appropriate type already created, but that we grab the latest one. For a production system, this is unnacceptable. But for a "cobbled together POC" for the interop? It should be fine. Especially considering that we have plans to change how this all works in the future. Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
Signed-off-by: Colton Wolkins (Laptop) <colton@indicio.tech>
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: