Closed cculianu closed 5 years ago
I dunno who this Yura person is. I think I copy-pasted something from my clipboard wrong! My bad!
I'm closing this issue as it has gotten zero love.
And also I'm familiar enough with the code that I don't need this open any more.. I think.
I am particularly interested in error situations that require USER intervention. The only one that comes to mind is if the server is down persistently and the user should probably pick another server.
Can we come up with a mechanism for those errors to make it back to the UI so the user can be prompted to take an action? I noticed the code is set up to propagate messages back to the Qt.py class... so -- it would be nice if we leveraged that somehow.
I want to diffidently and respectfully ask you to look over the protocol/shuffling code and think about situations that the code can get confused in. Like if UTXOs disappear and/or if other errors happen --- how good is the code at dealing with any and all errors? Keep in mind users may be switching chains between BSV and BCH and so UTXOs can disappear!
I am sure you have thought about this a lot over the past year you have worked on CashShuffle off and on. Just asking you to think about it yet again!
Again -- if there are error conditions that need user intervention (such as a server being persistently unavailable) -- we should come up with a way for that information to make its way back to the UI!