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

Precise timestamps of status changes #94

Closed
decentralgabe opened this issue Nov 13, 2023 · 2 comments
Closed

Precise timestamps of status changes #94

decentralgabe opened this issue Nov 13, 2023 · 2 comments
Labels
before-CR This issue needs to be resolved before the Candidate Recommendation phase. pr exists

Comments

@decentralgabe
Copy link
Contributor

We have a use case to determine the time when the status of a given credential has changed. Without drastically changing the spec this can only be done if status list credentials have a validity window (valid from / valid until).

With a validity window, and consistent fetching (at the windows expiry) of status lists one could determine that a bit had flipped within a given window, and be able to approximate a timestamp of a given status change.

To make this type of query simpler I suggest adding language to the spec that speaks to the (optional) capability of a status list server to support historical queries, or revisions of the document from a given time period. I believe this would maintain the privacy preserving characteristics of the specification while adding the ability for verifiers to approximate status change time, which is useful in a number of circumstances.

@decentralgabe decentralgabe changed the title Support historical query of status lists Precise timestamps of status changes Dec 11, 2023
@msporny msporny added before-CR This issue needs to be resolved before the Candidate Recommendation phase. ready-for-pr labels Dec 27, 2023
@msporny
Copy link
Member

msporny commented Dec 29, 2023

PR #112 has been raised to address this issue. This issue will be closed once PR #112 has been merged.

@msporny
Copy link
Member

msporny commented Jan 13, 2024

PR #112 has been merged, closing.

@msporny msporny closed this as completed Jan 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
before-CR This issue needs to be resolved before the Candidate Recommendation phase. pr exists
Projects
None yet
Development

No branches or pull requests

2 participants