Walletwasabi: Documents agreement when generating a new wallet

[yahiheb]

Should we agree to the Terms and Conditions, Privacy Policy, and Legal Issues documents whenever we generate a new wallet?

[MaxHillebrand]

This is in context to what we discussed at the dev-call on 2019-07-22 - we need to have a way of updating ToS, and notifying users about this.

It might be enough to require the ToC for the coin join service, and not for the "basic" wallet functions, but I'm not sure.

[hgergoil]

So currently need to agree the Terms and Conditions, Privacy Policy, and Legal Issues documents. But might be enough to require the legal documents on installation before starting to use the wallet.

[MaxHillebrand]

But then there would be no agreement when 1] downloaded releases from github not the website and 2] compile from source there is no agreement...

[nopara73]

This was a bad design decision. With this we cannot update our T&C. It should be agreed at first download of the wallet and whenever we'd update it. Anyhow, this should be refactored soon.

Same issue: https://github.com/zkSNACKs/WalletWasabi/issues/596

[nopara73]

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

[lontivero]

Controversial opinion: I think Wasabi offers two things: a bitcoin wallet and a coinjoin service. The user should accept the some condition to use the software and a different conditions (the service conditions) before starting to use the service.

[hgergoil]

If we are separating this two things and make two TaC , it complicates our lives unnecessarily...

[yahiheb]

3192