Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

use did-communication service type in DID Exchange #1043

Closed
troyronda opened this issue Mar 21, 2021 · 4 comments
Closed

use did-communication service type in DID Exchange #1043

troyronda opened this issue Mar 21, 2021 · 4 comments

Comments

@troyronda
Copy link

The service type should be did-communication rather than IndyAgent in DID Exchange.
@troyronda troyronda mentioned this issue Mar 21, 2021
Merged
@swcurran
Copy link
Contributor

@sklump -- can you please take this? For 0160, it can remain as it was, but for DID Exchange, it should be this new format. Not sure if this data lies in the shared "connection object", which makes it more fun...

@domwoe
Copy link

domwoe commented Apr 12, 2021

Related to this: decentralized-identity/didcomm-messaging#179

@andrewwhitehead
Copy link
Contributor

This is covered in my draft PR here, where we leave it as IndyAgent for the connections protocol for compatibility with current .NET agents: #1056

@swcurran swcurran added this to the 1.0.0 milestone Sep 20, 2022
@swcurran swcurran modified the milestones: Version 1.0.0, Frameworks Sprint 1 Apr 6, 2023
@swcurran
Copy link
Contributor

swcurran commented Aug 4, 2023

Closing this is being addressed in the PR for updating Unqualified DIDs to DID Peer.

@swcurran swcurran closed this as completed Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@swcurran @troyronda @domwoe @shaangill025 @andrewwhitehead