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.

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

Resolve DID Document at specific time #280

Open
bdesiderio opened this issue Jul 20, 2022 · 7 comments
Open

Resolve DID Document at specific time #280

bdesiderio opened this issue Jul 20, 2022 · 7 comments

Comments

@bdesiderio
Copy link

bdesiderio commented Jul 20, 2022

Hi! We are working with a scenario where we need to validate a VC signed by a Verification Method that then was removed from the DID Document.

We need to resolve the DID Document at time the VC was signed because we consider valid this VC. If we resolve latest DID Document version we can't validate the VC because the Verification Method was been removed.

Eg:
A valid delegate of a company that then changed because he retired. The signatures he has made would be valid until the moment he retired.

Can we solve this problem with ION?

@csuwildcat
Copy link
Member

The data is certainly there, there's just no API for outputting each past revision. It certainly could be added. We think most use cases like this can be more efficiently accomplished by sign old key representations with current keys and expose them through a standard personal datastore you can query from the attached Service Endpoints. This way you have granular ability to represent much more detailed information about the reason for rolling or what UTC date/time range they should be deemed valid from.

@bdesiderio
Copy link
Author

It's very nice! We already raised the possibility of adding this feature to the API

Thanks for the reply!

@peacekeeper
Copy link
Member

@bdesiderio do you have an example DID where this would be useful?

@bdesiderio
Copy link
Author

@bdesiderio do you have an example DID where this would be useful?

We mainly have the use case I discussed above, but another use case we have in mind would be a public key rotation for a verification method. Behind the verification method is the same person but he rotated the public key with which he signs.

But our main use case is this

A valid delegate of a company that then changed because he retired. The signatures he has made would be valid until the moment he retired.

@vriera
Copy link

vriera commented Jul 27, 2022

@peacekeeper
Another example would be: The dean of an University is the one in charge of singing the VC, in this case an univesity title. Eventually the dean will retire and it the Verification Method will be removed, but the titles he had signed before must stay valid.

@peacekeeper
Copy link
Member

@bdesiderio @vriera thanks, but what I meant was not a use case, but an actual example DID that you would like to resolve at a specific time.

I.e. did:ion:xxxxxx ?

@vriera
Copy link

vriera commented Jul 27, 2022

We don't have an actual example DID at ion but this or similiar scenarios have been proposed a few times and we are trying to find a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants