Ok, your solution solves the problem of people making bogus complaints on social media about your service, by giving signed proof mechanisms to protect your image. 
Does this solve the added "red tape" and complexity involved by making these transactions more difficult for the users? How many customers will know how to sign a transaction or request and how do they secure their private key or do you still manage that?
Does this solve the added "red tape" and complexity involved by making these transactions more difficult for the users? How many customers will know how to sign a transaction or request and how do they secure their private key or do you still manage that?
It doesn't just prevent bogus claims to protect us, it gives users something tangible if there is a real claim.
For the "red tape" issue the experience should be the same as a normal exchange with no extra baggage at all. Similar to how some web wallets work when you log in you will locally decrypt the keys.
Does this not expose your service to added risk if FDU's <Fkn Dumb Users> decrypt their own keys and then blame you when someone else steal their coins or fiat money with those keys?
We know most users cannot even secure their account passwords, so how would they know how to secure something as important as their own private keys?
This might lead to even more problems?