Closed msporny closed 1 year ago
-1 to split the specs (makes impl tougher) +1 to privacy analysis, language around privacy risk and reducing that risk
privacy considerations being tracked in #86
TPAC VC WG mtg. no consensus to unify the design space.
The issue was discussed in a meeting on 2023-09-15
The current specification, in an attempt to create just one status list type, overloaded the previous status list with a variety of new features that makes it more complex to implement and changes the privacy characteristics of the status list.
Managing a multi-bit status list has additional implications, such as how to decoy the list data in a believable way -- it's not as simple as just flipping bits now, you have to have expertise on what each status means and how statistically significant flipping each bit is going to be.
In addition there are status list messages that can be defined now that are not needed for the simpler revocation/suspension use cases provided before.
This issue is to track the notion of separating the design space into two different types of status lists - SingleBitStatusList and MultiBitStatusList (or whatever names we might bikeshed towards in the future).