-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add issue marker noting guidance about decoy values will be resolved in CR. #171
Conversation
005736f
to
0073c2c
Compare
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.
This accurately captures the status of exploration of the technique. Thanks.
@npdoty wrote:
Great, thanks for the confirmation, @npdoty; we'll get this merged as soon as we can and include it in the CR-ready draft. In an attempt to parallelize the approvals we need, could you please convey that you are ok w/ proceeding to CR as long as the text in this PR is included: |
The issue was discussed in a meeting on 2024-05-15
View the transcript3.1. Add issue marker noting guidance about decoy values will be resolved in CR. (pr vc-bitstring-status-list#171)See github pull request vc-bitstring-status-list#171. Manu Sporny: If we can merge this today, we can include it in the snapshot for publication.
Brent Zundel: You have approval to merge this after this call. |
Merging, as discussed on the call. |
This PR is an attempt to note that issue #150 will be addressed in CR, with more direct involvement by PING (and other concerned parties), by performing a more detailed analysis on decoy values.
Preview | Diff