You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My initial vote is for the latter (issuers should assign indexes in a pseudo-random fashion).
There are probably a lot of use cases where very few bits would be flipped -- and it would probably be significantly more costly across an ecosystem and over time to increase the size of lists vs. requiring implementers to do a bit more work (ideally once).
msporny
added
the
before-CR
This issue needs to be resolved before the Candidate Recommendation phase.
label
Sep 10, 2023
Should bitstring be initialized randomly, (reduces compression).
Should bitstring be consumed randomly, (implementation burden on the issuer).
The text was updated successfully, but these errors were encountered: