adding an option for a third party to attest binding between a DID and a domain. #99
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
Sakurann
requested review from
bumblefudge,
paulgrehan,
dtmcg,
quartzjer and
jischr
as code owners
OR13
approved these changes
Jul 1, 2023
Sakurann
commented
Jul 1, 2023
Sakurann
commented
Jul 1, 2023
|
Not sure if the profile support this, but are text records used for anything yet? |
sudeshrshetty
approved these changes
Aug 14, 2023
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.
adds a new section that defines a verified domain jwt that allows a third party to prove a binding btw a DID and a domain.
I think more clarifications can be provided, but first pass.
need to
also made clearer that trusting the verifier and verifying the binding btw DID and a domain are two different things.