-
Notifications
You must be signed in to change notification settings - Fork 44
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.
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
Verified Contact | development #1931
Comments
I was chatting with Oliver on this topic. We thought that the wallet could automatically acknowledge either a Person proof request, a DBC proof request or a CANdy DID as a verified contact. |
Recognition of the CANdy DID will work with issuer who have a static public DID. I am curious if our BC gov verifiers would or could have a static CANdy DID, and could that also be the for VC-AuthN-OIDC use cases like ACM. |
I am not too sure about the wallet "automatically acknowledge", I think it needs to have user consent. Just because I am connecting with you, it doesn't mean I want to tell you my real name, or share anything. Maybe there is a bit of someone needs to share first. The what is being verified, it might also be a factor. I just want to know you are a real person (and not robot) or I want to know that you are not only a real person, but the person named "John Smith". That is to say, there are some interesting question to investigate. we are not using public DIDs at the moment, we use peer DIDs. Ongoing conversations about OOB and reusing connections using public DIDs. |
I agree. Enable the wallet to recognized a successful proof request or static/public DID, but Allow the user to know that information make the decision to tag the connection as trusted/verified |
Description of feature / user story
As a holder, when connecting to an organization or individual, I want to have confidence that the individual/organization is who they say they are.
Notes
Reference Work
Acceptance Criteria
Wireframes or relevant image assets / links
The text was updated successfully, but these errors were encountered: