Update the SupportedRFCs Document to be up to date #2722
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Stephen Curran <swcurran@gmail.com>
|
I think the mediator coordination and did:key issues are now resolved. DIDComm v2 support is still work in progress. |
|
Thanks — I’ll update. |
Signed-off-by: Stephen Curran <swcurran@gmail.com>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd welcome feedback on this on other things we want to highlight in this document.
@dbluhm @andrewwhitehead @ianco, do you think these AIP 2.0 comments are still accurate:
did:keyfor full AIP 2.0 supportdid:keyDIDs is supported, but not all protocols are updated yet to usedid:key. This is a breaking change for AIP 1.0 -> AIP 2.0.