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
What is currently called "Account 0" is the lowest level, i.e. "one shield"
We can add the complexity that this will hide later on if we like, but the current view is all kinds of confusing, so this would be an improvement.
Note that this concept/design is by no means final, since we can't always map "privacy level" to "accounts" (mixdepths) in a truthful one-to-one manner. But again: it's a big improvement from the current UI and should be easier to understand than mixdepths.
The text was updated successfully, but these errors were encountered:
I like the idea of an overall privacy level to motivate users. I'm wondering how should we compute this, though.
(I'm using "privacy level" and "mixdepth" interchangeably here for simplicity.)
My first thought was simply computing a weighted average over all coins in all privacy levels. While implementing I started to doubt that this makes sense.
My thinking is this: Let's say you have one coin with privacy level 1️⃣ and another coin with privacy level 5️⃣ .
The overall average privacy level would then be 3️⃣ .
But if you spend the coin with privacy level 1️⃣ you don't get privacy as if it were a coin with privacy level level 3️⃣ . All you get is privacy level 0️⃣ . This might be confusing for the user who could assume that the overall privacy level applies to all coins when in reality it is just the average and doesn't correspone to the actual privacy of individual coins at all.
See the current design in Figma:
In short:
We can add the complexity that this will hide later on if we like, but the current view is all kinds of confusing, so this would be an improvement.
Note that this concept/design is by no means final, since we can't always map "privacy level" to "accounts" (mixdepths) in a truthful one-to-one manner. But again: it's a big improvement from the current UI and should be easier to understand than mixdepths.
The text was updated successfully, but these errors were encountered: