[bisq-network/bisq] BSQ trading fee calculated incorrectly (#5329)

chimp1984 notifications at github.com
Sat Mar 20 02:53:28 CET 2021


It can be that the user has not a synced DAO state. There are quite some nodes with incorrect BSQ state hash (see DAO monitor in app). We should add some popup to enforce those users to resync DAO state.
You can try to click take offer for those users, then you are connected and at next block you likely get their DAO state and it shows up in the monitor if they have an invalid hash. That would a way how to detect if that is the reason (no guarantee though that u get their hash).

One way to handle that would be like we do for fee receiver address. If the value does not match the expected value we iterate over all past dao param values and if one of those matches we consider it valid. That covers the non-in-sync cases.
As it always can happen that a user gets out of sync, I assume there is no other way around.

-- 
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/issues/5329#issuecomment-803223859
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20210319/984e20ee/attachment.htm>


More information about the bisq-github mailing list