search

dimmyvi / tigress-requirements

Other
0 stars 3 forks source link

Remove Req-NonCollection #41

Closed bslassey closed 1 year ago

bslassey commented 1 year ago

closes #40

dimmyvi commented 1 year ago

I am afraid if this requirement is removed - and user identity is collected, then nothing prevents implementation from storing and using this info afterwards. The only things that can guarantee identities are not collected is the fact that user IDs are not used to connect to intermediary.

bslassey commented 1 year ago

How would the protocol enforce this property?

alexpell00 commented 1 year ago

How would the protocol enforce this property?

The protocol couldn't really enforce this. I think the requirement should be reworked to something like:

"(Req-Anonymity) Multiple transfers from the same user should not require any consistent identifiers that could be tracked."

alexpell00 commented 1 year ago

How would the protocol enforce this property?

The protocol couldn't really enforce this. I think the requirement should be reworked to something like:

"(Req-Anonymity) Multiple transfers from the same user should not require any consistent identifiers that could be tracked."

We already have that with "Req-NonCorelation"