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
Bisq Easy did not provide a trade history view to avoid that users keep the trade history forever and leak privacy of their trade peer in case their computer gets compromised.
But the current solution can lead to 2 not desired behavior:
Some users might keep the trade open forever to have their trade history present. This leads to bad UX as the trade list gets long.
Users might use the export to csv feature and keep that file on their computer forever and by that countering our motivation to protect the peers privacy.
I think its better to add a trade history view where a trade after completion gets moved automatically.
After a certain time (maybe 4 weeks) the peers data in the trade will get deleted automatically to protect their privacy.
For this we would need to tag the log messages with the trade state so that we can find the relevant log messages containing the account data easier. In case users have exchanged in regular chat messages private information we cannot do much. Deleting all chat messages should be considered as well.
Bisq Easy did not provide a trade history view to avoid that users keep the trade history forever and leak privacy of their trade peer in case their computer gets compromised.
But the current solution can lead to 2 not desired behavior:
I think its better to add a trade history view where a trade after completion gets moved automatically.
After a certain time (maybe 4 weeks) the peers data in the trade will get deleted automatically to protect their privacy.
For this we would need to tag the log messages with the trade state so that we can find the relevant log messages containing the account data easier. In case users have exchanged in regular chat messages private information we cannot do much. Deleting all chat messages should be considered as well.
See Bisq 1 issue to the topic: bisq-network/bisq#5396 and bisq-network/bisq#6001
The text was updated successfully, but these errors were encountered: