Walletwasabi: Figure out proper sync mechnaism for terms, privacy and legal documents with website

Created on 7 Aug 2018 · 6Comments · Source: zkSNACKs/WalletWasabi

The first thing to do is to figure out if we can show GitHub Markup document or PDF in the software without introducing external packages.

questioresearch

Source

nopara73

All 6 comments

@nopara73, would the simplest way to do this be to just return the terms, privacy, and legal documents as json objects from the same, or different api endpoints. Otherwise the website and wallet are dependent on the same markup format. At least that would take care of the syncing part.

varsnotwars on 11 Aug 2018

Another issue is the changes. Maybe it'd be better to hash the terms and conditions and if the hash changes, the user must accept the new terms.
Also we should bring the terms from wallet generation to wallet opening. So whenever the wallet opens the wallet would check if the newest rems is accepted or not. We could also update the terms remotely. Or something like that. Nevertheless, we should revise the language of the terms and conditions, it's doesn't leave a good impression on our users.

nopara73 on 24 Dec 2018

If anyone wants to take this issue, please scream and I'll figure out the specification.

nopara73 on 29 Jul 2019

I will take this.

molnard on 14 Aug 2019

👍1

@molnard You did not:) So what needs to be done here.

[ ] Revise the legal docs now that we are 1 year smarter and we have funds to hire someone for legal review.
[ ] Add a new call to the backend that serves the legal documents.
[ ] Add a new json entry to the versions call that will contain the legal documents version.
[ ] On the client side, serialize a latest agreed legal version entry to the config file.
[ ] Code a new UI element that prevents the user to progress without agreeing to the legal docs.
[ ] If the latest agreed version entry is smaller than the reported version by the update checker, then fire up this new UI element so to make people agree.
[ ] Figure out the transition. Most of this change can be implemented, but in order to put everyone on the same page we need a Wasabi hardfork.