Getting the websocket error again which they supposedly fixed yesterday...
Same error here since 3 days...
I posted in their thread and they had fixed it for me yesterday, but it is back again today. If this is their testing policy, I don't mind not getting on their exchange. Doesn't matter how many times they call it a beta, testing is still number 1 priority when the environment goes live. Especially since they will be dealing with a lot of money.