I also noticed that when I log in after some time my dark them is all messed up and it is half light and half dark.
Like I said before, many people don't have a clue what they are doing with futures trading so making good tutorial and instructions is must have feature for your website.
I think we indeed have a bug related to half light and half dark themes, we'll investigate. Thanks!
And yes, we are working right now on making it simpler. We'll do a tutorial eventually, but for now we just want to make it easier and more intuitive.
That makes it less likely for P3 or P4 to strike a deal, but makes it more risky to recover the funds when needed. Say P1 dies. Now P2 needs both P3 and P4, while P3 only trusts P1.
I think we can use the scripting language to achieve the same effect without having one person holding multiple keys. So funds might be moved with the following combinations:
P1 + P2
P1 + P3 + P4
P2 + P3 + P4
Also P3 and P4 can have encrypted key backups so that funds are not lost in case P1+P3 or P2+P4 die at the same time. It seems really unlikely that P1 and P2 will die simultaneously, and it also seems really unlikely that the backups for both P3 and P4 are compromised simultaneously, and even so one of P1 and P2 would need to sign such a transaction.
That would be very, very bad! I've never seen any website that publishes all transaction data, and within EU it could even be a GDPR violation.
I assume any exchange keeps trade and transaction data forever, and if they ever need to provide it, they can dig it up.
TL;DR: don't do it. You'll scare away your customers.
Thanks for the candid feedback. Just to make things clear, we would never publish personal information (emails, etc). What we would do is use email + some random salt to generate a hash for each user and then, for each incoming deposit or withdraw, we would publish this hash. So no personal data involved! (and no GDPR violation for sure)
That would be somewhat equivalent to you geting your withdraws from the same address you used to deposit. Maybe you are right and this is really a bad idea, but I don't really understand why someone would be scared by that.
One reason I thought this was OK is because in the long-term I want to make our exchange work with decentralized custody. Fully decentralized exchanges have a lot of problems with latency, front-running and large fees (or spreads) that are really hard to solve. So I think we can get the best out of both worlds with centralized order matching + decentralized custody and setlement.
In this model, traders would make deposits and receive withdraws from smart contracts, and everybody would be able to easily link deposits and withdraws, so that I why I thought this lack of privacy would not be a big issue for most users.
After this explanation, do you still feel that this is a bad idea? If so, can you elaborate on what exactly do you think is bad or will scare users away?
It will be a centrally controlled database, meaning you can put anything you want in there, so anyone accused of anything could just deny it and government won't have conclusive evidence. Or you could be bribed to change something.
We would publish that daily (and maybe even save the hash in the blockchain) so we would have no power to change history.
Also, we if wanted to publish daily balances we could have a full proof of funds! Everyone would be able to check that we have as much funds as the sum of all balances because everyone would be to see the their own balance associated with their own user hash in a public ledger, and they would be able to see that our cold storage address contains at least the sum of all balances listed there.
But again, there are privacy considerations here, so this may turn out to be a very bad idea. We'll not do that if the overall feedback from the community is negative, and of course we would be very transparent regarding what privacy we can offer.
I wanted to test it, but I now get this:
Login Error: We cannot find a valid account with this credentials
Are you sure you didn't forgot your password? We only store a hash of your password, so we have a limited ability to debug that. Can you try the "forgot my password" button and see if it works? This should send you a link in your email to set a new password.
