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

Provide guidance on using decoy values. #191

Merged
merged 3 commits into from
Dec 8, 2024
Merged

Provide guidance on using decoy values. #191

merged 3 commits into from
Dec 8, 2024

Conversation

msporny
Copy link
Member

@msporny msporny commented Nov 30, 2024

This PR is an attempt to address issue #150 by providing guidance on the use of decoy values.


Preview | Diff

Copy link
Contributor

@dlongley dlongley left a 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.

index.html Outdated Show resolved Hide resolved
index.html Outdated Show resolved Hide resolved
Co-authored-by: Ted Thibodeau Jr <[email protected]>
Co-authored-by: Dave Longley <[email protected]>
index.html Outdated
Comment on lines 1470 to 1474
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.
Copy link
Member

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.

Suggested change
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.

index.html Outdated Show resolved Hide resolved
@msporny
Copy link
Member Author

msporny commented Dec 8, 2024

Editorial, multiple reviews, changes requested and made, no objections, merging.

@msporny msporny merged commit ba5f8a2 into main Dec 8, 2024
2 checks passed
@msporny msporny deleted the msporny-cr1-decoys branch December 8, 2024 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CR1 This item was processed during the first Candidate Recommendation phase. editorial
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants