nopara73

> It might be impossible to solve this with the robot It's not and it's already solved. If you don't understand it, then read https://github.com/zkSNACKs/WalletWasabi/issues/9092#issuecomment-1247764567 carefully please.

> simplicity by default Let's make that official 😄

One caveat that if more than 2 coins are already registered it's better to leave them registered rather than deregistering as it'd potentially expose common input ownership with a timing...

I think the attack vectors are clear and I explained them here: https://github.com/zkSNACKs/WalletWasabi/issues/8172#issuecomment-1140192207 FTR because of that, it makes little to no difference overall. But certainly an noncontroversial change.

I think your log and your screenshot are unrelated. The synchronizer works well. In line 272 it catches the network error and in line 274 it logs it, then it...

The PR wasn't resolving this issue.

@yahiheb if I understand you correctly you'd prefer not having this feature, because you believe people should be writing down their recovery words on a paper?

> Yes, on a paper or any physical support. If that premise would be true, then I might agree with those conclusions. I believe this is the premise that the...

I have it on my backlog. Probably what will happen with this is that we put these to the controversial bucket and start the non-yet existing controversial topic resolving protocol....

Thanks, this is very insightful! Let me try to parse point by point: **On long legal agreement.** Just to make sure you're talking about the [2.0 agreement](https://github.com/zkSNACKs/WalletWasabi/blob/master/WalletWasabi/Legal/Assets/LegalDocumentsWw2.txt) and not the...