[bisq-network/bisq] DAO state becomes out of sync due to proposal ignored by all voters (#2906)

[sqrrm]

I haven't been able to reproduce the duplication of proposals as you describe. I have seen the DAO state conflict though and I think I know why. The proposal that's not voted on by anyone is not seen as part of the hash chain so it's not saved. It's included in the original hash in the result phase however. 

After restart the clients will throw away the not voted on proposal and get a different hash. I need to look further but I think it might make sense to just exclude the proposals that were not voted on to begin with and there would be no conflicts from this issue.

-- 
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/2906#issuecomment-505840227
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20190626/c3426926/attachment.html>