-
Notifications
You must be signed in to change notification settings - Fork 20
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
Provide guidance on using decoy values. #191
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 with some suggestions.
Co-authored-by: Ted Thibodeau Jr <[email protected]> Co-authored-by: Dave Longley <[email protected]>
index.html
Outdated
Given how difficult it is to statistically simulate a population when it comes | ||
to status entries, and that general advice cannot be given since [=verifiable | ||
credentials=] serve a broad set of use cases, implementers are advised to | ||
allocate status list entry indexes randomly and strive to eliminate the rate at | ||
which status entries are changed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Incorporates suggestion from @dlongley. GitHub diff fails again.
Given how difficult it is to statistically simulate a population when it comes | |
to status entries, and that general advice cannot be given since [=verifiable | |
credentials=] serve a broad set of use cases, implementers are advised to | |
allocate status list entry indexes randomly and strive to eliminate the rate at | |
which status entries are changed. | |
Given how difficult it is to statistically simulate status entries for | |
a population, and that general advice cannot be given since | |
[=verifiable credentials=] serve a broad set of use cases, implementers | |
are advised to allocate status list entry indexes randomly, and to minimize — | |
optimally to never — the rate at which status entries are changed. Allocation | |
of status list entries preserves privacy best when it does not trigger any | |
observable change of a status list. |
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Editorial, multiple reviews, changes requested and made, no objections, merging. |
This PR is an attempt to address issue #150 by providing guidance on the use of decoy values.
Preview | Diff