[bisq-network/bisq] Use global price data instead of local (#3649)

Bisq2People notifications at github.com
Thu Nov 21 04:10:00 UTC 2019


With global price one is assured that all market prices have the same average reference price calculated by BitcoinAverage. Thus the all prices are behaving the same because all prices are then calculated by currency conversion. That is how prices normally are viewed as being on a single market. In opposite local prices are set separate thus the price appears way off and not properly aligned to the single global market on low volume currency markets. One can go to BitcoinAverage and check that for USD the difference between local and global price is about 0.1%. But for minor currencies on low volume markets the price is way off, typically 10-30% for SEK. 
There are reports that this price can not be used for serious trading. I would myself not make a market order in SEK in Bisq because of this. It would almost be the same as Bisq wouldn't have an external price reference. Because of low volume we need good external price references.
Thank you for your concern, you have a point, but I have studied this phenomena in depth on BitcoinAverage and it should be clear after some evaluation that using global price is the optimal solution that doesn't make special exceptions for selected currencies making it messy and more difficult to implement.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/pull/3649#issuecomment-556911250
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20191120/fc7bb1c9/attachment.html>


More information about the bisq-github mailing list